Tracking qualified first-time depositors in iGaming means treating registrations, first deposits and qualified deposits as three separate conversion events — then checking each against the operator's own qualification rules before you scale a campaign. A registration count alone tells you nothing about whether your traffic works; an unqualified deposit count lies to you in the other direction.
- Track registrations, first deposits and qualified FTDs as three separate events.
- Qualification rules belong to the operator: deposit size, payment method, geography, multi-account checks.
- Postbacks carry the data from operator to tracker — set one per event, never one shared event.
- Reconcile tracker totals against operator statements weekly before scaling.
- Scale on qualified FTDs; raw registrations inflate ROAS and hide junk traffic.
Why iGaming tracking needs its own discipline
iGaming offers pay for player behavior, not clicks. In 2026 almost every serious affiliate program pays on depositors, and many pay only for depositors who pass the operator's own checks — minimum deposit, a real payment method, a permitted country, no multi-accounting. If your tracker treats every registration as a conversion, your cost-per-acquisition number is fiction, and you will scale campaigns that never pay out.
The fix is structural, not cosmetic: three separate events, three separate reports, one reconciliation habit. EZmob campaigns on push, popunder and native traffic report clicks by zone and GEO in real time — the tracker's job is to join that click data to what the operator actually credits you for.
What you are actually tracking: three events, not one
| Event | What fires it | What it proves |
|---|---|---|
| Registration | Player completes signup | Interest, not value |
| First deposit (FTD) | Player's first successful deposit | Real intent |
| Qualified FTD | Deposit that passes the operator's rules | Money you actually get paid on |
Only the third event pays. A campaign can look profitable at 1,000 registrations and $30 CPA on FTDs, then collapse when the operator disqualifies 40% of deposits for bonus abuse or unsupported countries. That gap is the single most common reason iGaming media buyers lose money on paper-winners.
Step 1: Get the qualification rules in writing before launch
Ask the operator or affiliate manager what disqualifies a deposit before you send the first click. The usual rules in 2026: minimum deposit amount, restricted payment methods, excluded countries, bonus-hunter screening, duplicate device or IP checks, and a hold or clawback window. Put each rule into your tracker as a note on the offer so whoever reads the report knows what the numbers mean.
- Minimum deposit: below it, no payout and no credit.
- Geography: deposits from excluded countries are void even if the player registered from an allowed GEO.
- Payment method: some programs exclude prepaid or certain wallets.
- Fraud screens: multi-accounting and emulators void the deposit.
Step 2: Set up separate postback events
Every established tracker supports multiple conversion events per offer. Wire one postback URL per event — registration, deposit, and (where the operator supports it) a qualified-deposit signal — and never merge them into one shared event. How to connect EZmob to Keitaro for real-time postback tracking and How to connect EZmob to Voluum for automated conversion tracking both walk through the exact setup; the same pattern applies to AdsBridge, RedTrack and Binom.
Each postback should carry the click ID and the sub-IDs you passed at click time: campaign, zone, GEO, device and creative. Without sub-IDs you can see that deposits happened but never which zones produced the ones that qualified — and zone-level decisions are where pop and push campaigns are won.
Step 3: Reconcile tracker data against operator reports
Set a weekly habit in 2026: pull the operator's statement, pull your tracker's FTD report, and compare by date and GEO. Expect three kinds of gaps:
- Timing: deposits credited a day or two after the click (hold windows, payment clearing).
- Qualification: deposits the operator refuses that your tracker counted.
- Attribution: deposits your tracker missed because the postback failed.
A tracking gap is a reporting problem; a qualification gap is a targeting problem. The first is fixed with a postback check, the second with GEO and audience changes. Treating them as one number is how campaigns get scaled into quiet losses. How to track EZmob conversions in Google Analytics 4 covers the site-side measurement that complements tracker postbacks when you run landing pages.
Step 4: Check the operator's platform and back office
What the operator's own software can and cannot report shapes what you can track. Operators running platforms with granular back-office reporting can credit per-deposit detail; older stacks often only send aggregate numbers, which forces reconciliation at the offer level.
BetCode provides casino software covering player accounts and back-office management, game aggregation, payments and identity verification, bonuses and affiliate tracking. It also offers WhatsApp and SMS engagement and 24/7 AI support. Operators use their own brand and licence, while BetCode handles launch and migration, including player data, wallets and open bonuses.
When an operator's stack includes affiliate tracking at the platform level, ask for the postback specification early — retrofitting tracking after launch is slower than wiring it in during setup.
Step 5: Scale on qualified FTDs only
Decide in advance what a qualified FTD must be worth to you, and let the tracker's CPA report on qualified events — not registrations, not raw deposits — drive budget moves. Zones and GEOs that produce registrations but no qualified deposits get cut, not topped up. How much do CPA networks pay per conversion explains how payout structures change what counts as a qualified conversion on different programs.
The discipline pays because pop and push traffic is cheap enough to test broadly in 2026 but not free: $100 of test budget spread across junk zones teaches you nothing, while the same budget concentrated on zones that produce qualified depositors gives you a repeatable acquisition number.
FAQ
What is a qualified first-time depositor in iGaming?
A player whose first deposit passes the operator’s own checks: minimum deposit amount, allowed country, valid payment method and no fraud or bonus-abuse flags. Only qualified FTDs reliably pay out.
Why do my tracker deposits not match the operator’s report?
Three reasons: timing (payment holds and clearing delays), qualification (deposits the operator refuses) and attribution (failed or missing postbacks). Compare by date and GEO to see which one you have.
Should I scale campaigns on registrations or first deposits?
Neither. Scale on qualified first deposits. Registrations measure interest, unqualified deposits inflate ROAS, and qualified FTDs are the only number that matches what you get paid.
How long do iGaming conversion holds last?
Hold and clawback windows differ by program and are stated in the offer terms. Ask the affiliate manager before launch and build the delay into your reconciliation schedule rather than judging performance day one.
Can one tracker event cover both deposits and registrations?
No. Keep registration, deposit and qualified-deposit postbacks separate. Merged events destroy the difference between what happened and what paid.
What data should each postback carry?
The click ID plus sub-IDs for campaign, zone, GEO, device and creative. Zone-level and GEO-level joins are where pop and push optimization decisions actually get made.
One last thing
Build a simple weekly spreadsheet with four columns: tracker registrations, tracker FTDs, operator FTDs and operator qualified FTDs. The trend of the last two columns — not the first — is your campaign's real health. Ad networks rarely send qualified-deposit postbacks automatically; the buyers who reconcile manually are the ones whose ROAS matches their bank statements.
Start advertising on EZmob to run iGaming campaigns on push, popunder and native traffic with full sub-ID control: https://dashboard.ezmob.com/auth/register?role=Advertiser