ARPU (Average Revenue Per User) in iGaming: Definition, Formula and Why Operators Read It Differently
Average Revenue Per User (ARPU) is the revenue an operator generates per active player over a period. It is one of the most-used and most-misread metrics in iGaming, because the definition of "user" and "revenue" both vary across teams. ARPU is most useful when defined precisely and…
TL;DR
Average Revenue Per User (ARPU) is the revenue an operator generates per active player over a period. It is one of the most-used and most-misread metrics in iGaming, because the definition of "user" and "revenue" both vary across teams. ARPU is most useful when defined precisely and tracked over time, and least useful when quoted in isolation or compared across operators with different conventions.
Formula
In its simplest form:
Both terms in the formula need explicit definitions. Revenue can be GGR or NGR. Active users can be defined by any login, any settled bet, any deposit or any combination over any window. Each combination produces a different number, and most of them are valid for some purpose.
A typical warehouse-level aggregation:
Warehouse-level aggregationWITH active AS (
SELECT COUNT(DISTINCT player_id) AS active_users
FROM bets
WHERE bet_date BETWEEN :start AND :end
),
revenue AS (
SELECT SUM(stakes - winnings) AS ggr
FROM bets
WHERE bet_date BETWEEN :start AND :end
)
SELECT revenue.ggr * 1.0
/ NULLIF(active.active_users, 0) AS arpu
FROM active, revenue;Operators commonly maintain ARPU(GGR) and ARPU(NGR) in parallel, with the activity definition documented for each.
Why it matters in iGaming
ARPU is the per-player monetisation signal. It tells you how productive your active player base is in revenue terms, independent of acquisition volume. A growing ARPU on a flat player base means your retention and engagement work is paying off. A flat ARPU on a growing player base means you are acquiring lower-value players, which can be deliberate or alarming depending on strategy.
Different teams read ARPU for different reasons:
- CRM uses ARPU per cohort to evaluate lifecycle programme effectiveness.
- Marketing tracks ARPU per acquisition channel to measure channel quality, not just volume.
- Finance forecasts revenue from ARPU times projected active users.
- Executives watch ARPU trend as a top-level engagement health signal.
ARPU is also one of the most-quoted metrics in industry conversations and the most-likely to be miscommunicated. Cross-operator ARPU comparisons usually compare apples to oranges, because activity definitions and revenue conventions differ. Within a single operator, ARPU is most powerful as a trend metric and a cohort metric, less useful as a snapshot.
Common mistakes and how teams get ARPU wrong
Mixing ARPU(GGR) and ARPU(NGR) in the same conversation. These are very different numbers. NGR-based ARPU runs structurally lower than GGR-based ARPU. Quoting one as if it were the other is a recurring source of confusion.
Inconsistent active user definition. If CRM defines active as any login and Finance defines active as any settled bet, the two teams produce different ARPU numbers and reach different conclusions about the same business. The fix is one shared activity definition or explicit naming when multiple are used.
Aggregating across very different segments. VIPs and casual players have radically different ARPU. A blended ARPU hides which segments are growing and which are deteriorating. Cohort-level and segment-level ARPU is far more diagnostic.
Treating ARPU as a cross-operator benchmark. Operator A reporting ARPU 80 EUR and operator B reporting ARPU 120 EUR tells you almost nothing without alignment on activity definitions, vertical mix and player mix. ARPU is best used internally and in cohort form.
Reading short-window ARPU as a trend. ARPU has natural variance from one or two large players' activity. Single-week swings are not always meaningful. Rolling four-week and twelve-week views give a much cleaner trend signal.
Healthy ranges and benchmarks
ARPU varies dramatically by vertical, market and player mix. Directional patterns:
- Casino-heavy operators tend to run higher ARPU than sportsbook-heavy operators because of higher monetisation per active session.
- Mature regulated markets typically deliver higher ARPU than newly entered markets, where acquisition cohorts skew towards lower-value players initially.
- VIP cohorts can run ARPU one to two orders of magnitude above the casual base.
- Bonus-driven acquisition cohorts run lower ARPU than organic cohorts in early lifecycle, with the gap narrowing as the cohort matures.
These are directional patterns based on industry observation, not strict benchmarks. The most useful comparisons are within an operator over time, by cohort and by segment.
How Gamblitude handles ARPU
In Gamblitude, ARPU is a governed Metric defined once at the semantic layer with explicit conventions for activity definition and revenue base. Teams can use multiple variants (ARPU GGR Monthly, ARPU NGR Monthly, ARPU GGR per Settled-Bet Active, VIP ARPU, Sportsbook ARPU, Casino ARPU) as separate Metrics with clear naming and ownership. The same definition flows into Reports, AI Agent answers and Insight Radar alerts, so every team works from one shared number when the variant matches their use case.
FAQ
No. ARPU averages revenue across all active users, including those who never deposited. ARPPU averages revenue across paying users only (typically defined as those who deposited in the period). ARPPU is structurally higher than ARPU and is more useful for monetisation analysis. Both have valid uses. Mixing them is a common error.
Both, with explicit naming. ARPU(GGR) is more useful for engagement analysis. ARPU(NGR) is more useful for retained-revenue analysis. Reporting only one creates blind spots. Reporting both without clear naming creates confusion. The right answer is both, named clearly.
ARPU is a per-period metric. LTV is the cumulative revenue a player generates over their entire lifecycle, projected forward from observed behaviour. ARPU is an input to LTV models. Operators sometimes confuse the two, treating monthly ARPU as if it were LTV, which leads to large forecasting errors.
Because the active player base is growing faster than revenue. This typically signals an acquisition push that is bringing in lower-value players at scale. It is not necessarily bad, but it changes the operational picture and should not be confused with engagement deterioration on the existing base.
Both, separately. Brand-level ARPU evaluates each consumer-facing brand on its own merits. Operator-level ARPU rolls them up. Some players are active across multiple brands of the same operator, which complicates the rollup. Player-level deduplication on identity is the cleaner approach for operator-level reporting.
Further reading
Found a mistake or want a term added to the iGaming Glossary? Let us know.
Browse the complete glossary or see how governed definitions work across dashboards, reports, alerts and AI answers.