For iGaming operators running RevShare or Hybrid affiliate programs, GGR and NGR are not interchangeable revenue bases — they are different commission foundations that produce materially different payout outcomes from the same player activity. Choosing the wrong one, or misconfiguring the deduction logic, costs real money at month-end. This guide is for operators who need to understand what each definition means commercially, when to use which structure, and what your affiliate platform must do correctly for either to work.
⚡ TL;DR — GGR vs NGR in iGaming Affiliate Commission Models
- GGR and NGR are different commission bases that produce wildly different payout outcomes from the same player activity. Operators frequently misconfigure one while intending the other, especially at program launch when the deduction logic hasn’t been fully stress-tested.
- NGR deducts bonuses, chargebacks, payment processing fees, and sometimes taxes from GGR before applying the RevShare rate. A 30% NGR deal and a 30% GGR deal can differ by 15–20 percentage points in actual affiliate earnings on a mature player base.
- The choice of revenue base signals something about program structure, fraud risk tolerance, and affiliate partner quality. Programs built on GGR attract a different affiliate profile than programs built on NGR.
- Platform-level enforcement matters more than contract language. If your affiliate platform can’t apply deduction rules at the player event level, your NGR calculations will drift. We see this consistently when operators migrate from platforms that calculate commissions at report-generation time rather than at event ingestion time.
Most posts explaining GGR vs NGR treat the topic like a glossary entry. Two definitions, a comparison table, done.
That’s not what operators actually need. What operators need is the answer to the commercial question underneath the vocabulary question: which revenue base should your affiliate program use, under what conditions, and what does the platform have to do correctly for either definition to mean what your contracts say it means?
We’ve configured both commission architectures across hundreds of operator deployments. The definitional question resolves quickly. The operational consequences take much longer to untangle.
What GGR and NGR Actually Measure
Gross Gaming Revenue is the simplest formulation: GGR = Total Player Wagers − Total Player Winnings.
If a casino’s players collectively wager €1,000,000 in a month and win back €960,000, GGR is €40,000. No adjustments. No deductions. The affiliate’s 30% RevShare on GGR in this scenario is €12,000.
Net Gaming Revenue subtracts operator costs from that GGR figure before the commission rate applies. The standard NGR formula is: NGR = GGR − Bonuses − Chargebacks − Payment Processing Fees − (sometimes) Applicable Taxes and Regulatory Levies.
Using the same €40,000 GGR but subtracting €8,000 in welcome bonuses, €1,500 in chargebacks, and €800 in processing fees produces NGR of €29,700. The same 30% RevShare rate now produces a commission of €8,910 — roughly 26% less than the GGR equivalent, for the same player activity.
| Metric | GGR Scenario | NGR Scenario |
|---|---|---|
| Player wagers | €1,000,000 | €1,000,000 |
| Player winnings | €960,000 | €960,000 |
| GGR | €40,000 | €40,000 |
| Bonus deductions | — | −€8,000 |
| Chargeback deductions | — | −€1,500 |
| Processing fee deductions | — | −€800 |
| Commission base | €40,000 | €29,700 |
| RevShare rate | 30% | 30% |
| Affiliate commission | €12,000 | €8,910 |
| Difference | €3,090 — same player activity, same stated rate, different outcome | |
That gap is not abstract. Over a year, across a meaningful affiliate partner, it’s the difference between program economics that work and program economics that quietly destroy margin.
The Deduction Categories That Actually Move the Needle
Not all NGR deductions are equal in their financial impact. Understanding which deductions dominate the NGR calculation informs both how you structure the deal and what you need your platform to track.
| Deduction Type | Typical Impact | Operator Notes | Platform Requirement |
|---|---|---|---|
| Bonus costs | Largest deduction — 40–60% of total NGR drag for high-bonus programs | Affiliates on GGR deals effectively subsidize bonus costs without knowing it | Per-player bonus tagging at award and redemption events |
| Chargebacks | Volatile and seasonally unpredictable | A single geo with elevated payment fraud can produce months where chargeback deductions exceed RevShare liability | Per-player chargeback attribution, not aggregate pool allocation |
| Processing fees | Consistent but underestimated — 1.5–3% of transaction value in European markets | Some operators exclude fees as a goodwill concession; must be contractually explicit either way | Configurable per-deal: include or exclude per affiliate contract |
| Tax deductions | Jurisdiction-dependent — UK RGD, Italian concessione, Swedish GBT all vary | Affiliates in multi-jurisdiction programs often discover effective RevShare rate varies by market | Per-jurisdiction tax deduction rules, not a global formula |
Operator rule: The commission model you choose is only as precise as the deduction categories you’ve defined, documented, and configured in your platform. A contract that says “NGR” without specifying which deductions apply is not an NGR contract — it’s a dispute waiting to be scheduled.
GGR Deals: When They Make Sense and Who They Attract
A GGR-based commission is simpler to explain, easier for affiliates to model, and carries no ambiguity about what drives earnings. The affiliate knows that player wagers minus player winnings equals the base their percentage applies to. No bonus adjustments, no chargeback deductions, no platform fee allocations.
Programs using GGR as their commission base tend to attract established affiliates with verified traffic quality — partners who can confidently predict player LTV because they’ve seen their own traffic performance across multiple programs. These affiliates don’t need NGR protection because their traffic doesn’t generate the chargeback rates and bonus abuse patterns that make NGR deductions significant.
GGR also makes sense for operators with tight bonus controls. If you’re running a low-bonus or bonus-free program, or a program targeting a niche with lower chargeback risk, the gap between GGR and NGR narrows substantially. Paying affiliates on GGR in that environment isn’t materially more expensive than NGR — and it’s a better affiliate recruitment argument.
The risk of GGR at scale is that the operator absorbs all acquisition cost risk. If a high-volume affiliate sends a surge of bonus abusers or chargeback-heavy depositors, the GGR calculation sees that traffic as normal player activity generating normal commission liability, even while the actual economics of that traffic are sharply negative for the operator.
GGR is not a charity arrangement for affiliates. It’s a simplicity trade-off that works when traffic quality is predictable and bonus exposure is controlled.
NGR Deals: The Operational Complexity You’re Taking On
NGR is the more commercially defensible commission base for most operator programs at scale. It aligns affiliate incentives with actual program economics — affiliates are only earning well when the operator is earning well, and the costs that reduce operator margin are shared costs rather than operator-only costs.
The alignment argument is real. An affiliate whose RevShare is calculated on NGR has a direct financial interest in the quality of the traffic they send. Bonus-hunting, chargeback-prone traffic reduces their commission as well as the operator’s margin. Over time, this should select for affiliates with better traffic quality.
Should. In practice, this alignment only materializes if the NGR calculation is transparent and the platform reports clearly on which deductions reduced commission. Affiliates who see their NGR balance but can’t understand why it diverges from the GGR they’d expect will — reasonably — challenge the calculation, assume the operator is manipulating the deductions, and eventually move their traffic to a competitor program.
The operational demands of NGR are significant. You need per-player cost attribution, not aggregate deduction pools. If your platform calculates NGR by taking total bonuses issued and dividing them across affiliate-referred players by some pro-rata formula, your NGR calculation is wrong. An affiliate who referred a player who never used a bonus is being charged a share of bonuses issued to players they didn’t refer. We see this consistently in programs that migrated from spreadsheet-based commission reconciliation or from platforms where cost attribution is an afterthought rather than an architectural feature.
Per-player attribution requires that every bonus award, every chargeback event, and every processing cost is tagged at the player level and rolled up to the affiliate who referred that player. That’s not an analytics task. It’s a data architecture task that has to be correct at event ingestion, not corrected at report time.
Platform evaluation question: Ask your affiliate software vendor specifically whether NGR deductions are calculated at the player level or applied as aggregate pool distributions across a cohort. If they can’t answer that question directly, your NGR calculation is running on approximations — and those approximations will produce affiliate disputes at exactly the months when your program economics are already under stress.
The Hybrid Approach: GGR With an NGR Ceiling
Some operators use a hybrid structure that gives affiliates GGR-based simplicity while protecting the program from catastrophic downside: RevShare calculated on GGR, but with a clause that caps commission liability to a defined percentage of NGR.
The structure typically reads as: “RevShare calculated at X% of GGR, subject to a maximum of Y% of NGR.” If NGR for a player cohort collapses due to heavy bonus redemption, the commission cap triggers and the affiliate’s earnings are reduced even though the GGR calculation would suggest higher earnings.
This protects operators against the bonus-surge scenario without requiring affiliates to understand the full complexity of the NGR calculation. The GGR component is their primary calculation; the NGR cap is visible only when the program economics are under genuine stress.
The downside is that affiliates don’t always see the cap clearly at program signup, which creates disputes when it triggers. And when it triggers, it’s almost always in months where something else has also gone wrong with program economics — making the conversation with the affiliate harder than it would be in a neutral environment.
We’d argue this structure is underused relative to how well it manages the actual risk. The reason it doesn’t appear more often is that configuring a conditional cap within a RevShare calculation requires a platform that supports compound commission logic — a GGR base, a secondary NGR calculation, and a conditional override rule that activates when the ratio crosses a threshold. Not all platforms handle this natively.
Negative Carryover: The Decision That Follows the NGR Choice
If your program uses NGR, negative carryover is a decision you cannot defer. It will come up.
Negative carryover occurs when a player on an affiliate’s NGR account has a winning month — player winnings exceed wagers in that period, producing a negative GGR, which produces a negative NGR, which produces a negative commission balance for the affiliate. Under some contract structures, that negative balance carries forward and must be recovered from future positive months before new commission accrues.
| Negative Carryover ON | Negative Carryover OFF | |
|---|---|---|
| Player wins €5,000 in month 1 | Affiliate balance goes negative; no commission paid | Month resets to zero; no commission paid but no debt created |
| Player generates €8,000 NGR in month 2 | First €5,000 recovers the carryover deficit; affiliate earns commission on €3,000 | Affiliate earns commission on the full €8,000 |
| Player churns after month 2 | Operator recovers more of the winning-streak cost | Operator absorbs month 1 variance entirely |
| Affiliate relationship impact | High-performing affiliates will negotiate to remove it | Attracts better partners; increases LTV on quality traffic |
| Best used when | Lower-volume programs with concentrated per-affiliate risk | High-volume programs where LTV smooths variance at scale |
Both positions are commercially coherent. Programs targeting top-tier affiliates with consistent high-volume traffic can often remove negative carryover as a negotiating point without material P&L impact, because LTV smooths out variance at scale. Programs running smaller traffic counts across more affiliates see individual variance more clearly and carry more concentrated risk per affiliate relationship.
The platform implication: if you’re offering no-negative-carryover to select affiliates while maintaining it as a default, your commission engine needs to handle this as a per-affiliate configuration, not a program-wide setting. Toggling it globally is the wrong architecture.
What Your Platform Has to Get Right
The GGR vs NGR decision is made at the commercial level. But it lives or dies at the platform level. Here’s the operational checklist.
Platform Requirements for Accurate NGR Commission Calculation
| Requirement | What It Means in Practice | What Breaks Without It |
|---|---|---|
| Per-player cost attribution | Every bonus, chargeback, and fee tagged to the specific player who generated that cost | Affiliates charged for deductions from players they didn’t refer; NGR figures wrong by construction |
| Event-time calculation | Commission accrual updates when the event occurs — not batched at month-end report generation | Dashboard commission balance diverges from final amount; affiliates notice mid-month discrepancies |
| Deduction transparency in reporting | Affiliates see full breakdown: GGR → bonus deductions → chargeback deductions → fee deductions → NGR | Every negative NGR movement generates a support request; trust erodes |
| Configurable deduction categories per deal | Different affiliates can have different deduction structures enforced by the platform | Single global NGR formula applied to all accounts regardless of contract terms |
| Per-affiliate negative carryover | Carryover setting configurable at the individual affiliate level | Toggling globally forces operators to choose one policy for all partners |
We, the team behind Scaleo, built the commission engine specifically to handle compound models at this level of granularity — not because it was technically interesting, but because we watched operators run into exactly these reconciliation problems at month-end when the platform couldn’t hold the specificity the commercial agreements required.
The Affiliate Conversation You’ll Have to Have
Switching a program from GGR to NGR — or vice versa — is one of the more charged affiliate management situations an operator can create. Affiliates on existing GGR deals who are asked to migrate to NGR will almost always ask for a rate increase to compensate for the deduction drag. The negotiation is cleaner if you can show them the expected deduction structure in advance: here is the average bonus deduction rate across our program, here is the average chargeback rate, here is what 30% NGR would have produced versus 30% GGR over the last six months on comparable traffic.
That conversation requires data. It requires knowing your average NGR-to-GGR ratio by traffic segment, by product vertical, by acquisition channel. Programs that can’t produce that data are either guessing at fair rate adjustments or offering increases they can’t justify — both of which create problems down the line.
The transparency question here connects to something broader about how the affiliate-operator relationship is structured. Operators who can share clear, auditable revenue base calculations with their affiliate partners build different relationships than operators who treat the NGR formula as proprietary information to be defended. The mistrust that accumulates when affiliates can’t verify what they’re being paid on is one of the structural inefficiencies in iGaming affiliate programs that the industry has been slow to address. It’s not purely a platform problem — it’s a culture problem. But the platform has to make transparency technically possible before it can be commercially practiced.
Which Revenue Base Should You Use?
Not a hedge — a framework for the decision.
| Use this model when… | GGR | NGR | Hybrid GGR with NGR Cap |
|---|---|---|---|
| Affiliate profile | Established partners with verified traffic quality | Mixed or unverified partner base | Established partners where bonus surge risk exists |
| Bonus structure | Controlled, low-bonus, or bonus-free program | Aggressive acquisition bonusing | Variable bonus exposure by campaign period |
| Fraud / chargeback risk | Low-risk geos and payment methods | Elevated risk where cost-sharing is needed | Normal conditions, protection for spikes |
| Platform capability required | Basic — GGR calculation is straightforward | High — per-player deduction attribution, event-time calculation, configurable categories | High — compound commission logic with conditional cap override |
| Affiliate relationship impact | Stronger recruitment argument; top affiliates prefer it | Acceptable if deduction transparency is clear | Affiliate-friendly in normal months; cap must be disclosed upfront |
| Wrong to use when | Bonus abuse or chargeback risk is elevated | Platform can’t calculate NGR at player level accurately | Platform doesn’t support compound commission logic natively |
The wrong answer is deploying NGR because it sounds more sophisticated without having the data infrastructure to calculate it correctly. An NGR calculation running on aggregate deductions and batch reconciliation is worse than GGR — it’s inaccurate and opaque simultaneously.
The Commission Architecture Test
Your affiliate platform should be able to answer this question precisely: for any affiliate, in any month, show the GGR figure, every deduction applied, the deduction category each one falls under, the player each deduction is attributed to, and the final NGR commission base. If it can’t produce that breakdown on demand, you don’t have an NGR program — you have an approximation wearing NGR labels.
Scaleo’s commission engine enforces deductions at the player event level, supports configurable deduction categories per affiliate deal, and surfaces the full calculation breakdown in affiliate-facing reporting.
Frequently Asked Questions: GGR vs NGR Commission Models
What is the difference between GGR and NGR in iGaming affiliate programs?
GGR (Gross Gaming Revenue) equals total player wagers minus total player winnings — it measures the raw revenue generated before any operator costs are deducted. NGR (Net Gaming Revenue) deducts operator costs from GGR before the affiliate commission rate applies. These costs typically include bonuses awarded to players, chargeback losses, payment processing fees, and in some jurisdictions, applicable gaming taxes. A 30% RevShare on NGR is materially different from a 30% RevShare on GGR — NGR produces lower commission amounts in most program environments because the deduction stack reduces the base the percentage applies to.
Which is better for affiliates: GGR or NGR commission?
GGR is generally better for affiliates in pure payout terms, because the commission base is higher before any operator cost deductions. However, for affiliates with strong, consistent traffic quality, the practical difference narrows — their players don’t generate the bonus abuse or chargeback volume that makes NGR deductions significant. NGR at a higher stated rate can outperform GGR at a lower stated rate if the deduction drag is low. Affiliates evaluating programs should ask for historical NGR-to-GGR ratios by traffic type before comparing stated RevShare rates.
What costs are deducted from GGR to calculate NGR?
Standard NGR deductions include: bonuses awarded to and redeemed by referred players (welcome bonuses, reload bonuses, free spin values), chargeback losses attributed to referred players, payment processing fees on deposits from referred players, and in some contract structures, applicable gaming taxes and regulatory levies. The specific deduction categories must be defined explicitly in the affiliate contract — programs that leave NGR deductions vague create audit disputes when the final calculation diverges from affiliate expectations.
What is negative carryover in RevShare affiliate programs?
Negative carryover applies when a player on an affiliate’s NGR account wins more than they wager in a given period, producing negative NGR for that player in that month. Under negative carryover terms, that negative balance carries forward to future periods and offsets positive NGR before new commission accrues. Programs without negative carryover reset each month — negative player months don’t burden future earnings. Operators use negative carryover to protect against variance in player outcomes; affiliates typically negotiate to remove it for high-value traffic relationships.
How do iGaming affiliate platforms calculate NGR?
Platforms differ significantly in NGR calculation architecture. The correct approach calculates NGR at the player level — tagging each bonus cost, chargeback event, and processing fee to the specific player who generated it and rolling that up to the referring affiliate. The incorrect approach applies aggregate deductions across a pool of players on a pro-rata basis, which misattributes costs and produces NGR figures that can’t be audited. Operators evaluating affiliate platforms should ask specifically whether NGR calculation is event-time (updated as costs occur) or batch-time (applied at report generation), and whether affiliate dashboards expose the deduction breakdown or only the final NGR figure.
