The Markin ARPU report for B2C enterprisesRead now
MARKIN
Field notes
Guides8 min read

What is ARPU? Definition, formula and how to calculate it

ARPU (Average Revenue Per User) explained: definition, formula, worked example and the mistakes most operators make when reporting it.

Team Markin
  • #ARPU
  • #Glossary
  • #Guides
What is ARPU? Definition, formula and how to calculate it

ARPU stands for Average Revenue Per User. It is the revenue a business earns, on average, per active customer over a defined period. In B2C subscription and consumption businesses, it is the primary per-user unit economic, and it appears in almost every board pack from telecom to streaming to fintech.

The concept is simple enough to fit in a formula. The operational reality — what counts as revenue, who counts as a user, how to compare it across periods — is where most teams get it wrong. This guide covers all three.

The ARPU formula

Both terms must cover the same period and the same population. A quarterly revenue number divided by a monthly user count is not a real quantity. Neither is a revenue figure that includes professional services divided by a user count that only counts end consumers. This is boring to say and universally violated.

How to calculate ARPU, worked example

A streaming service reports $12,000,000 in subscription revenue in July, from 4,000,000 subscribers who were active at least one day in the month. Monthly ARPU is $12,000,000 / 4,000,000 = $3.00. Straightforward.

Two adjustments to make it defensible:

  1. 1Net revenue, not gross. Subtract refunds, chargebacks and taxes if you want ARPU to reflect what the business keeps. Different jurisdictions handle taxes differently; be explicit about which convention you use and hold it constant.
  2. 2Consistent definition of active. Pick one: paying users, logged-in users, entitled users. Most subscription businesses use the paying-users denominator (which is functionally the count of active subscriptions during the period). Any change in this definition can move ARPU by more than any product change.

ARPU vs ARPA vs ARPPU

Three acronyms show up interchangeably and mean subtly different things:

  1. 1ARPU. Average Revenue Per User. Denominator is all users, whether paying or not.
  2. 2ARPA. Average Revenue Per Account. Used in businesses where one account can have multiple users (family plans, business accounts). Denominator is accounts.
  3. 3ARPPU. Average Revenue Per Paying User. Excludes non-paying users from the denominator. Almost always higher than ARPU in freemium or ad-supported models.

None of these is more correct than the others; they are different lenses on the same base. What matters is disclosing which one you use and not switching definitions between periods without saying so.

Common ways ARPU gets misread

1. Reading it as a level, not a rate

ARPU only carries information when compared inside a category, controlling for tenure, plan mix and geography. A prepaid mobile carrier in Southeast Asia and a US streaming service can have identical growth stories with 20x different ARPU. Absolute levels across categories tell you almost nothing.

2. Confusing ARPU with LTV

ARPU is a per-period rate. LTV (Lifetime Value) is the discounted sum of future ARPU over the expected customer lifetime, net of variable cost. LTV depends on both ARPU and retention; ARPU depends on neither. A cohort with high ARPU and high churn can have lower LTV than a cohort with lower ARPU and long tenure.

3. Attributing cross-period ARPU changes to programs

ARPU moves for many reasons that have nothing to do with any program: seasonality, mix changes, tariff changes, currency movements, cohort maturation. Attributing quarter-over-quarter ARPU deltas to a specific campaign or a specific product change without a preserved holdout is almost always overclaiming.

What good looks like

A defensible ARPU report has: (1) an explicit revenue definition (net, gross, tax treatment); (2) an explicit denominator definition (paying, active, entitled); (3) a breakdown by tenure cohort and plan tier so mix effects are visible; and (4) an incremental-lift number against a preserved holdout wherever ARPU is being actively influenced by a growth program.

The last point is where most operators leave the largest ARPU gains unrealized. For a practical framework on turning ARPU into a growth rate rather than a reporting metric, see how to increase ARPU: a framework for B2C enterprises. For where the leaders sit today, see ARPU benchmarks 2026.


Markin measures ARPU as incremental lift against a preserved holdout on your own base. To see the number your growth program is actually earning, explore Revenue discovery.

Frequently asked

Questions readers ask about this.

What does ARPU stand for?
ARPU stands for Average Revenue Per User. In some categories it is reported as ARPA (Average Revenue Per Account) or ARPPU (Average Revenue Per Paying User) to disambiguate the denominator.
What is the ARPU formula?
ARPU = Total revenue in the period / Number of active users in the period. Both terms must cover the same period and use the same definition of 'active'.
How do you calculate ARPU?
Pick a period (usually a month). Sum recognized revenue attributable to end users over that period, excluding refunds and taxes. Divide by the count of unique users who were active in the same period, using a consistent definition of active (paying, logged-in, or entitled).
What is a good ARPU?
There is no absolute benchmark. ARPU only carries information when compared inside a category, controlling for tenure, plan mix and geography. A subscription streaming service in the US and a prepaid mobile carrier in India can have identical growth stories with 30x different ARPU.
Is ARPU the same as LTV?
No. ARPU is a per-period rate. LTV (Lifetime Value) is the discounted sum of future ARPU over the expected customer lifetime, net of variable cost. LTV depends on both ARPU and retention; ARPU depends on neither.

See it in the product

This runs in Markin today.

The same loops this note describes run 24/7 against your customer base. Watch the workspace decide, experiment and execute 1:1.

Explore the product