8 min read
Key takeaways
- The wallet is the source of truth, not the thank-you page.
- Signal loss hits last-click in the ad account first, then analytics, then anything still waiting on a pixel.
- A conversion API is a pipe with a match rate, not a strategy.
- Map first-time deposit as its own event, in a currency finance recognises.
- Fix the cashier-to-platform join before you buy another dashboard.
What actually breaks?
ITP, consent banners, in-app browsers, cashier retries on a second device, and platforms that train on the last event they can see. A GTM trigger on a success URL misses the player who funded in the app. It also double-counts the player who reloaded the receipt.
Typical loss is not 'a bit of attribution noise'. It is enough to make Meta hunt registrations while finance asks where the deposits went. If you need the service view, see attribution that survives the browser.
How should a deposit event be mapped?
| Field | Rule | Failure if ignored |
|---|---|---|
| Name | ftd vs repeat_deposit, never a generic purchase | Algorithms buy sign-ups |
| Value | Amount finance calls NGR or cash-in, pick one | ROAS becomes fan fiction |
| Currency | Wallet currency, not ad-account default | Geo mix looks profitable by FX |
| Time | Cashier timestamp, not pageview | In-play sportsbook events land tomorrow |
| ID | Stable player key hashed for the platform | Match rate collapses |
If 'purchase' means registration in the Meta account and FTD in GA4, you do not have a stack. You have an argument.
What is a conversion API for, in euros?
Suppose the cashier records 1,200 FTDs. The browser pixel reports 740. The conversion API, with a decent join key, reports 1,050. Match rate is 1,050 / 1,200 = 87.5%. The 150 missing are the work: app deposits, refused consent, bad IDs.
Spending another €20,000 while match rate is 62% trains the platform on a biased 62%. That spend is not acquisition. It is a donation to the wrong audience. MOTIV will not scale paid acquisition on that pipe.
What to fix first
- One FTD definition, written, shared with media and CRM.
- Cashier emit, not thank-you-page emit.
- Conversion API or equivalent pipe with a match-rate dashboard.
- Kill duplicate browser events that still fire 'for backup'.
- Only then models and multi-touch stories.
Identity graphs that ship in two quarters are not a first fix. A 70% join this month is.
Further: How to set a target CPA that still works in month three and the attribution and analytics service.