Why Average Revenue Per User matters
ARPU can rise because users spend more or because the user mix shifts toward higher-value plans. It can fall during rapid low-priced growth even while total revenue increases.
- Business question
- How much revenue does each user contribute on average during this period?
- Teams that use it
- Finance, product, growth, pricing, and leadership teams.
- Decisions it supports
- Pricing changes, plan mix, packaging, monetisation experiments, and revenue forecasts.
Average Revenue Per User formula
Total Revenue ÷ Total Users
Formula components
- Total revenue
- Revenue recognised for the chosen period and product scope.
- Total users
- The agreed average or period-end count of users that generated or were eligible to generate that revenue.
- Period
- The same month, quarter, or year used for both revenue and user count.
How to calculate Average Revenue Per User
- Choose the product, geography, customer type, and reporting period.
- Calculate revenue for that exact scope.
- Count users using a documented denominator convention.
- Divide revenue by users and label the time basis, such as monthly ARPU.
Average Revenue Per User example
A software product recognises £240,000 of subscription revenue in June and uses an average active subscriber count of 3,200.
- Total June revenue = £240,000.
- Average users in June = 3,200.
- ARPU = £240,000 ÷ 3,200 = £75.
Monthly ARPU is £75 per user.
Each user contributed £75 of recognised revenue on average in June; individual users may be far above or below that average.
How to interpret the result
Break ARPU down by plan, segment, acquisition channel, and geography to separate price and mix effects. Pair it with user growth so a higher average is not mistaken for total growth.
No universal ARPU target applies across products. Currency, billing interval, free users, account structure, discounts, and revenue recognition policy all affect comparability.
Common mistakes and limitations
- Revenue and user scope mismatch
- Company-wide revenue divided by one product’s users produces a meaningless average.
- Using an unstable point-in-time count
- For a fast-growing base, an average user count may be more representative than month-end users.
- Mixing users and accounts
- A business account with many seats is not interchangeable with one end user.
- Ignoring plan mix
- ARPU can move when the mix changes even if no customer’s price changes.