Identify the numerator and denominator

The calculation needs a revenue scope, a user-eligibility rule and a reporting period. Write these beside the amount, including the currency.

Two documented report definitions

Google Analytics defines ARPU using total revenue divided by active users, including users who did not purchase. Its ARPPU metric instead uses purchase revenue per active user who made a purchase.

Those two reported metrics can differ in their revenue scope as well as their user population.

ChartMogul's ARPA report, also described by that provider as ARPU or ARPC, divides MRR by paying subscribers. Free subscriptions are excluded, and one customer with multiple subscriptions counts once.

These are provider-specific methods; an account count is not automatically a count of individual people.

A denominator check with hypothetical users

Assume USD 600 of revenue in one month comes entirely from 80 paying users, alongside 40 nonpaying users. All 120 meet the eligibility rule for this illustrative user population.

Hypothetical averages using the same monthly revenue
PopulationCalculationAverage for this month
All 120 defined usersUSD 600 ÷ 120 usersUSD 5 per user
80 paying users onlyUSD 600 ÷ 80 paying usersUSD 7.50 per paying user

The all-user average is USD 5; the paying-user average is USD 7.50. Changing only the denominator changes the average without adding revenue.

Combine segments with their counts

In the same hypothetical example, paying users average USD 7.50 and nonpaying users average USD 0. Weighting each subgroup by its user count gives (USD 7.50 × 80 + USD 0 × 40) ÷ 120 = USD 5 per user for the month.

To combine disjoint segments, sum their revenue and their eligible user counts before dividing. Do not take an unweighted average of subgroup averages when the groups have different sizes.

When an average changes, compare revenue totals, eligible user counts and segment membership before attributing the change to pricing.

Annual revenue divided by the eligible annual user count is not automatically the monthly average multiplied by 12: the population and revenue base may change between periods. Customer accounts, contract values and user counts also need separate labels; an annual per-user average is not automatically annual contract value.

Questions about ARPU

What happens if the eligible user count is zero?

The average is undefined because it requires division by the eligible user count. Do not present it as zero revenue per user; retain the revenue amount and explain the missing denominator.

Does a higher ARPU establish that a pricing change worked?

No. Check the same revenue scope, period and population, then inspect the underlying changes. A different user mix or eligibility rule can change the average without demonstrating a pricing effect.

Monthly Recurring Revenue · Customer Lifetime Value · Customer Acquisition Cost

Metric methods