MetricRaven

Metrics

What is ARPU (average revenue per user)?

ARPU (average revenue per user) is the revenue you earn in a period divided by the number of users in that period. If 2,000 users bring in $10,000 in a month, ARPU is $5 per user per month.

Updated

What ARPU measures

ARPU tells you how much an average user is worth over a set period, usually a month. Telecoms, mobile apps, games and SaaS companies use it to track whether they earn more from the same audience over time, and to compare plans, countries or markets.

Who counts as a user is the part that changes between companies. A free app may count every monthly active user, paying or not. A SaaS company may count only accounts. Write the definition down next to the number, because ARPU from two companies (or two of your own reports) is only comparable when the user count means the same thing.

ARPU is an average over everyone, so it falls when you add many free or low-value users, even if paying customers are worth more than before. That is why it usually comes with two siblings: ARPPU, which counts only payers, and ARPA, which counts accounts instead of people.

ARPU formula

ARPU = revenue in the period ÷ users in the period

  • Revenue: what users paid in the period, ideally net revenue after refunds. For subscriptions you can also use MRR to get a monthly run-rate ARPU.
  • Users: the average number of users in the period, or the count at the start or end. For a month, (users at the start + users at the end) ÷ 2 is a common choice. Pick one and keep it.

Annual ARPU is the same calculation over a year, or monthly ARPU × 12 if the user base is stable.

Worked example

A note-taking app has 8,000 monthly active users in March. 400 of them pay for a subscription, and March revenue is $6,000.

ARPU = $6,000 ÷ 8,000 users = $0.75 per user per month

ARPPU = $6,000 ÷ 400 paying users = $15 per paying user per month

In April a viral post brings 4,000 extra free users, but only 20 of them pay. Revenue rises to $6,300 from 420 payers. ARPU drops to $6,300 ÷ 12,000 = $0.53, while ARPPU stays at $15. Nothing is wrong with pricing; the audience just grew faster than paying customers. Reading ARPU alone, you might have cut the price for no reason.

ARPU vs ARPPU

ARPPU (average revenue per paying user) divides revenue only by users who paid in the period. Freemium apps and games watch it because most of their users never pay.

ARPPU = revenue in the period ÷ paying users in the period

The two are linked by the share of users who pay: ARPU = ARPPU × paying share. In the example, $15 × (400 ÷ 8,000) = $0.75. So when ARPU moves, check which side moved: what payers spend, or how many users pay. The second one is a conversion rate problem, not a pricing one.

ARPA: average revenue per account

B2B SaaS usually bills accounts (companies or workspaces), not people. A team of 20 on one plan is one account. ARPA divides revenue by paying accounts, so it doesn't fall when customers add seats for free.

ARPA = MRR ÷ paying accounts

A SaaS with $48,000 MRR from 300 paying accounts has an ARPA of $160 per month. If expansion revenue from upgrades pushes MRR to $52,500 with the same 300 accounts, ARPA rises to $175. ARPA is also an input to customer lifetime value: LTV ≈ ARPA ÷ monthly churn rate.

How to measure ARPU

Take revenue from your payment provider, not from your ad platforms or analytics estimates, and the user count from your product database or analytics. Keep the period the same on both sides. Then break it down:

  • By plan or country, to see where pricing works.
  • By signup month, to see whether newer customers are worth more or less than older ones (cohort analysis).
  • By acquisition channel, to see which traffic brings valuable customers rather than many cheap ones. Two channels with the same signup count can differ several times in revenue per user, and that difference decides where your ad budget should go.

Per channel, ARPU pairs naturally with customer acquisition cost: a channel with a high CAC can still be the best one if its users are worth more. See the LTV:CAC ratio.

Common ARPU mistakes

  • Mixing user definitions. Monthly active users, registered users and paying accounts give very different ARPU. Label which one you used.
  • Comparing ARPU across free and paid products. A freemium app and a paid-only tool can't be compared on ARPU; use ARPPU.
  • Using gross revenue. Refunds and chargebacks make gross ARPU look better than it is.
  • Dividing annual payments into one month. A $1,200 yearly plan paid in March is $100 a month of ARPU, not $1,200 in March. Use MRR for subscriptions.
  • Reading the average only. A few large customers can lift ARPU while most users pay little. Check the median too.

How MetricRaven shows revenue per user

MetricRaven doesn't show a figure labeled ARPU, ARPPU or ARPA. It shows the closest building blocks from your real payments:

  • Revenue per visitor on the Traffic tab: revenue divided by visitors for the period and filters you choose. It is ARPU with visitors as the user count. See revenue per visitor.
  • Lifetime value on the Revenue tab: average, median and per-month revenue per customer, by plan. The per-month figure is close to ARPPU over each customer's lifetime.
  • MRR and Active subs on the Revenue tab. MRR ÷ active subscriptions gives an ARPA-style number for subscription businesses.

To compare channels, filter Traffic by a channel, campaign or referrer: revenue, paying customers and revenue per visitor follow the filter, with revenue credited to the visit that first brought each customer. See Filters & segments and the Revenue dashboard docs.

Questions

How do you calculate ARPU?
Divide the revenue of a period by the number of users in that period. $25,000 of monthly revenue from 5,000 users is an ARPU of $5 per user per month.
What is the difference between ARPU and ARPPU?
ARPU divides revenue by all users, paying or not. ARPPU divides it only by users who paid. ARPU equals ARPPU multiplied by the share of users who pay, so ARPU can fall while paying users spend just as much.
What is ARPA in SaaS?
ARPA is average revenue per account: MRR divided by paying accounts. B2B SaaS uses it because one account can have many users, and billing happens per account.
Is ARPU the same as customer lifetime value?
No. ARPU is revenue per user for one period, usually a month. Customer lifetime value is the total a customer pays over their whole relationship with you, which you can estimate as monthly ARPA divided by monthly churn.
Full glossary

See revenue per visitor for every channel

MetricRaven ties payments from Stripe, Paddle and other providers to the visit that brought each customer, so you can compare revenue per visitor and lifetime value by channel, campaign and plan.

14-day free trial, no card required.