Average revenue per paying user (ARPPU)
Average revenue per paying user (ARPPU) is total revenue divided by the number of paying users — it excludes everyone who did not spend. By isolating the paying base, ARPPU separates how much paying customers spend from how many people convert to paying. It is always at least as large as ARPU, and reading the two together reveals whether revenue is driven by spend depth or by the share who pay.
What this means
ARPPU = total revenue ÷ paying users. The denominator counts only users who made a purchase or paid for a subscription in the period, so non-paying users do not dilute it. It measures the spending depth of the people who actually pay.
ARPPU versus ARPU
ARPU divides by the whole user base; ARPPU divides by only payers, so ARPPU is always greater than or equal to ARPU. The relationship is informative: ARPU ≈ ARPPU × (paying users ÷ all users). If overall ARPU falls, comparing it to ARPPU shows whether the cause is fewer payers (paying share dropped) or lower spend per payer (ARPPU dropped). That decomposition is why product teams track both rather than a single blended figure.
- ARPPU = revenue ÷ paying users only
- Always ≥ ARPU (which includes non-payers)
- ARPU ≈ ARPPU × paying-user share
How it appears in analytics and logs
An ARPPU figure tells you what an average paying user spends. If ARPPU rises while ARPU is flat, fewer people are paying but each pays more — a mix shift the blended ARPU would hide.
Diagnostic use case
Use ARPPU alongside ARPU to separate monetization depth (spend per payer) from conversion (share who pay) when diagnosing revenue changes.
What WebmasterID can help detect
WebmasterID can record purchase events first-party, so the paying-user base and revenue behind ARPPU are grounded in your own measured conversions.
Common mistakes
- Using ARPPU and ARPU interchangeably.
- Ignoring paying-user share when comparing the two.
- Comparing ARPPU across different period lengths.
Privacy and accuracy notes
ARPPU is an aggregate revenue-to-paying-users ratio; it needs no personal identifiers. Revenue should be aggregated, not linked to identifiable people.
Related pages
- Average revenue per user (ARPU)
Average revenue per user (ARPU) is total revenue in a period divided by the number of users in that period. It is a standard unit-economics metric for subscription and consumer products, summarizing how much revenue each user generates. ARPU depends heavily on which users are in the denominator (all users vs active vs paying) and the length of the period, and it differs from ARPPU and lifetime value.
- Monthly recurring revenue (MRR)
Monthly recurring revenue (MRR) is the normalized, predictable subscription revenue a business expects each month. Annual and multi-month plans are divided down to a monthly figure so the run rate is comparable. MRR is decomposed into new, expansion, contraction, and churned components, and it deliberately excludes one-off and usage-based charges — so it is a run-rate concept, not booked or recognized revenue.
- Conversion rate: definition and denominators
Conversion rate is the share of some base that converted. The trap is the denominator: conversions per session, per user, and per unique visitor give different numbers and mean different things. Without stating the base, a conversion rate is ambiguous — and comparing rates with different bases is meaningless.
- Website observability
Track paying-user revenue from first-party events.
Sources and verification notes
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.