Quick answer: There is no single “average FTD payout” that an operator should copy into every casino affiliate deal. Scaleo’s commission model guide describes an indicative market span from about €50 in less competitive markets to €250 or more in regulated tier-one markets. Your payable CPA should come from the expected value of a qualified player cohort, the acquisition costs and risk you are prepared to carry, and a qualification rule the platform can enforce. A high headline rate with a weak gate can cost more than a lower rate that attracts better players.
“What should we pay per FTD?” sounds like a pricing question. In practice, it is a unit-economics and contract-design question. The same €150 CPA can be affordable for one operator, reckless for another and unattractive to an affiliate buying expensive traffic. A payout benchmark helps you start the conversation; it does not tell you what your program can sustain.
This guide is written for casino and sportsbook operators planning or repricing an affiliate CPA offer. It explains what counts as payable, how to set a rate from cohort economics, what to compare across markets and partners, and how to put the agreement into software. It is a focused companion to our broader RevShare, CPA and hybrid model comparison. If you are evaluating the platform as well as the deal, our iGaming software decision matrix covers the infrastructure behind those offers.
First decide what the CPA actually buys
CPA means cost per acquisition, but an affiliate agreement must define the acquisition event. A registration is not an FTD. A first deposit is not necessarily a qualified FTD. A player can make a minimum deposit, claim a bonus, fail verification, reverse a payment or turn out to be a duplicate account. If the contract and platform treat all first deposits as equally payable, the operator is effectively buying the easiest event to manufacture.
For most operator CPA deals, the payable event should be an attributed player who completes the agreed first deposit and passes the deal’s eligibility conditions. Those conditions can include a minimum deposit, accepted GEO, KYC outcome, unique-player check, permitted traffic source and, where appropriate, a wagering or activity requirement. The exact gate must fit the product, market and partner agreement. A sportsbook program may also need to distinguish a deposit from a settled qualifying bet.
| Event | What it proves | Why it may not yet justify CPA |
|---|---|---|
| Click | A tracked visit was attributed to a partner | No player acquisition has occurred |
| Registration | A player account was created | The player may never deposit or may fail eligibility checks |
| Raw FTD | A first deposit event was received | KYC, reversal, minimum amount and duplicate review may still be pending |
| Qualified FTD | The contract’s eligibility tests passed | This is usually the payable acquisition event, subject to the stated approval process |
| Active or retained player | Later play or value is observed | Useful for repricing and quality review, even when the initial CPA is already payable |
Keep the raw FTD and the qualified FTD in reporting. If the raw event disappears when it fails a gate, managers cannot diagnose a partner’s traffic quality and affiliates cannot understand why an expected payout did not appear. Our FTD qualification guide goes deeper into the event and verification logic.
Contract box: Write the payable event in one sentence before negotiating a rate. Include the attribution rule, minimum deposit, verification conditions, excluded traffic and approval timing. If two managers can read the sentence and reach different payout totals, the deal is not ready to launch.
Use the market range as context, not as a rate card
The €50 to €250+ reference in our commission guide spans very different markets and operator economics. It does not imply that a tier-one offer must be €250, or that €50 is profitable in every lower-cost market. More competition can push acquisition cost up, but revenue quality, product mix, bonuses, taxes, payment costs and the affiliate’s traffic source all affect what the operator can pay.
Also separate affiliate payout from total customer acquisition cost. If you pay a €150 CPA and separately fund creative production, landing pages, sign-up bonuses, account management and tracking operations, the program costs more than €150 per approved player. When teams quote a “target CPA,” make sure they specify whether they mean the commission alone or all costs attributable to the cohort.
The payout itself should be compared with the expected NGR from players acquired under similar conditions. A cohort from a trusted organic review site may retain differently from a burst of paid traffic. A casino cohort cannot automatically stand in for sportsbook, and a launch-month cohort may not represent a mature brand. Do not promise a uniform rate across every GEO simply because a benchmark table has one tidy column.
Set the ceiling from cohort economics
Before naming a rate, define the observation window you use to judge acquired players. Thirty days may be enough to spot a quality problem; it is often too short to understand the full value of a retained player. Use actual comparable cohorts when available, and distinguish realized revenue from a forecast. The rate-setting conversation should use at least three views: a conservative cohort, a base case and a high-performing cohort.
The working calculation is straightforward, even though the inputs require care:
Maximum sustainable affiliate CPA = expected NGR per qualified acquired player over the chosen window − other acquisition and servicing costs per player − required operator contribution − risk reserve.
This is a decision model, not a universal accounting formula. Some costs are already included in the operator’s NGR definition; subtracting them again would be wrong. Document the NGR base before calculating the ceiling. If you pay an affiliate on RevShare elsewhere, avoid comparing a CPA ceiling against a revenue figure that includes another partner’s commission treatment.
Consider a deliberately illustrative case. An operator expects €420 in NGR per qualified player over its chosen review window. It allocates €65 for other acquisition and servicing costs, wants €140 in contribution, and reserves €45 for forecast error and reversals. That leaves a €170 maximum affiliate CPA under those assumptions. A proposed €190 flat offer would need a better-performing cohort, lower costs, a different contribution target or a narrower qualification gate to make commercial sense. It is not justified by a competing program’s headline rate alone.
| Illustrative input | Amount per qualified player | Decision role |
|---|---|---|
| Expected NGR in defined window | €420 | Value basis; verify against comparable cohorts |
| Other acquisition and servicing costs | −€65 | Include only costs not already in NGR |
| Required operator contribution | −€140 | Commercial margin requirement |
| Risk reserve | −€45 | Forecast error, reversals and cohort variance |
| Illustrative maximum affiliate CPA | €170 | Ceiling under these assumptions, not a market benchmark |
Sensitivity matters. If the NGR forecast falls by €60, the same model yields a €110 ceiling. If the operator would still be paying €170, the apparent “market rate” has become an unsupported bet on player value. Run the calculation by partner type or traffic source where the cohort evidence is strong enough, and use a cautious default where it is not.
Decision box: When evidence is thin, buy a smaller test cohort under clear caps and review its qualified FTD rate, NGR and rejection reasons. Paying a premium to an untested source because it promises volume transfers uncertainty to the operator without pricing it.
Compare CPA with RevShare and hybrid on the same cohort
A CPA offer is attractive to affiliates that need predictable payment after an acquisition event. It gives the operator a known initial commission per approved player, but the operator carries more risk if those players have weak lifetime value. RevShare aligns ongoing payout to the agreed revenue base but creates long-term commission exposure and can be harder for paid-media affiliates to finance. Hybrid shares both kinds of exposure.
| Model | When the affiliate earns | What the operator must forecast | Main control question |
|---|---|---|---|
| Flat CPA | On approved qualified acquisition | Whether future player value covers fixed upfront cost | Is the qualification gate strong enough? |
| RevShare | As eligible player revenue accrues | Long-term margin and the contractual NGR or GGR base | Are deductions and negative carryover unambiguous? |
| Hybrid CPA + RevShare | On approved acquisition and later revenue | Both initial cash cost and ongoing revenue share | Can both components be calculated and reconciled together? |
Compare the models using the same player cohort, attribution rule and time window. A flat CPA will look cheap in the first month if the RevShare cohort matures later; a RevShare deal may look cheap before a valuable player starts generating NGR. Our hybrid commission guide explains how to set the two components without hiding total cost.
The chosen model should also match the traffic source. An SEO publisher with a loyal audience may value recurring income. A media buyer may need a predictable acquisition payout to cover spend. That is a commercial discussion, not a reason to relax the qualification event. The operator should be willing to offer different deals where the underlying cohorts justify them, while keeping the rules visible and enforceable.
Qualification rules protect rate integrity
A rate and a gate form one offer. Raising the minimum deposit or requiring a completed activity event can reduce low-quality approvals, but it can also make a deal harder for a legitimate affiliate to promote. The right rule is the one that matches the operator’s risk and can be explained to the partner before traffic arrives.
Start with eligibility: approved GEOs, products and traffic sources. Then define player uniqueness and KYC. Set the minimum deposit in the contract’s currency, and decide how reversals or chargebacks affect approval. If a wagering requirement applies, identify the event and timing precisely. “Active player” is too vague to drive an automated payout. The agreement should also say when a pending event becomes approved and how an affiliate can question a rejection.
Consider the difference between a €150 offer triggered by any €10 deposit and a €150 offer that requires a €20 minimum deposit, verified player and a completed wager. The monetary rate is identical; the operator’s exposure is not. Those figures illustrate two configurations already discussed in our commission model guide. They are not recommendations to copy without reviewing your product and terms.
An overly strict gate can fail too. If the operator asks an affiliate to drive a valuable depositor but withholds CPA on an obscure rule that was not disclosed, the program loses credibility. Transparency is a control for both sides. Show the pending event, its status and the reason for a final exclusion, while protecting private player information.
Caps, overrides and status changes need a single record
Once the basic deal works, operators often add a monthly cap, campaign cap, partner-specific override or temporary higher payout. Each change must have an effective date and a defined precedence rule. Otherwise two dashboards can calculate different commissions for the same FTD. A manual spreadsheet may hide the difference until payout day.
Three cap questions should be answered separately. What is the maximum number or value of CPAs in a month? Can the same player ever trigger a second acquisition commission? Does a time-bound campaign have its own budget boundary? Our CPA commission configuration guide explains why those controls are not interchangeable.
The statement should keep the original candidate event, the qualification decision, the effective commission plan and any later adjustment. If a player passes KYC after a period closes, the operator should know which period receives the payable item. If a payment is reversed after approval, the adjustment should point to the original event. The partner-facing view and finance export must use the same status language, even if they expose different levels of detail.
| Payout control | Failure it prevents | Evidence to save |
|---|---|---|
| Unique-player rule | Double CPA on the same player or cross-brand duplicate | Player reference and attribution history |
| Event qualification | Commission on an ineligible deposit | Rule version, status and reason |
| Rate effective date | Old and new rates applied to the wrong event | Deal version and timestamp |
| Campaign or monthly cap | Unplanned payout exposure | Cap definition, consumed amount and overflow behavior |
| Approval and reversal trail | Unexplained finance difference | Original event, review action and statement adjustment |
Reprice partners using evidence, not only volume
An affiliate who brings 100 FTDs is not automatically more valuable than one who brings 40. Compare qualified rates, cohort NGR, retention, fraud review share and acquisition cost under a consistent window. Segment within the affiliate by SubID or placement where possible. One source can deserve more budget while another requires a cap or investigation.
When a partner requests a higher CPA, agree on what would justify it. A defined test period, enough qualified volume to read the cohort, an eligible traffic source and an agreed review date create a fair negotiation. The operator can offer a tiered rate or a limited override rather than making a permanent program-wide change from one strong week. If the cohort disappoints, the contract should let the parties return to the base arrangement prospectively, without rewriting already approved commissions.
That is also how a new program can compete without copying the largest advertised rate. Fast, understandable approval; reliable attribution; transparent reporting; and a partner portal that shows the status of traffic can be as valuable to a serious affiliate as an inflated headline CPA followed by disputes. The software does not replace a compelling commercial offer, but it can make the offer credible.
How Scaleo supports an operator CPA workflow
Scaleo lets operators assign commission plans by partner and configure qualification conditions at the plan level. The player platform can send the relevant events through server-to-server postbacks so a CPA is triggered when the agreed requirements are met, rather than when a browser happens to load a confirmation page. Operators can inspect traffic and conversion quality, manage caps and overrides, and give affiliates a portal view of their performance and commission status.
For this use case, the valuable part is the connection between deal terms, player event and payable statement. Set the gate in the agreement, implement the matching event logic, then test both approved and rejected paths before traffic is scaled. Scaleo can calculate according to the configured rules; it cannot infer an operator’s true cohort economics or repair a player system that sends the wrong event. Our server-side tracking guide explains why that event contract matters.
If you are evaluating Scaleo for a CPA program, bring one of your harder deals to the demonstration: multiple GEOs, a partner override, a monthly cap, a late KYC approval and a reversal. The answer should be a reproducible statement and a clear partner-facing status, not a promise that the standard plan can be “customized later.”
Eight acceptance tests before launching a CPA offer
Run these tests with the affiliate lead, risk team, integration owner and finance reviewer. Each should have a known expected outcome. Save the event ID and resulting statement line for sign-off.
- Approved player: A valid attributed player completes the minimum deposit and all other requirements; one CPA appears at the correct rate.
- Below-threshold deposit: The raw FTD remains visible, but no payable CPA is created until the agreement’s condition is met.
- Duplicate player: A repeated deposit or duplicate account cannot create a second acquisition commission.
- Wrong GEO or source: Ineligible traffic is flagged according to the stated policy with a reason visible to the reviewer.
- Late verification: A pending event becomes approved only when the verification result arrives, with both timestamps retained.
- Rate change: Events on either side of an override’s effective date use the intended version of the deal.
- Cap reached: The platform applies the defined campaign or period cap without silently moving excess events into a different payout.
- Reversal or correction: An adjustment refers back to the original approved event and reconciles in the affiliate and finance views.
An operator who cannot pass these tests should not compensate by checking every payout manually forever. Fix the source event, rule or statement design that causes the exception, then retest. The point of affiliate software is to make a complex commercial promise repeatable.
Frequently asked questions
What is the average casino affiliate payout per FTD?
There is no universal amount. Scaleo’s existing commission model guide uses roughly €50 in less competitive markets to €250+ in regulated tier-one markets as an indicative span. The sustainable payout for your program depends on qualified-player value, other acquisition costs, contribution requirements, traffic quality and the qualification gate. Treat the range as market context, not a rate to copy.
Is CPA paid on every first deposit?
Only if the operator’s agreement defines every first deposit as payable, which is usually a risky design. Most serious CPA deals distinguish a raw FTD from a qualified FTD that passes deposit, verification, uniqueness and source rules. The platform should record both events and the approval reason.
How do I calculate the maximum CPA I can afford?
Start with expected NGR per qualified acquired player over a declared window. Subtract relevant costs not already included in NGR, the contribution the business requires and a reserve for uncertainty. Check conservative and base cohorts, not just the best-performing affiliate. If the proposed payout exceeds the resulting ceiling, revisit the economics or the deal structure.
When is a hybrid deal better than flat CPA?
Hybrid can help when an affiliate needs some predictable acquisition income but both parties also want upside tied to player value. The operator must model and report the upfront CPA and ongoing RevShare together. A hybrid offer is not automatically cheaper; its lifetime cost depends on the cohort and the precise RevShare base.
Should different affiliates receive different CPA rates?
They can, if differences reflect evidence such as source quality, GEO, product, cohort value or a negotiated test. Keep partner-specific plans, effective dates and caps explicit. A rate exception made in a conversation but not reflected in the platform is a future payout dispute.
A defensible payout is a promise your system can keep
The strongest CPA offer is not necessarily the highest advertised number. It is a rate the operator can afford on the players it actually receives, attached to a qualification rule partners understand and a statement both sides can verify. Use benchmark ranges to frame negotiations, then let your own cohort data set the ceiling.
Scaleo is built to run the operational side of that promise: attribute the player, apply the configured commission plan, show the status and reconcile the payout. Use the commission model guide for the wider choice between CPA, RevShare and hybrid, and use the tests above when you put the selected deal into production.
