AdsExam

#relationships·Jul 17, 2026·6 min read

ARPU vs Session RPM: Which Revenue Metric Tells You More About User Value?

Average Revenue Per User (ARPU) vs Session RPM (Revenue Per Mille Sessions) relationship cover

ARPU (Average Revenue Per User) and Session RPM (Revenue Per 1,000 Sessions) both measure revenue efficiency, but at different levels. ARPU looks at the full user lifecycle, while Session RPM focuses on the revenue earned per browsing session.

Core Difference: User Lifetime vs. Session Snapshot

ARPU = Total Revenue / Total Users. It averages all revenue (ads, subscriptions, in-app purchases) across every user who ever installed or registered. It’s a macro metric.

Session RPM = (Total Revenue / Total Sessions) × 1,000. It measures how much revenue you earn for every thousand sessions. It’s a micro metric tied to engagement frequency.

Key distinction

  • ARPU includes users who never return. A high ARPU can hide low engagement if a few big spenders skew the average.
  • Session RPM ignores user count entirely. A high Session RPM can hide a small user base.

Formula

  • ARPU = Revenue / Users
  • Session RPM = (Revenue / Sessions) × 1,000

What They Share

  • Both are revenue efficiency metrics.
  • Both can be used to compare performance across cohorts, channels, or time periods.
  • Both are influenced by ad fill rate, CPM, and user engagement.
  • Neither tells you about cost or profit — they are gross revenue metrics.

Which to Use When

Pick ARPU when:

  • You need to evaluate long-term user value (LTV).
  • You’re comparing acquisition channels (e.g., Facebook vs. organic).
  • Your business model relies on subscriptions or in-app purchases.

Pick Session RPM when:

  • You’re optimizing ad placements or session-level monetization.
  • You want to measure the impact of a UI change on revenue per visit.
  • You’re comparing performance across different app versions or markets.

Use both when:

  • You want to understand if revenue growth comes from more users (ARPU) or better monetization per session (Session RPM).
  • Diagnosing a flat ARPU but rising Session RPM: users are engaging less often but each session earns more.

How they diverge

Denominator

ARPU uses total users (including inactive). Session RPM uses total sessions (active events).

  • ARPU can be diluted by installs that never open the app.
  • Session RPM ignores users who never generate a session.

Time Horizon

ARPU is typically calculated over a long period (monthly, quarterly, lifetime). Session RPM is often daily or per-session.

  • ARPU smooths out short-term fluctuations.
  • Session RPM reacts quickly to changes in ad load or user behavior.

Use Case

ARPU is best for acquisition strategy and LTV modeling. Session RPM is best for monetization optimization and A/B testing.

  • Example: A high ARPU from paid users may hide poor ad revenue from free users.
  • Example: A high Session RPM may come from a small, highly engaged segment.

Where they overlap

Both Are Revenue Metrics

Both ARPU and Session RPM measure revenue generation — not profit, retention, or satisfaction. They are top-line indicators.

Both Can Be Segmented

You can calculate both for specific cohorts (country, device, acquisition source) to compare performance across segments.

Both Are Averages

Both are averages and can be skewed by outliers. Always check distribution (e.g., median ARPU, median Session RPM) for a complete picture.

Real scenarios

  1. Flat ARPU, Rising Session RPM

    Setup: A gaming app sees ARPU flat at $0.50 for three months, but Session RPM jumps from $2.00 to $3.00.

    • What happened: Users are playing fewer sessions per month (engagement dropped), but each session now earns more (better ad placement).
    • What they checked: They segmented by session frequency and found a 20% drop in sessions per user.

    Takeaway: Session RPM alone would look positive; ARPU reveals the user engagement problem.

  2. Rising ARPU, Flat Session RPM

    Setup: A news app’s ARPU grows from $0.30 to $0.45, while Session RPM stays at $1.50.

    • What happened: The app acquired more high-value subscribers (paid users) who visit often, but ad revenue per session didn’t change.
    • What they checked: They split ARPU by paid vs. free users. Paid ARPU grew; free ARPU was flat.

    Takeaway: ARPU growth came from mix shift, not better monetization. Session RPM revealed no improvement in ad performance.

How they work together

ARPU

Use ARPU when you need to evaluate user-level value over time — for example, to decide how much to spend on user acquisition (UA). It’s the standard metric for LTV calculations.

Session RPM

Use Session RPM when you’re optimizing in-session monetization — for example, testing a new ad format or changing the frequency of interstitials. It isolates revenue per engagement event.

Both

Use both when you’re diagnosing revenue changes. If ARPU drops but Session RPM holds steady, the issue is user acquisition or retention. If Session RPM drops but ARPU holds, the issue is session-level monetization.

Side-by-side snapshot

LensARPUSession RPM
DenominatorTotal UsersTotal Sessions × 1,000
Time HorizonLong-term (monthly, lifetime)Short-term (daily, per session)
Best ForUser acquisition, LTV modelingAd placement, session monetization
Sensitive ToUser churn, installsSession frequency, ad load
Skew RiskHigh spenders inflate averagePower users inflate average

Common pitfalls

  • Confusing ARPU with Session RPM

    Why the confusion is wrong: Some teams treat ARPU as a session metric, but ARPU includes users with zero sessions.

    • What to do instead: Always check the denominator. If you’re analyzing session-level changes, use Session RPM. If you’re analyzing user-level value, use ARPU.

  • Optimizing Session RPM Without Considering User Count

    Why the confusion is wrong: A high Session RPM can come from a tiny, highly engaged user base. Growing Session RPM while users decline is not sustainable.

    • What to do instead: Monitor both metrics together. If Session RPM rises but total users drop, you may be over-monetizing and churning users.

Quick check

Test whether you can tell these metrics apart.

Progress: 1/5

single

Which metric includes users who never generate a session?

Select an answer to continue

For learning only. Not advice on bids or spend.

You may also like