The iGaming Software KPI Glossary Every Operator Needs in 2026: GGR, NGR, RTP, CAC, LTV and More
What is GGR in iGaming and why does every contract reference it?
GGR stands for Gross Gaming Revenue. It equals total wagers placed minus total winnings paid to players, across a defined period. No costs, no bonuses, no fees are deducted yet. GGR is the universal top-line metric in iGaming software reporting, used in platform revenue-share agreements, licensing fee calculations and regulator filings worldwide.
When you sign a white-label or turnkey agreement with a platform provider like SoftSwiss or EveryMatrix, the revenue-share percentage they charge is almost always applied to GGR. A 15% platform fee on GGR sounds modest until you realize that number comes before you pay your payment processor, your affiliate, or your bonus liability. Operators who negotiate on GGR without modeling their full cost stack routinely find their actual margin is negative in the first six months.
Regulators also anchor their reporting requirements to GGR. Curaçao's revised 2024 framework under the National Ordinance on Offshore Games of Hazard requires licensees to report GGR monthly. The MGA in Malta uses GGR as the basis for its compliance contribution levy, which runs on a tiered scale. MINCETUR in Peru and Coljuegos in Colombia both require certified GGR declarations for tax assessment. The number is not just an internal metric; it is a legal figure with audit implications.
One practical trap: GGR can look strong while your business is hemorrhaging cash. A casino generating $500k GGR per month with a 60% bonus-to-GGR ratio, a 5% payment processing cost and a 20% platform fee is running at a loss. That is why sophisticated operators track GGR only as the starting point, then immediately layer in the deductions to get to NGR.
What is NGR and how is it calculated differently across platforms?
NGR (Net Gaming Revenue) is GGR minus bonuses redeemed, payment processing fees, chargebacks and sometimes affiliate costs, depending on the contract definition. It is the closest thing to actual earned revenue before overhead. The problem is that 'NGR' is not a legally standardized term, so its definition varies meaningfully between platform vendors and licensing jurisdictions.
The most common NGR formula in iGaming software back-offices is: NGR = GGR minus bonus costs minus payment fees. Some operators also subtract affiliate commissions to get a tighter profitability view, though many affiliate networks prefer to calculate their CPA or revenue-share on GGR to avoid disputes over what counts as a 'cost.' If you are negotiating a revenue-share deal with an affiliate network, nail down whether their percentage applies to GGR or NGR before you sign. The difference on a $1M GGR month with 35% bonus costs is roughly $350,000 in calculation base.
Platform providers define NGR differently in their dashboards. SoftSwiss's back-office, for instance, lets operators configure which cost categories feed into the NGR calculation. EveryMatrix's CasinoEngine reports GGR natively and leaves NGR modeling to the operator's BI layer. Digitain and BetConstruct both include configurable NGR dashboards, but the default setups do not always include payment gateway fees unless you map them manually. Always test your platform's reporting against a manual calculation for the first 30 days of live operation.
From a regulatory standpoint, the UK Gambling Commission uses 'Net Revenue' in its fee structure, which is broadly equivalent to NGR but with specific exclusions defined in its Licence Conditions and Codes of Practice. MGA uses GGR for its compliance levy but expects operators to maintain NGR-level records for AML transaction monitoring. Understanding which metric each regulator cares about prevents expensive reconciliation errors at audit time.
| Metric | Bonuses Deducted | Payment Fees Deducted | Affiliate Costs Deducted | Typical Use Case |
|---|---|---|---|---|
| GGR | No | No | No | Platform revenue-share base, regulator filings, top-line reporting |
| NGR (standard) | Yes | Yes | No | Internal P&L, operator margin tracking, some affiliate deals |
| NGR (full-cost) | Yes | Yes | Yes | True profitability view, investor reporting, unit economics modeling |
| Net Revenue (UKGC) | Yes (specific rules) | Partial | No | UKGC licence fee calculation |
What is RTP and what does hold percentage mean for casino operators?
RTP (Return to Player) is the percentage of all wagered money a game pays back to players over a statistically large sample. A 96% RTP slot returns $96 for every $100 wagered on average. Hold percentage is simply 100 minus RTP. Operators care about hold because it determines theoretical revenue per dollar wagered, and regulators enforce minimum RTP floors to protect players.
Game studios publish certified RTP figures in their technical sheets. Pragmatic Play, Play'n GO, NetEnt and most major studios certify their RTP through independent labs like BMM Testlabs, GLI (Gaming Laboratories International) or eCOGRA. When you integrate games via an aggregator like Relax Gaming or Pariplay, you receive access to these certified sheets. The certified RTP is the figure regulators check. If you are running in a licensed jurisdiction and a player complaint triggers a game audit, the regulator will compare actual game performance against the certified RTP over a defined sample size.
Hold percentage is where operators sometimes misread their own data. A slot running at 4% hold (96% RTP) does not mean every $10,000 wagered generates $400 GGR. Volatility matters enormously. High-variance games like Pragmatic Play's Gates of Olympus can swing wildly over short session samples. You might generate 8% hold one week and 1% the next. The theoretical hold only stabilizes over millions of rounds. This is why experienced operators monitor actual hold versus theoretical hold in their game analytics, and flag games running consistently outside their certified range for investigation.
Regulatory minimums vary by jurisdiction. The MGA mandates a minimum 92% RTP for slots. The UKGC requires operators to publish RTP information and does not set a hard minimum, but the practical floor from certified studios is around 94-96%. New Jersey's Division of Gaming Enforcement requires a minimum 83% RTP for online slots. Curaçao does not specify a statutory minimum but requires operators to use certified games. If you are building a game portfolio, filtering by RTP floor compliance per jurisdiction is a necessary step during your content integration phase.
| Jurisdiction / Regulator | Minimum RTP (Slots) | Certification Required | Notes |
|---|---|---|---|
| MGA (Malta) | 92% | Yes (accredited lab) | Applies to all RNG games |
| UKGC (UK) | No statutory minimum | Yes (accredited lab) | Operators must publish RTP; studios typically 94-96% |
| New Jersey DGE (US) | 83% | Yes (GLI or approved lab) | One of the lower US state floors |
| Michigan MGCB (US) | 75% (table games), no slot floor published | Yes | Operators should verify current rules directly |
| Curaçao (revised 2024) | No statutory minimum | Yes (certified games required) | Game certification via approved lab mandated |
| Colombia (Coljuegos) | 85% | Yes | Applies to licensed online operators |
How do CAC and LTV apply to iGaming software and marketing decisions?
CAC (Customer Acquisition Cost) is total marketing spend divided by the number of new depositing players acquired in a period. LTV (Lifetime Value) is the total NGR a player generates over their active lifetime. The ratio between them determines whether your acquisition strategy is economically rational. In iGaming, a healthy LTV:CAC ratio is generally 3:1 or higher, though this varies by market and product type.
Most iGaming software platforms surface CAC and LTV data in their CRM and analytics modules, but the quality of the data depends heavily on how you configure player segmentation and attribution. If you are running a white-label through a platform like SoftSwiss's SOFTSWISS Casino Platform or EveryMatrix's EmaxSys, you will have access to cohort-level LTV reporting. The challenge is that raw platform data often conflates different acquisition channels, making it hard to calculate channel-specific CAC. You need UTM tracking, a proper affiliate management system (Income Access, MyAffiliates or similar) and ideally a BI layer to get clean numbers.
In practice, iGaming CAC varies enormously by jurisdiction and channel. Organic SEO acquisition in a mature market like the UK can yield a CAC of $50-150 for a depositing player. Paid search in New Jersey or Pennsylvania, where competition from DraftKings, BetMGM and FanDuel is intense, can push CAC above $400-600 for a first-time depositor. Affiliate CPA deals in LATAM markets like Mexico or Argentina currently range from $80-200 per depositing player, depending on the network and vertical. These are directional ranges, not guarantees. Your actual CAC will depend on your brand, bonus offer and the quality of your onboarding funnel.
LTV is harder to model before launch because you have no churn data. Most operators use industry benchmarks as a starting point: average player LTV in a competitive European market might be $300-600 NGR over 12 months for a slots-focused casino. VIP players can generate 10-20x that figure. The key insight is that LTV is not static. Your retention team, bonus strategy, VIP program and payment experience all directly affect LTV. Operators who treat LTV as a fixed input rather than a managed output leave significant revenue on the table.
What other iGaming KPIs should operators track from day one?
Beyond GGR, NGR, RTP, CAC and LTV, operators should track First Time Depositor rate (FTD%), Average Revenue Per User (ARPU), Churn Rate, Bonus Cost Ratio, and Payment Conversion Rate from day one. These metrics collectively tell you whether your platform, game content, bonus engine and payment stack are performing. Ignoring any one of them creates blind spots that compound over time.
FTD rate is the percentage of registered players who make a first deposit. Industry benchmarks vary, but a well-optimized onboarding flow with a compelling welcome bonus should convert 25-45% of registrations to first deposits in a competitive market. If your FTD rate is below 20%, the problem is almost always one of three things: a friction-heavy KYC process, a payment method mismatch for your target market, or a welcome bonus that doesn't compare favorably to competitors. All three are fixable, but you need the metric to know you have the problem.
Bonus Cost Ratio (bonuses paid divided by GGR) is a metric operators consistently underestimate pre-launch. New casino operators often set aggressive welcome bonuses to compete, and bonus costs of 40-60% of GGR in the first three months are not unusual. That ratio needs to compress toward 15-25% as the player base matures and organic retention improves. If it doesn't, your bonus strategy is subsidizing players who churn immediately after clearing wagering requirements. Platforms like Optimove and FastTrack CRM let you model bonus ROI by player segment, which is the only way to run a rational bonus program at scale.
Payment Conversion Rate measures the percentage of deposit attempts that succeed. This is a critical iGaming software metric that most operators don't track granularly enough. A payment stack that converts 85% of deposit attempts versus one that converts 70% is a 15-point difference that directly flows through to GGR. Payment orchestration platforms like Nuvei, Payroc or Worldpay's iGaming vertical can route transactions dynamically to maximize approval rates. In markets with high card decline rates (many LATAM and emerging markets), offering local payment methods like PIX in Brazil, OXXO in Mexico or PSE in Colombia is not optional; it is a conversion necessity.
How does iGaming software report these KPIs and what should operators look for in a back-office?
A modern iGaming back-office should surface GGR, NGR, RTP variance, FTD rate, ARPU and bonus costs in real-time dashboards with drill-down by game, player segment, geography and acquisition channel. If your platform can't do this natively, you will need a third-party BI tool. Platforms that bury KPIs behind export-only reports are a serious operational liability.
The back-office reporting capability is one of the most underweighted factors in platform selection. Operators evaluating SoftSwiss, EveryMatrix, Digitain or BetConstruct during a demo tend to focus on the player-facing UI, the game library and the payment integrations. The back-office gets a 20-minute walkthrough at the end. That is backwards. The back-office is where you run your business. You need to see real-time GGR by game category, NGR with configurable cost deductions, player lifetime reports filterable by cohort, and bonus redemption analytics that show wagering requirement completion rates.
SoftSwiss's back-office is widely regarded as one of the more operator-friendly in the white-label space, with configurable reporting and a reasonably clean BI layer. EveryMatrix's BackOffice module is robust but can require technical configuration to surface NGR-level data correctly. Turnkey builds on custom tech stacks (often used by larger operators) typically integrate with dedicated BI tools like Tableau, Looker or Metabase for KPI reporting, giving more flexibility but requiring internal data engineering resources.
One specific thing to demand from any platform vendor during due diligence: ask them to demonstrate how their system calculates NGR and whether bonus costs are deducted in real-time or batched. Batched bonus accounting can create a 24-48 hour lag in your NGR view, which matters enormously during a promotional campaign when you need to monitor spend velocity. Also ask whether RTP variance reporting is included natively or requires a separate game analytics integration. Some platforms rely on studio-side RTP reporting, which is not granular enough for a serious operation.
What is the difference between theoretical RTP and actual hold, and why does it matter for game selection?
Theoretical RTP is the certified long-run payout percentage calculated by the game studio and verified by a testing lab. Actual hold is what your casino actually retained from that game over a specific period. They will almost never match in the short term due to variance. The gap between them is a key diagnostic tool: consistent over-performance suggests data integrity issues; consistent under-performance may indicate a game configuration error.
When you integrate a game like Book of Dead from Play'n GO (certified RTP around 96.21%) and run it for a month, your actual hold might be anywhere from 2% to 8% depending on session volume and variance. That range is normal. The issue arises when actual hold deviates from theoretical hold consistently over millions of rounds. At that point, you have either a game configuration problem (wrong RTP version loaded, which can happen when aggregators manage multiple RTP variants), a data pipeline error in your reporting, or in rare cases, a game integrity issue worth escalating to the studio or aggregator.
Most major game studios offer multiple RTP variants of the same title. Pragmatic Play's Wolf Gold, for example, has been available in 84%, 91.5% and 96% RTP configurations depending on the jurisdiction. When you license games through an aggregator, confirm which RTP variant is being served in each market. Serving a lower-RTP variant in a jurisdiction that mandates a minimum floor is a compliance violation. This is not a hypothetical risk; it has resulted in regulatory penalties for operators in multiple European markets.
For game selection strategy, actual-versus-theoretical hold data helps you identify which titles drive the best risk-adjusted GGR. High-volatility games with wide hold variance can be problematic for smaller operators with limited bankroll buffers. A game running at 2% actual hold for three consecutive months is costing you revenue relative to theoretical, and while variance will eventually correct, you need the cash flow to survive the correction period. This is a practical argument for building a balanced portfolio across volatility profiles rather than loading up on high-variance jackpot titles from day one.
How do these KPIs connect to iGaming licensing requirements and compliance obligations?
GGR, RTP and player transaction data are not just internal metrics; they are regulatory deliverables in every serious licensing jurisdiction. Curaçao, MGA, UKGC, Coljuegos and US state regulators all require some form of certified reporting tied to these figures. Building your KPI infrastructure to meet the most demanding jurisdiction you plan to enter is the right approach, even if you launch offshore first.
Under the MGA's Gaming Compliance and Enforcement Regulations, licensees must submit monthly compliance reports including GGR by product vertical. The MGA also requires operators to maintain game transaction logs at the individual round level for a minimum of five years, which means your iGaming software platform needs robust transaction archiving. If your platform stores logs in a format that can't be exported in the MGA's required schema, you will face a compliance gap at your first audit. This is worth verifying explicitly during platform due diligence, not after go-live.
In the US, state-by-state requirements add another layer. New Jersey's DGE requires monthly financial reports with GGR broken down by game type (slots, table games, poker). Pennsylvania's PGCB has similar requirements. Both require certified RTP data from approved testing labs for every game offered. If you are building toward a US state licence, your game aggregation partner needs to have GLI or BMM certification relationships already in place. Aggregators like Pariplay, Relax Gaming and White Hat Gaming have this infrastructure. Smaller aggregators may not.
AML compliance also intersects with KPI tracking. Financial intelligence units in most jurisdictions require operators to flag unusual player GGR patterns, large single-session wins relative to deposit history, and rapid deposit-withdrawal cycles. Your CRM and KPI system needs to feed into your AML monitoring layer. Platforms like BetConstruct and SoftSwiss have built-in AML alert modules, but the quality of those alerts depends on how well your KPI data is structured. Garbage-in, garbage-out applies to compliance reporting just as much as it does to marketing analytics.
What is the relationship between iGaming software architecture and KPI data accuracy?
KPI accuracy depends entirely on the integrity of your data pipeline from game engine to back-office to reporting layer. White-label platforms with tightly integrated stacks (single vendor for platform, games aggregation and payments) tend to have more consistent KPI data. Operators running hybrid stacks with multiple vendors face integration gaps that can corrupt GGR, RTP and player-level reporting if not managed carefully.
The cleanest KPI data comes from operators running on a single integrated platform where the game server, wallet, bonus engine and reporting module all share the same database schema. SoftSwiss's platform is a reasonable example: because the game aggregation, player wallet and back-office are built on a unified architecture, GGR calculations are consistent and real-time. When you start bolting on third-party components (a separate payment orchestration layer, an external CRM, a third-party bonus engine) you introduce reconciliation points where data can drift.
The most common data integrity problem I see in operator launches is a mismatch between the game aggregator's reported GGR and the platform's wallet-level GGR. This happens when the aggregator's feed settlement runs on a different clock cycle than the platform's wallet reconciliation. The discrepancy is usually small (fractions of a percent) but it compounds over time and creates headaches at month-end reporting and regulatory filing. The fix is to establish a daily reconciliation process between your aggregator's GGR report and your platform's wallet GGR from week one, not after you notice a discrepancy six months in.
For operators considering a custom build or a turnkey solution with significant third-party integrations, investing in a dedicated data warehouse (even a lightweight one on BigQuery or Redshift) from day one is worth the cost. Centralizing your GGR, player transaction, payment and bonus data in a single queryable layer gives you reliable KPI reporting that doesn't depend on any single vendor's dashboard. It also makes regulatory reporting substantially less painful, because you can generate audit-ready exports in whatever format a regulator requires rather than being constrained by your platform's export templates.
How do GGR and NGR benchmarks compare across different casino product verticals?
Slots typically generate the highest GGR volume but carry significant bonus cost drag. Live casino has lower theoretical hold (often 1-3% on baccarat and roulette) but attracts higher-value players with lower bonus dependency. Sports betting operates on margins of 5-8% on GGR but requires a very different software stack. Understanding per-vertical economics is essential before deciding which products to prioritize at launch.
Slots dominate GGR in most online casino operations, often accounting for 60-75% of total GGR. The theoretical hold on video slots ranges from 3-8% depending on RTP configuration and game mix, which is attractive on paper. The problem is that slots are also the product most heavily promoted through welcome bonuses and free spins offers, which means bonus cost ratios are highest in this vertical. A realistic NGR margin on slots after bonuses and payment costs might be 40-55% of GGR for a mature operation, and lower in the first year when bonus costs are elevated.
Live casino (Evolution Gaming, Pragmatic Play Live, Ezugi) operates on lower theoretical hold but attracts a different player profile. Baccarat hold is typically 1.06-1.24% on the banker bet. Roulette (European) holds about 2.7%. These are thin margins, but live casino players tend to wager larger amounts, churn more slowly and respond less to bonus incentives. The result is that live casino often generates better NGR margins as a percentage of GGR than slots, despite lower theoretical hold, because bonus costs are a smaller share of revenue. Many operators underweight live casino in their initial game portfolio and regret it.
If you are considering adding sports betting to your casino platform, the economic model is structurally different. Sports margins (the 'vig' or overround) run 5-8% on GGR for a well-managed book. But sports betting requires a trading team or a managed trading service (SBTech, Kambi, Sportradar), risk management infrastructure and a very different CRM approach. Most casino-first operators who add sports as an afterthought find the cross-sell works better in theory than in practice. The player acquisition cost for a sports bettor is also different from a casino player, and the two cohorts don't always convert to each other's products as readily as the marketing decks suggest.
| Vertical | Typical Theoretical Hold | Bonus Cost as % of GGR | Approx. NGR Margin | Notes |
|---|---|---|---|---|
| Video Slots | 3-8% | 30-50% (year 1) | 40-55% | High volume, high bonus dependency, volatile short-term hold |
| Live Casino (Baccarat/Roulette) | 1-3% | 5-15% | 55-70% | Lower hold but better NGR margins due to low bonus costs |
| Table Games (RNG) | 2-5% | 15-25% | 50-65% | Moderate bonus dependency, lower volume than slots |
| Sports Betting | 5-8% (margin) | 10-20% | 45-60% | Requires trading infrastructure; different player economics |
| Poker (cash games) | Rake-based (~5%) | Low | 60-75% | Liquidity-dependent; hard to launch standalone |
Comments
No comments yet, be the first.