Average revenue per user divides eligible period revenue by a defined average user, customer, subscriber, or account population.
Average revenue per user (ARPU) is a company-defined operating metric that divides eligible revenue for a period by the average number of eligible users, customers, subscribers, or accounts during that same period. ARPU shows how much revenue the measured population generated on average, but the number is meaningful only when the numerator, denominator, and time period are clear.
Despite its name, ARPU does not always use individual people. A company may calculate revenue per paying subscriber, active account, household, device, or daily active user. Analysts should therefore read the company’s definition before comparing ARPU across periods or businesses.
A general formula is:
When only opening and ending user counts are available, a simplified average is:
This two-point average can be misleading when growth, churn, or an acquisition occurs unevenly during the period. Some companies instead average daily active users, month-end subscribers, or another regularly observed population.
The numerator may include all company revenue or only revenue associated with the measured user group. Questions to ask include:
Using total company revenue with only one product’s users would produce a mismatched ratio.
The denominator needs an equally precise policy. A business should explain what makes a unit active, when a new unit enters the count, and when a churned or suspended unit leaves. Trials, free users, shared accounts, wholesale relationships, bots, duplicate accounts, and multi-product customers may require separate treatment.
Assume a subscription business reports:
| Item | Amount |
|---|---|
| Opening paying users | 80,000 |
| Ending paying users | 100,000 |
| Eligible quarterly revenue | $10.8 million |
Using the simple opening-and-ending average:
If the company incorrectly divided by ending users alone, ARPU would be only $108. That denominator includes all 100,000 users as if each had been present for the entire quarter. A daily weighted average could differ from both results if most users joined near the beginning or end of the quarter.
The $120 quarterly ARPU equals a $40 monthly average only as a simple period normalization. It does not prove that each month produced $40 per user or that the next month will do so.
An aggregate ARPU can move because the mix of users changes, even when no segment changes price:
| Segment | Average users | Quarterly revenue | Segment ARPU |
|---|---|---|---|
| Basic | 60,000 | $4.5 million | $75 |
| Premium | 30,000 | $6.3 million | $210 |
| Total | 90,000 | $10.8 million | $120 |
If premium users become a larger share of the total, blended ARPU can rise without any price increase. Segment-level ARPU can therefore reveal more than the consolidated average.
| Driver | Possible effect | Interpretation question |
|---|---|---|
| Price increase | Raises ARPU if volume and discounts are stable | Did churn or contraction also increase? |
| Product upgrade | Raises ARPU through mix | Is the higher tier also more profitable? |
| Advertising demand | Changes ad-supported ARPU | Is the change seasonal or cyclical? |
| Usage growth | Raises usage-based revenue | Is usage recurring and collectible? |
| Loss of low-revenue users | Can raise ARPU while total revenue falls | Did the business become smaller? |
| Acquisition | Changes both revenue and user mix | Are acquired users included for a comparable period? |
| Foreign exchange | Changes translated revenue | Is constant-currency ARPU also disclosed? |
| Definition change | Can create an artificial step | Were prior periods recast? |
An ARPU increase is economically useful only when considered with user growth, churn, gross margin, acquisition cost, and cash collection.
| Metric | Main question | Important distinction |
|---|---|---|
| ARPU | How much period revenue did an average unit generate? | Flow metric divided by an average population |
| Revenue generating units | How many separately counted services are active? | One customer can represent several units |
| MRR | What eligible recurring value is active on a monthly basis? | Point-in-time normalized run-rate KPI |
| ARR | What eligible recurring value is active on an annualized basis? | Annualized run rate, not recognized annual revenue |
| Customer lifetime value | What contribution or value is expected over a relationship? | Model-based, multi-period estimate |
| Gross margin per user | How much gross profit remains per user? | Includes direct cost, unlike ARPU |
ARPU ordinarily starts with period revenue, but it does not establish when revenue should be recognized. Revenue recognition depends on the applicable accounting framework and the transfer of promised goods or services. Billing and cash collection can occur before or after recognition.
For example, a customer may prepay $1,200 for a one-year service. The full cash receipt can occur on day one, while revenue may be recognized over the service period. A monthly ARPU calculation should use the company’s disclosed eligible-revenue method rather than treating the payment month as $1,200 of monthly revenue per user.
ARPU is a company-defined operating metric. This article provides general financial education, not accounting, valuation, business, or investment advice.