467 claims. Zero credited.
Vision Bridge reported 467 native orders across eight days. We matched every one of them against Converge first-party data and found no Myosin UTM anywhere in the visible paths. Nothing has been paid out while the fix runs.
Zero Myosin UTMs across all 467 visible paths — at both the visit level (141 verified) and the warehouse UTM level (46). When a tag fires, the pipeline captures it completely (Google's control sessions show full source/medium/campaign structure). Myosin's simply don't fire.
The claims' timing checks out — verified orders land within a day of the report date. The gap is not fabrication; it's missing tags.
UTMs dropped client-side
33 of the 46 session-having orders carry a UTM — zero carry Myosin's. The native path lands untagged. Client-side stripping, fix in flight. The 13 Direct/Organic are what we could credit if the map held.
Zero balance
27 of 46 end on Facebook — Meta takes 0%. Nothing is owed while we track a week and return with proper numbers.
141 verified to the minute
The journey rail verified 141 orders with real timestamps and full visit paths. 92% within ±1 day of the report date.
The 326 still pending
Journey capture is running; the Aug-1 warehouse backfill hasn't landed (events_raw holds 09-11 only). No new order events matched in today's sync — the page re-pulls from the same tables when they connect.
The rules we score by
Meta — 0% creditGoogle — 25% creditCPA — $65
Every order is a drop-in
Open any of the 467 in Customer Explorer — its claim, its verified path, its warehouse sessions, its Myosin UTM check.
Two layers, two methods
The 46 orders with warehouse sessions give the UTM-level readout behind the 27 / 13 numbers. The 141 verified journeys give the visit-level census. Different samples, different methods — each labeled, neither overruled by the other.
Layer 1 is the warehouse event stream — session-level, UTM fields intact, the basis of the 27 / 7 / 6 / 4 / 1 / 1 readout. It only exists where the warehouse held a matching session (46 orders).
Layer 2 is Converge journey capture — visit-level paths with minute-precision order times (141 orders). Meta shows up larger here because journeys see every touch, not just sessions that logged events.
Google Ads sessions in the same stream carry the full structure — utm_source=google, utm_medium, utm_campaign, cvg tags. When a partner's tags fire, we capture them completely. Myosin's tags simply don't fire — the gap is upstream, on the client side, and the fix is in flight.
Drop in on any claim
Every one of the 467 orders opens. Claim, verified order time, the full visit path, UTM-level warehouse sessions, and the Myosin UTM check — per order.
Click any row to open it in the explorer above. V = verified order time · W = warehouse sessions · UTM ✓ = a Myosin UTM was found (none were).
| Order | Reported | File | Match | Order time (verified) | Visits | Last touch / visit | WH sessions | UTM |
|---|