metricMarket & business

Average Revenue per User

Average revenue per user divides revenue for a defined period by the average number of users or accounts represented in that period.

Download Markdown (.md)

01What it means

Average revenue per user, or ARPU, measures revenue generated per user over a stated period. Businesses may instead use average revenue per account or customer when one account contains multiple users. The numerator may be total or recurring revenue, while the denominator may include paying users, active users, or subscribers; both must be explicit.[1][2]

Revenue normalized by an explicitly defined population ARPU is interpretable only when revenue, denominator, and period match
ARPU = included period revenue ÷ average eligible population
Revenue boundary
Total, recurring, gross, or another declared basis
Population
Users, accounts, customers, payers, or subscribers
Average base
Population averaged consistently through the period
Period
Monthly, quarterly, or annual result

State whether the unit is a user, account, customer, active user, payer, or subscriber and whether revenue is total or recurring.

02Why it matters

ARPU condenses monetization across pricing, packaging, usage, discounts, and customer mix into a trackable measure. Changes can signal successful expansion, downgrades, shifts toward larger accounts, or movement between free and paid populations. Segmenting it helps teams understand whether growth comes from more customers or more revenue per customer.

03When to use it

Use ARPU for subscription, communications, marketplace, and digital-service models where a stable user or account denominator can be defined. It supports pricing and cohort analysis, forecasting, and comparisons among segments. Use ARPA rather than ARPU when the buying and billing entity is an organization, not an individual user.

04How it works

  1. Define the revenue included, the user or account population, and the reporting period.
  2. Calculate the average eligible population during the period rather than relying on an arbitrary end count.
  3. Divide revenue by that denominator and state whether the result is monthly, quarterly, or annual.
  4. Segment by plan, cohort, geography, or customer type and reconcile changes with pricing and mix.

05A practical example

Example

A workspace product’s monthly ARPU rises after introducing a premium tier. The increase is not broad-based: large teams upgraded while small-team ARPU fell because of discounts. Reporting both account-level ARPA and seat-level ARPU shows that expansion came from customer mix and packaging, not higher monetization for every user.

06Where it breaks

ARPU is an average and can be distorted by a few large customers, currency changes, acquisitions, seasonality, or changes in who counts as active. Companies use different definitions, so external comparisons are risky. Rising ARPU can coexist with worsening retention, declining user value, or a shrinking customer base.

Common mistakes

  • Changing the denominator between active users, paying users, and accounts without disclosure.
  • Dividing period revenue by the ending population rather than an appropriate average.
  • Interpreting higher ARPU as healthier growth without checking retention and customer mix.

07Sources

  1. Average Revenue Per Account (ARPA)ChartMogul · Subscription analytics referenceAverage Revenue Per Account (ARPA)
  2. Snap Inc. Quarterly Results ExhibitU.S. Securities and Exchange Commission · Regulatory filing with company metric definitionSnap Inc. Quarterly Results Exhibit
View saved topics

Start typing to search titles, definitions, categories, and frameworks.