Average revenue per paying user (ARPPU)

ARPPU is average revenue per paying user: the revenue booked in a period, divided by the users who paid in that period. It is a monetisation read on the people who already spend, not on the registered base.

The period is part of the definition. A monthly ARPPU and a quarterly ARPPU are different measurements even if the formula looks the same.

The formula

Revenue must be defined before the first report. Most iGaming finance teams start from net gaming revenue for the period. Using gross gaming revenue, or mixing the two across months, makes the series incomparable.

Paying user is the other definition that has to be locked. A common version is a user with at least one successful deposit or in-scope purchase in the period. Including failed deposits, reversed payments or bonus-only balances inflates the denominator and understates ARPPU.

iGaming teams also have to say whether “paying” means a cash deposit, a stored-value purchase, or any movement that hits the ledger. Sportsbook and casino can share a wallet and still disagree on that line. A user who deposited for football and did not open casino is a paying user for the brand and not a paying user for the casino P&L.

📊 Worked numbers, for the arithmetic only: $100 000 of NGR in a month and 2 000 users with a qualifying payment produce an ARPPU of $50. Those figures are an illustration of the division, not a benchmark.

ARPPU, ARPU and LTV

ARPU divides the same revenue by all users in the period, including people who did not pay. ARPPU will always sit above ARPU when some of the base does not spend, because the denominator is smaller.

The gap between the two is a conversion story. ARPU can rise while ARPPU falls if more of the base starts paying at a lower average ticket. ARPPU can rise while ARPU falls if paying users spend more and the non-paying share of the base grows.

📚 Read more: Average Revenue Per User (ARPU)

Player LTV follows one acquisition cohort forward through time, usually at 30, 90 or 180 days from a qualified first-time deposit. ARPPU does not follow a cohort. It photographs whoever paid in this month, including players acquired years earlier.

A brand can therefore print a strong ARPPU on a shrinking, high-spending remnant while 90-day LTV on new qualifying depositors is falling. The two metrics are not substitutes.

💡 Key point: ARPPU photographs whoever paid this month. LTV follows one acquisition cohort. The two metrics are not substitutes.

📚 Read more: Lifetime value (LTV)

What a move in ARPPU can mean

An increase means paying users produced more revenue each, on the chosen revenue definition. The cause can be ticket size, frequency, product mix, or a change in who still counts as paying. The metric does not identify which of those moved.

A decrease can be more low-ticket payers entering the denominator, a bonus cost sitting inside NGR, or a product mix shift. It is not, by itself, evidence that “retention failed”.

Comparing ARPPU across countries without restating FX and bonus treatment is the other silent break. A euro-denominated NGR divided by paying users is not the same series as a dollar print for a brand that books both. Say the currency on the report or the comparison is theatre.

Blask does not publish operator ARPPU. Market-level demand and revenue baselines in Blask sit in other metrics — Blask Index, BAP and CEB — which describe brands and geos, not the yield of a single cashier.

📚 Read more: Blask Index

Mistakes that break the series

The metric breaks as soon as the inputs drift. A brand that books GGR in Q1 and NGR in Q2 is not tracking ARPPU through the year — it is stitching two different products into one line. The same thing happens in the denominator: unique paying users in January and average monthly payers in February look adjacent, but they are not the same count, and the ratio will move even if spend does not.

Cross-brand comparison fails for a quieter reason. If one operator nets bonus cost out of NGR and another leaves it in, the two ARPPU figures are not peers. Treating ARPPU as LTV makes the error worse. Both describe value per player, but one is a period snapshot and the other is a lifetime sum — reading them as substitutes collapses time.

FAQ