From FTDs to Player Lifetime Value: Tracking iGaming LTV
Two traffic sources each bring you 100 first-time depositors in September. Same GEO, same operator, same cost per FTD. On day 30 their players have generated almost the same net gaming revenue: $48 per FTD from one source, $52 from the other. On day 90, the first source has crept up to $62. The second is at $186.
Same FTD count, three times the value.
Short answer: player lifetime value (LTV) is the net revenue a player generates for an operator over the whole relationship, not just the first deposit. If any part of your deal pays on revenue, you need to track it by acquisition cohort: which source and campaign brought each player, and what that group was worth at day 30, 60 and 90.
This guide is for iGaming affiliates and agencies paid on RevShare or hybrid deals, and for anyone tired of scaling sources that look great at the FTD and fade afterward. It covers what LTV actually measures, how CPA, RevShare and hybrid deals change what you need to track, and how to set up Voluum so revenue that arrives months after the click still lands on the source that earned it.
What Player Lifetime Value Means in iGaming
In iGaming, player lifetime value is usually measured in net gaming revenue (NGR), not deposits. Deposits tell you a player funded an account. NGR tells you what the operator kept after the player’s wins, bonuses and costs, and that’s the number RevShare is paid on.
The definitions stack up like this. Gross gaming revenue (GGR) is bets minus wins. NGR takes GGR and subtracts bonuses, payment fees, gaming taxes and, in many deals, an admin fee. AffRoom’s breakdown of casino affiliate deals shows how much those deductions matter: in its example, a 35% RevShare on NGR works out to about 21% of GGR once bonuses, fees and a 10% admin fee come off.
So before you track anything, read your deal. If it pays on NGR, track NGR. If the operator reports deposits but pays on NGR, deposits are a useful early signal, not your revenue.
CPA vs RevShare vs Hybrid: What Each Deal Pays For
Each commission model pays for a different slice of the player’s life, and that decides how far past the FTD your tracking has to reach.
| Deal | What you’re paid for | When the money arrives | Main risk | What you need to track |
|---|---|---|---|---|
| CPA | A fixed amount per qualified FTD | Once, after the hold period | Rejected FTDs that miss the baseline | Registrations, FTDs and qualification |
| RevShare | A share of the NGR each player generates, often for life | Monthly, starting small and growing | Losing months and negative carryover | NGR per player, by month, by source |
| Hybrid | A reduced CPA plus a reduced RevShare | Part upfront, part monthly | Both of the above, at smaller scale | Everything in both rows |
Typical rates vary widely. AffRoom’s 2026 overview puts casino CPAs at roughly $20 to $60 in Tier-3 GEOs and $150 to $400 or more in Tier-1, and RevShare at 25% to 50% of NGR, with hybrids such as $100 plus 25%. Your deal will differ, so use your own terms in the math below.
The One Formula That Settles CPA vs RevShare
To compare a CPA offer with a RevShare offer on the same traffic, work out the NGR per FTD at which they pay the same:
Break-even NGR per FTD = CPA ÷ RevShare rate
With a $100 CPA and a 30% RevShare, the line sits at $333 of NGR per FTD. Players who generate more than that over the deal’s life make RevShare the better choice. Players who generate less make CPA the better choice.
Back to the two sources. At day 90, Source A’s players are at $62 per FTD and Source B’s at $186. Neither has crossed $333 yet, so CPA is still ahead on both. But Source A has flattened out and will likely never get there, while Source B is still climbing. On A, take the CPA. On B, a RevShare or hybrid deal may pay more over a year, and it’s the cohort curve, not the FTD count, that tells you so.
One clause can move that line: negative carryover. Under it, a month where players win more than they lose leaves a negative balance that has to be covered by future profit before you earn RevShare again. A single lucky high roller can wipe out months of commission, so check whether your deal has full, capped or no carryover before you model anything.
Why FTD Counts Mislead
Optimizing on FTDs means optimizing for volume at the top of the funnel. You reward whatever traffic produces the most first deposits, whatever those players do next.
That works on a pure CPA deal, up to a point. Even there, the FTD you see isn’t always the FTD you’re paid for: operators pay CPA only for players who meet the baseline, such as a minimum deposit and some wagering, and bonus hunters who deposit once and vanish often miss it. KYC timing adds another gap, since verification can land between registration and FTD or between FTD and the first withdrawal. Our guide to KYC and AML from a tracking perspective covers how that shifts your numbers.
On RevShare and hybrid deals, the gap gets wider. Two sources with identical FTD counts can produce very different revenue, and you only see it weeks later. If your reports stop at the FTD, you’ll keep scaling the source that looks cheapest on day one.

The Events to Track After the FTD
Lifetime value tracking starts with deciding which events matter, then giving each one its own conversion type in Voluum. A setup that covers most RevShare and hybrid deals tracks four kinds of events:
- Registration. The earliest quality signal, and the denominator for your registration-to-FTD rate.
- FTD. Still your main acquisition event, and the one you count players by.
- Redeposits. The best early sign that a player will stick around. Count them per FTD.
- Revenue. The NGR or commission the operator reports for each player, usually monthly, including negative months.
Voluum’s custom conversions turn each of these into a separate column. Each type also has settings that keep your reports honest. Include in ‘Conversions’ column decides whether an event adds to your conversion count, so redeposits and monthly revenue entries don’t inflate it. Include in ‘Revenue’ column decides whether its payout counts toward campaign revenue and ROI. Send postback to traffic source decides whether the event is passed on to the ad platform.
A practical default: FTDs count as conversions; redeposits are tracked as their own column with no payout and no effect on the conversion count; and revenue entries add to revenue but not to conversions. Your ROI then reflects what you’ve actually earned, and your conversion count still means players.
Getting Revenue Into Voluum: Postbacks vs Conversion Upload
Revenue reaches Voluum in one of two ways: in real time by S2S postback, or in batches by Conversion Upload. Most affiliates end up using both.
Postbacks for Real-Time Events
One detail trips up a lot of setups. By default, Voluum rejects a second conversion with the same click ID as a duplicate, to keep your data clean. A redeposit sent with only the click ID will simply be dropped.
There are two ways to make repeat events count. Add a transaction ID in the txid parameter, unique for each event, such as the operator’s deposit ID. Or send the event as a different conversion type in the et parameter. For redeposits you’ll usually want both, so a postback carries the click ID, the event type and a unique ID for each deposit:
https://your-voluum-domain.com/postback?cid={clickid}&et=redeposit&txid={deposit_id}
The parameter names come from Voluum; the tokens in braces come from your operator or network, so check their names in your partner platform. If the operator can’t fire postbacks for redeposits, you can still upload them later.
Conversion Upload for Monthly Statements
Most RevShare revenue doesn’t arrive by postback. It comes in a monthly statement, often one row per player. Conversion Upload lets you add that data in bulk, with each line holding the click ID, payout, transaction ID, conversion type and conversion time, up to 50,000 conversions per hour.
A few rules make it work for lifetime value tracking:
- Keep the click ID. Ask the operator to store Voluum’s click ID in a sub ID at registration and include it in player-level reports. Without it, there’s nothing to match revenue to.
- Make each line unique. A click ID that already registered a conversion can’t be reused on its own, so add a conversion type such as
revshareand a transaction ID such as the statement month. - Upload losing months too. Payouts can be negative, so a month where a player won money can reduce that source’s revenue instead of being ignored.
- Reconcile carryover separately. Negative carryover is usually applied to your whole account, not to each player. Voluum’s docs suggest a separate correction conversion type that’s excluded from the conversion count, which lets you match your totals to the operator’s statement without distorting player counts.
Set a cadence that matches the operator’s reporting, usually monthly, and upload each statement as it arrives.
Building a 30/60/90-Day Player Value Report in Voluum
Voluum doesn’t have a dedicated cohort view, but its default reporting setting does most of the work. Under conversion registration time reporting, Voluum counts conversions at the time of the visit by default, not when the postback arrives. A deposit made in November by a player who clicked in September shows up in September.
That makes any report filtered to an acquisition window a cohort report. Here’s how to build the 30/60/90-day view:
- Keep the visit timestamp setting. It’s the default. Switching to postback time would scatter a cohort’s revenue across later months.
- Pick the acquisition window. Set the report’s date range to the month (or week) the players clicked, and group by traffic source, campaign or creative.
- Read the right columns. Divide revenue by the FTD column to get revenue per FTD, and redeposits by FTDs to get redeposits per player.
- Snapshot it three times. Run the same report 30, 60 and 90 days after the window closes and save each export. Scheduled reports can deliver the data as a CSV link that updates automatically, which you can connect to Looker Studio, Tableau or Power BI to chart the curves.
The day-30, 60 and 90 columns live in your spreadsheet or dashboard, not inside Voluum. What Voluum guarantees is that every dollar, whenever it arrives, is attributed to the source, campaign and creative that brought the player in. That’s the hard part.
Once you have two or three cohorts, compare sources ranked by FTDs with the same sources ranked by revenue per FTD at day 90. When the order changes, and it usually does, you’ve found the difference between traffic that looks profitable and traffic that is.
Acting on Lifetime Value Before Day 90
Waiting three months for every decision would burn budget, so look for early signals that predict the curve. A redeposit within the first week is often one; the share of FTDs that clear the operator’s baseline is another. Once a few cohorts are in, check which early metric tracked best with day-90 revenue on your traffic, and optimize on that in the meantime.
Feed the good signals back to the source as well. If a platform optimizes toward a postback event, sending it a redeposit or qualified-FTD event through the custom conversion’s postback setting teaches its bidding to find more players like your best ones, rather than more first deposits. For guarding the budget while you wait, our guide to automated rules for iGaming traffic shows how to pause losing placements and get alerts. If your team also runs CRM retention, Voluum data inside iGaming CRMs covers passing the same source data downstream.
For the full metric set, from EPC to cost per FTD, see our affiliate marketing KPIs, and for setting automation thresholds from your margins, break-even ROAS.
Track Every Player From the First Click to the Last Deposit
Voluum keeps each player’s FTD, redeposits and monthly revenue tied to the click that brought them in, so you can see which sources build long-term value and scale those, not just the ones that win on day one. See how Voluum tracks iGaming campaigns.
Frequently Asked Questions
What is player lifetime value?
Player lifetime value (LTV) is the total net revenue a player generates for an operator over the whole relationship, usually measured in net gaming revenue (NGR). For affiliates on RevShare or hybrid deals, it decides how much a player is worth to you, so it’s tracked by acquisition cohort and traffic source rather than stopping at the first deposit.
How is LTV calculated in iGaming?
Add up the NGR a player or group of players generates over a set period, such as 30, 60 or 90 days after the first deposit, then divide by the number of first-time depositors. NGR is gross gaming revenue (bets minus wins) minus bonuses, fees, taxes and any admin fee. Check your deal for the exact formula, since operators define deductions differently.
CPA vs RevShare: which is better for affiliates?
It depends on the players your traffic brings. Divide the CPA by the RevShare rate to find the break-even NGR per FTD, for example $333 with a $100 CPA and a 30% RevShare. Players who generate more than that favor RevShare; players who generate less favor CPA. Cash flow matters too, because RevShare pays slowly.
What is an FTD in iGaming?
An FTD, or first-time deposit, is a player’s first real-money deposit after registering with an operator. It’s the main acquisition event in iGaming and the trigger for CPA payouts, usually only once the player meets the operator’s baseline, such as a minimum deposit amount and some wagering activity.
What is negative carryover?
Negative carryover is a RevShare clause that carries a negative NGR balance into the following months. When referred players win more than they lose, the affiliate earns no RevShare until future profit covers the deficit. Deals without negative carryover reset the balance to zero each month, so the clause can change the value of a deal significantly.