Revenue per User (RPU / ARPU)

Revenue per user, often called average revenue per user or ARPU, is revenue for a defined period divided by a corresponding user count. If a service records 100,000 of monthly revenue for 5,000 users under its stated denominator, monthly ARPU is 20. The result describes revenue per unit of the chosen population; it is not profit per customer or necessarily the amount paid by a typical user.

Define the numerator and denominator together

A total-revenue ARPU can include subscriptions, purchases and advertising attributable to the users in scope. A recurring-revenue ARPU deliberately uses a narrower numerator. Distinguish recognized revenue, billings and cash receipts; they can occur in different periods. State the currency and treatment of refunds or credits, and use the same revenue definition when comparing periods.

The denominator may be distinct active users during the period, average active subscribers, paying accounts or another explicitly defined unit. These choices are not interchangeable. A SaaS account can contain many seats, and a user can have several devices. Deduplicate according to the business identity being measured. New users and users who leave partway through a period also make a period-end count different from an average subscriber count.

ARPPU means average revenue per paying user and uses payers as the denominator. For purchase revenue of 50,000, 10,000 active players and 2,000 paying players, ARPU is five and ARPPU is 25. If both use exactly the same purchase-revenue numerator and period, ARPU = payer fraction × ARPPU: 0.20 × 25 = five. Advertising revenue from nonpaying users requires care; the identity no longer applies if the two metrics use different revenue scopes.

An average is not a representative person

Suppose five users spend 0, 0, 0, 10 and 90. ARPU is 20, while the median is zero and one user supplies 90% of revenue. Both summaries are correct. The mean is useful for reconciling total revenue; the distribution explains how that total is generated. Do not turn a synthetic spending distribution into a claim that a fixed percentage of every product’s users pays below the average.

Report the payer fraction, ARPPU, relevant percentiles and revenue concentration when they affect the decision. For pricing, examine which users face the change and how their purchasing or retention might respond. A mean alone cannot show willingness to pay, identify a suitable price, or establish that a price increase caused observed revenue growth.

A rising ratio can reflect a shrinking base

Keep the 2,000 payers spending 25 each, for total revenue of 50,000. If active users fall from 10,000 to 2,500 solely because nonpaying users leave, ARPU rises from five to 20 while revenue is unchanged. ARPPU remains 25. The higher ARPU describes a changed population, not improved spending behavior. Whether losing those free users is beneficial depends on their costs, future conversion and other contributions.

A change can also come from price, usage, premium-tier adoption or customer mix. Compare like-for-like segments and cohorts, then reconcile them to the total. If high-revenue customers occupy a larger share, blended ARPU can rise with no within-segment improvement. Check user counts and retention alongside the ratio before assigning a cause.

Connect period revenue to lifetime economics

Monthly ARPU has units of currency per user-month, while CAC is an acquisition outlay per customer. Multiplying ARPU by one period’s retention rate does not produce lifetime value. A simple contribution LTV model multiplies period ARPU by a compatible margin and expected active periods, under stable assumptions.

For example, monthly ARPU of 20, a 70% contribution margin and 20 expected active months give 280 in undiscounted contribution. Against CAC of 250, the corresponding LTV:CAC ratio is 1.12. That calculation still depends on compatible customer populations, retained spending, included costs and the lifetime model. It does not establish the timing of payback or company profitability.

Annual recurring revenue is an annualized recurring run rate. An ARPU based on realized period revenue may include nonrecurring amounts and therefore cannot be multiplied into ARR without aligning scope and timing. Use ARPU to explain revenue per defined unit, then carry the denominator, time basis and revenue definition into any larger forecast.

References

• Stripe, Average revenue per user