Average Revenue Per User (ARPU)

ARPU answers a simple question: For every active user, how much revenue did we collect? It is calculated by dividing total recognized revenue by the number of users (or subscribers) in the same period.

Where it lives

• Subscription businesses (SaaS, streaming): ARPU is a core KPI alongside LTV and churn.
• Publisher ad models: ARPU is often compared to RPM, but they are not interchangeable. RPM is inventory-centric (revenue per thousand page views); ARPU is audience-centric (revenue per unique user).
• Hybrid models (freemium, ad-supported + subscription): ARPU helps track whether the blend of ad revenue and subscription revenue is improving per user.

So what: ARPU tells you if your monetization strategy is gaining or losing ground per user. A rising ARPU with flat user count means you are extracting more value. A falling ARPU may signal ad load fatigue, subscription downgrades, or user mix shift toward low-monetization segments.

ARPU = Total Revenue / Total Users (or Subscribers)

Revenue is recognized revenue for the period (subscription fees, ad revenue, in-app purchases). Users are active, paying, or subscribed — depending on the business model.

Important caveats

1. User definition varies. A streaming service counts monthly active subscribers; an ad-supported news site counts monthly unique visitors. Always check the denominator before comparing ARPU across companies.
2. Time period must match. Monthly ARPU uses monthly revenue and monthly active users. Annual ARPU uses annual figures. Mixing periods inflates or deflates the number.
3. Blended vs. segment ARPU. A single ARPU hides differences between high-value and low-value user cohorts. Segment by acquisition channel, plan tier, or geography for actionable insight.
4. Non-revenue users. If you include free-tier users in the denominator, ARPU drops — but that may be intentional for freemium analysis.

A single ARPU number is nearly useless without context. Read it as a trend (week-over-week, month-over-month) and as a comparison against segments.

What to pair it with

• User count — ARPU can rise because revenue grew, or because user count dropped (the denominator shrank). Always check both.
• Churn rate — For subscription models, rising ARPU + rising churn often means you are pushing prices too hard and losing price-sensitive users.
• RPM — For publishers, compare ARPU and RPM to see if page-level efficiency is translating into user-level value. If RPM rises but ARPU is flat, you may be serving more pages to the same users without growing the audience.

Easy mistake: A team sees ARPU jump 20% and celebrates. They forgot to check that user count dropped 15% — the revenue per remaining user went up, but total revenue barely moved. Always read ARPU with its denominator.

Revenue-side levers

• Pricing changes — Raising subscription price or ad rates directly lifts revenue per user, assuming demand holds.
• Upsells & cross-sells — Moving users from free to paid, or from basic to premium tier, increases ARPU.
• Ad load optimization — For ad-supported models, increasing ad frequency or introducing new ad formats (video, native) can lift ARPU — but watch for user fatigue.

User-mix levers

• Acquisition quality — Targeting higher-intent users (e.g., via paid search vs. display) can raise cohort ARPU.
• Reactivating lapsed users — Bringing back churned users at zero marginal acquisition cost boosts the denominator without proportional revenue gain, lowering ARPU in the short term. That is not necessarily bad.

Tradeoffs

ARPU vs. user growth. Aggressively raising prices to boost ARPU can accelerate churn and shrink the user base. Conversely, adding many low-monetization users (e.g., via a free tier) will depress blended ARPU even if total revenue grows. The right balance depends on whether your strategy prioritizes total revenue scale or per-user efficiency.

When you should NOT chase this metric: If your business is in a land-grab phase (e.g., a new market entry), optimizing for ARPU can lead you to ignore user acquisition. In that context, total revenue and user growth matter more than ARPU.

ARPU is a powerful efficiency metric, but only when read in context.

• Always pair ARPU with user count and churn to avoid misreading denominator shifts.
• Segment ARPU by cohort — blended averages hide the real dynamics.
• Distinguish ARPU from RPM: one is user-level, the other is page/session-level.