ARPPU is Average Revenue Per Paying User, calculated by dividing total revenue by the number of paying users in a defined period. It measures monetization strength among the payer segment only, excluding non-spending players entirely. ARPPU is the standard metric for evaluating in-app purchase health in freemium and live-service games.
How ARPPU Works
ARPPU equals total revenue divided by the number of paying users in a given period. Total players are excluded from the denominator entirely. ARPU and ARPPU share a direct algebraic relationship: ARPU equals ARPPU multiplied by payer conversion rate. A rising ARPPU alongside falling total revenue signals a shrinking payer base. The calculation period, whether daily or monthly, must stay consistent for comparisons to be valid.
ARPPU vs. ARPU: What the Difference Actually Means
ARPU divides total revenue by all players, payers and non-payers alike. In freemium games, where the vast majority of players never spend money, this blended average dilutes the monetization signal considerably. ARPPU isolates only players who spent money, giving a cleaner read on payer behavior and IAP health. ARPPU can rise while total revenue falls when the payer base is shrinking, so studios benefit from tracking both figures together. Teams that need daily granularity often add ARPDAU as a third metric alongside both.
Benefits of Tracking ARPPU
Tracking ARPPU gives analytics and LiveOps teams a payer-focused signal that blended revenue metrics obscure:
- Isolating monetization health from acquisition-volume noise, so free-player influxes do not mask payer decline.
- Detecting whale concentration risk, where high-spender cohorts inflate ARPPU and mask erosion in the mid-tier payer segment.
- Modeling player lifetime value for paying cohorts, giving growth teams more accurate revenue forecasts.
- Benchmarking IAP performance across geographies or acquisition channels to guide pricing for battle passes and consumables.
ARPPU in Live-Service Games
In freemium and live-service titles, ARPPU varies significantly across monetization models. Consumable currency and gacha mechanics drive frequent smaller purchases, while battle passes and subscriptions create predictable recurring spend with a defined ceiling. Each model produces a different ARPPU profile, and benchmarking across them without segmentation leads to misleading conclusions. Segment-level ARPPU, separated by player tier, gives LiveOps teams an early signal before high-value players churn. Studios on the Helpshift platform connect player engagement data to payer behavior, so support teams can act on ARPPU signals through proactive outreach.
Studios looking to connect monetization metrics to proactive player engagement can explore the Helpshift platform at helpshift.com/request-demo.
