All terms

ARPU: What Average Revenue Per User Tells You

ARPU (Average Revenue Per User) measures how much revenue each user generates over a given period. Learn how to calculate ARPU correctly, how it relates to LTV, and what benchmarks look like by app category.

Jay Ma
3 min read
ARPU definition: average revenue per user calculation and benchmarks
On this page

ARPU (Average Revenue Per User) is total revenue divided by total users in a given time period. If your app generated $50,000 in a month from 200,000 monthly active users, your monthly ARPU is $0.25.

It sounds simple, but the denominator choice changes everything. ARPU calculated on installs tells you average revenue per download. ARPU on monthly active users tells you revenue per engaged user. ARPU on paying users (sometimes called ARPPU, Average Revenue Per Paying User) tells you revenue per customer. All three numbers are valid; they just answer different questions.

How to Calculate ARPU Correctly

The formula: ARPU = Revenue / Users in Defined Period

You need to be specific about both halves. "Revenue" should include all monetization channels: in-app purchases, subscriptions, ad revenue, and any other in-app income. Excluding ad revenue understates ARPU for ad-supported apps, sometimes substantially.

"Users" is where teams diverge. Common choices:

Total installs gives you ARPU across your entire user base, including users who installed years ago and never opened the app again. It's the most conservative number and the one most comparable across apps if you're benchmarking.

Monthly active users (MAU) gives you ARPU for users who actually engaged during the period. This is more useful for monetization optimization because it reflects what engaged users are generating.

New installs in the cohort lets you track how ARPU develops over time for users who installed in the same period. Day 7 ARPU, Day 30 ARPU, and Day 90 ARPU for the same install cohort shows you how monetization ramps, which is directly usable in LTV modeling.

ARPU vs. LTV

ARPU is a snapshot. LTV is a projection. The distinction matters when you're deciding how much to spend on acquisition.

ARPU tells you that users who installed in January generated an average of $1.20 by Day 30. LTV modeling takes that trajectory and estimates that the same cohort will generate $4.80 over their lifetime with the app. You then compare that $4.80 LTV to your CAC to determine whether acquisition is profitable.

The problem with LTV models is that they require assumptions about future retention, future monetization, and future behavior — all of which may not hold. For apps newer than 12-18 months, using observed ARPU curves with conservative extrapolation is usually more reliable than complex LTV models built on limited data.

Heroes of Mavia, a blockchain mobile game, tracks Day 7, Day 30, and Day 60 ARPU for every install cohort separately by acquisition source. This lets them see that Google UAC installs have a 30-day ARPU of $1.80 while organic installs run $3.40 — organic users monetize better, but there aren't enough of them at scale, so the team uses paid acquisition to drive volume while optimizing onboarding to close the ARPU gap.

ARPU Benchmarks by Category

These are approximate ranges based on public data:

Casual games: $0.10-$0.50 (30-day ARPU on installs) Mid-core strategy games: $1-5 Hardcore/shooter games: $5-30 Social casino: $3-15 Fitness/health subscriptions: $5-15 Productivity SaaS (consumer): $3-10 Dating apps: $2-10

These ranges are wide. The top 10% of payers in any gaming category can generate 50-80% of total revenue (the "whale" dynamic), which means average ARPU is pulled by a small group of high spenders. If you're optimizing acquisition toward users who resemble your top payers, your effective ARPU from paid acquisition can look quite different from the overall average.

Why ARPU Matters for Paid Acquisition Decisions

The relationship between ARPU and CAC determines whether your paid acquisition is sustainable.

If your 30-day ARPU is $0.60 and your CAC is $1.20, you need users to stay long enough and spend enough to generate at least $1.20 in lifetime revenue. Whether that's realistic depends on your Day 60 and Day 90 ARPU trajectory. If ARPU grows significantly beyond Day 30 (because subscriptions renew, or because late-stage purchasing behavior kicks in), you can sustain acquisition that looks unprofitable at Day 30 but becomes profitable over time.

Managed Growth tracks ARPU by acquisition source, channel, and cohort, so you can see whether the users you're buying are generating enough revenue to justify the CAC — and which channels are bringing in users who monetize at higher rates.

Frequently asked questions

  • What is ARPU in mobile apps?

    ARPU stands for Average Revenue Per User and measures how much revenue the average user generates within a defined time period, typically 7, 30, or 90 days. It's calculated by dividing total revenue by total active users (or installs) in that period.

  • What is the difference between ARPU and LTV?

    ARPU is a backward-looking snapshot: total revenue divided by users in a fixed time window. LTV (Lifetime Value) is forward-looking: the projected total revenue a user will generate over their entire relationship with the app. ARPU is easier to calculate accurately; LTV requires predictive modeling.

  • What is a good ARPU for a mobile game?

    Casual mobile games typically see 30-day ARPU of $0.20-$0.80. Mid-core games run $1-5. Hardcore or strategy games with engaged paying players can reach $10-50. These ranges vary enormously by genre, region, and monetization model.

  • How often should you calculate ARPU?

    ARPU should be tracked on a rolling basis for the key windows relevant to your monetization model: Day 7, Day 30, and Day 90 are standard for games; Day 30 and Day 365 for subscription apps. Tracking it weekly at each window lets you catch monetization drops early before they compound into LTV projection errors.

  • What is the difference between ARPU and ARPPU?

    ARPU (Average Revenue Per User) divides revenue by all users, including non-payers. ARPPU (Average Revenue Per Paying User) divides revenue only by users who made at least one purchase. ARPPU is typically 10-20x higher than ARPU in freemium apps where only 3-8% of users pay. ARPU tells you blended revenue efficiency; ARPPU tells you how valuable your paying users are individually.

  • How does ARPU relate to the LTV:CAC ratio?

    ARPU is the building block for LTV. If your 90-day ARPU is $3.20 and you estimate users generate 60% of lifetime value in the first 90 days, projected LTV is about $5.33. Against a $2.40 CAC, that is a 2.2x LTV:CAC ratio — below the typical 3x threshold. Raising ARPU through better monetization or lower churn is often more capital-efficient than cutting CAC.

Jay Ma

Co-founder

Co-founder of Hellyeah. Writes about building durable growth loops that compound over time.

Find the next growth opportunity.

Tell us what you are promoting, where you are spending and what result you need. We will review the fit and come prepared for the growth audit.