How CPA Networks Work for iGaming Advertisers (The FTD Model, Explained)

You've launched a casino offer. Traffic is flowing, your dashboard shows thousands of clicks, registrations are ticking up — and your finance team still wants to know one thing: how many of those people actually deposited money? That single question is the whole reason CPA networks exist in iGaming. Everything else is plumbing.

If you're buying media for a sportsbook, an online casino, or a poker brand, the cost-per-acquisition (CPA) model built around the first-time deposit (FTD) is probably where most of your budget lives. It's also where most of the confusion lives. Marketers throw around "CPA," "CPL," "RevShare," and "hybrid" as if everyone agrees on the definitions, and they don't. So let's slow down and walk through how this actually works — the payout mechanics, the postback that makes it all trackable, and the levers that genuinely move your cost-per-FTD.

What a CPA Network Actually Does

A CPA network sits between you (the advertiser, or the operator's media buyer) and the traffic. You define an event you're willing to pay for. The network — or in the case of a self-serve ad platform, the network's inventory and optimization layer — delivers users, fires your ads, and only counts a conversion when that defined event happens.

In most verticals the "event" is a sale or a sign-up. In iGaming it's almost always the first-time deposit: the moment a brand-new player funds their account for the first time. That's the FTD. It's the event operators care about because it's the first real signal that a user has economic value, not just curiosity.

So when people say "CPA network for iGaming," they usually mean a network that:

• Sources or aggregates traffic across ad formats and geos
• Tracks the user journey from impression to deposit
• Reconciles conversions through a server-to-server (S2S) postback
• Bills the advertiser per qualified FTD (or per click/impression, depending on the model)

The distinction worth holding onto: a network is a marketplace and an optimization engine, not your CRM. It tells you which click became a depositor. What that depositor does for the next twelve months — that's your retention team's problem, and it's measured separately.

The Payout Models, and Why FTD Wins for Acquisition

There are four pricing structures you'll run into. Each answers a different question.

CPM and CPC are top-of-funnel currencies. You're paying for attention or for traffic, and the conversion math is on you. They're cheap per unit and brutal if your funnel leaks.

CPA-FTD flips the risk. You're paying for an outcome that already has value attached. A deposit means a verified, funded player — not a maybe. That's why it's the default for acquisition budgets: it ties spend directly to the metric your CFO is actually tracking.

RevShare is the long game. Instead of a fixed bounty per deposit, you (or the affiliate) earn a slice of the player's net losses over months or years. Great for aligned, long-term relationships; harder to forecast and slower to pay back.

A lot of mature operators run hybrid deals — a smaller upfront CPA-FTD plus a RevShare tail — to balance immediate cash flow against lifetime value. There's no universally "correct" structure. There's only the one that matches your cash position, your LTV confidence, and your appetite for risk.

For the rest of this guide we'll focus on CPA-FTD, because that's the model most advertisers come to a network like Taroviser to run.

How the FTD Conversion Is Actually Counted

Here's the part that trips up newcomers. A click is not a conversion. A registration is not a conversion. The FTD is the conversion, and it happens on the operator's side — inside the casino's payment system, well after the user has left the ad.

So how does the ad network ever find out the deposit happened? It doesn't see it directly. The operator has to tell it. That handshake is the postback.

The flow, end to end, looks like this:

1. A user sees your ad — a push notification, a popunder, a native widget, whatever format you're running.
2. They click. The network appends a unique click_id to the destination URL.
3. The user lands on the operator's page, registers, and the click_id rides along, stored against that session.
4. Days later, the user deposits for the first time.
5. The operator's system fires a server-to-server postback — a simple HTTP call back to the network's tracking endpoint — carrying that same click_id and the conversion details.
6. The network matches the click_id to the original click, marks an FTD, and attributes it to the exact ad, placement, and source that drove it.

That's it. No pixel sitting in a browser hoping cookies survive. The deposit confirmation travels server to server, which is why S2S is the backbone of iGaming tracking and not an optional extra.

Why S2S beats pixel tracking here

Browser pixels were never built for a conversion that happens days after the click, often on a different device, frequently after the user has cleared cookies or switched from mobile web to a downloaded app. iGaming breaks every assumption a pixel relies on.

S2S postbacks sidestep all of it:

• Latency-proof. The deposit can land hours or weeks after the click. The click_id is stored server-side, so the match still works.
• Cross-device. No reliance on the same browser session surviving.
• Privacy-resilient. As third-party cookies keep getting deprecated, server-side attribution holds up where pixels quietly fail.
• Auditable. Both sides hold a log of the postback. When numbers disagree — and they will — you have something concrete to reconcile against.

The trade-off is setup. You have to wire the postback correctly, pass the right parameters, and agree on what counts as a valid FTD. Get a parameter wrong and conversions silently vanish. More on that in the FAQ.

Optimizing Cost-Per-FTD: Where the Money Actually Moves

Plenty of advertisers obsess over CPM or CPC and lose the plot. Those are input costs. The number that decides whether a campaign lives or dies is cost-per-FTD — total spend divided by qualified first-time deposits. You can have a gorgeous $0.40 CPC and a horrifying $300 cost-per-FTD if the funnel between the two is broken.

Here's where the leverage really is.

1. Optimize on the deposit, not the click

If your bidding and creative decisions are tuned to clicks, you're optimizing for the wrong thing. A source that delivers cheap clicks but few depositors is more expensive than a "pricey" source that converts. Feed FTD data back into the system — through the postback — so optimization happens against the event you're paying for. This is the single biggest lever, and it's the one most easily skipped.

2. Let the campaign learn before you panic

Performance campaigns need a learning window. FTDs arrive with a lag, so the first 24–48 hours of data are misleading by design — you'll see spend before you see the deposits that spend earned. Cutting a source on day one is how good campaigns die young. Give it enough conversions to judge it fairly, then prune.

3. Match the format to the funnel

Different ad formats pull different intent:

• Push and in-page push — strong for re-engagement and high-volume, lower-cost reach
• Popunder — big scale, top-of-funnel, needs a landing page that does heavy lifting
• Native — blends into content, tends to bring more considered clicks
• Banner — reliable for branding and retargeting depositor look-alikes

There's no "best" format in the abstract. There's the format that produces the lowest cost-per-FTD for your offer, in your geo. Test a couple in parallel and let the deposit numbers decide.

4. Use AI optimization to do the boring math at scale

Manually rebalancing bids across hundreds of placements and 200+ geos is a losing battle for a human. This is where algorithmic optimization earns its keep — continuously shifting budget toward placements that produce qualified FTDs and away from the ones that don't, faster than any analyst could by hand. The human's job moves up a level: strategy, geo selection, anti-fraud judgment.

5. Watch the geo mix closely

Cost-per-FTD varies enormously by market. A deposit in a high-competition Tier-1 geo can cost several times what an equivalent deposit costs in an emerging SEA market — and the local payment habits, preferred deposit methods, and regulatory framing differ in every one of them. This is exactly where local market intelligence stops being a buzzword and starts being budget you don't waste. Knowing that a particular SEA market over-indexes on a specific deposit flow, or that a creative angle lands flat in one country and converts in the next, is the difference between a profitable campaign and an expensive lesson.

6. Defend the metric against fraud

Inflated FTD counts ruin your cost-per-FTD math from the inside. Bot deposits, incentivized fake players, and click-spam all corrupt the number you're optimizing against. Algorithmic filtering catches the obvious patterns; a human analyst layer catches the clever ones that adapt to the filters. If your FTDs look too cheap to be true, they probably are — and you want that flagged before you scale spend behind a poisoned source.

A Quick Worked Example

Say you run a push campaign in a SEA market. Numbers are illustrative [VERIFY against your own dashboard]:

• Spend: $5,000
• Clicks: 25,000 → effective CPC $0.20
• Registrations: 2,500 (10% of clicks)
• FTDs confirmed via postback: 100 (4% of registrations)
• Cost-per-FTD: $50

Now you reallocate. The postback data shows two of your six placements drive 70% of FTDs at half the cost. You shift budget toward them, drop a creative that pulls clicks but no deposits, and the registration-to-FTD rate climbs as traffic quality concentrates. Same $5,000, more deposits, lower cost-per-FTD. Nothing exotic — just optimizing on the right event with clean attribution. That's the whole game.

Where Taroviser Fits

Taroviser runs the CPA-FTD model the way it's meant to run: you pay for qualified first-time deposits, S2S postback integration is built in, and AI optimization continuously steers budget toward the placements that actually produce depositors. The platform spans four formats — push and in-page push, popunder, native, and banner — across 200+ geos, with depth in Asia and SEA where local market intelligence does real work on your cost-per-FTD.

A few things that matter operationally:

• No platform fee, no minimum to get started — you're not pre-committing a budget before you've seen the platform convert.
• Fast ad approvals, so launches don't stall in review queues.
• Human-analyst anti-fraud sitting on top of algorithmic filtering, because protecting the integrity of your FTD count is protecting your CPA math.
• 24/7 support plus both self-serve and managed options — run it yourself or have a team run it with you.

The pitch is simple: tie your spend to the deposit, track it cleanly with S2S, and let optimization do the rebalancing while you focus on which markets and offers to push.

FAQ

What exactly counts as an FTD?

A first-time deposit is the first time a brand-new player funds their account. It's distinct from registration (free) and from any subsequent deposit. Networks and operators agree on qualifying rules up front — minimum deposit amount, valid payment method, geo eligibility — so both sides count the same event.

What's the difference between CPA and RevShare?

CPA pays a fixed amount per FTD, settled shortly after the deposit. RevShare pays an ongoing percentage of the player's net revenue over time. CPA gives you predictable acquisition cost and fast feedback; RevShare ties earnings to long-term player value but pays back slowly. Many advertisers blend the two in a hybrid deal.

How does a postback get set up?

The operator (or your tracking platform) configures a postback URL pointing at the network's endpoint. When an FTD fires, that URL is called server-to-server with the original click_id and conversion parameters. The network matches the click_id to the click and credits the FTD. Test it with a manual conversion before going live — a single wrong parameter means conversions never register.

Why are my postbacks not registering conversions?

Usual suspects: the click_id isn't being passed through registration and stored, parameter names don't match what the endpoint expects, the postback fires on the wrong event, or it's blocked by an IP/whitelist rule. Fire a test conversion and check both logs. S2S issues are almost always a mismatch in what's sent versus what's expected.

How long should I run a campaign before judging cost-per-FTD?

Long enough to clear the FTD lag and gather a meaningful sample of deposits — not the first 24 hours, where you've paid for clicks but the deposits haven't landed yet. Judge on confirmed FTDs over a stable window, then optimize. Premature cuts kill campaigns that were about to turn the corner.

Does CPA-FTD work for emerging SEA markets specifically?

Yes, and it's often where the model shines, because cost-per-FTD in less-saturated markets can run well below Tier-1 levels. The catch is local nuance — payment methods, language, and permitted-market framing differ by geo. That's where local market intelligence directly lowers your cost-per-FTD.

Ready to Lower Your Cost-Per-FTD?

If you're an iGaming advertiser tired of optimizing for clicks that never deposit, run the model that's tied to the outcome you actually pay for. Taroviser gives you CPA-FTD pricing, built-in S2S postbacks, AI-driven optimization across 200+ geos, and a human anti-fraud layer — with no platform fee and no minimum to start. Talk to the Taroviser team or launch a campaign and start measuring spend against deposits, not guesses.