ActivationPal

ARPPU: Formula and How It Differs From ARPU

ARPPU is average revenue per paying user: the revenue in a period divided by the users who paid in it. ARPU divides the same revenue by all users, so ARPU = ARPPU × paying share. Comparing the two shows whether growth came from more payers or from bigger payments.

ARPPU formula

ARPPU = revenue in the period / paying users in the period. If an app earns $5,000 in a month from 250 payers, ARPPU is $20.

Three rules keep the number honest:

  • Count each payer once per period. A user with three renewals or two purchases is still one payer, otherwise the denominator inflates and ARPPU drops.
  • A trial start is not a payer. The user becomes one at the first charge.
  • Use revenue and payers from the same period or the same install cohort. Revenue from this month divided by payers from last month measures nothing.

Revenue can be gross or net. Net revenue removes refunds and store fees such as the Apple Small Business Program 15% commission, and gives a net ARPPU.

ActivationPal joins RevenueCat or Superwall purchases to installs, so the dashboard headline shows revenue, purchases, ARPU (revenue divided by installs) and install-to-purchase conversion for the same date range. ARPPU follows from two of those figures:

  1. Pick a date range and read ARPU and install-to-purchase conversion.
  2. Divide ARPU by the conversion rate. An ARPU of $0.10 with 0.5% of installs purchasing gives $20 per paying install.
  3. Switch the revenue view between gross and net to get both versions.

Purchases counts purchase events, so it overstates payers whenever one user buys more than once. Use the conversion rate for the payer share. Revenue from renewals of older installs also lands in the numerator, so a short range right after a release gives the cleanest read.

ARPPU vs ARPU

MetricDivides revenue byAnswersMoves when
ARPUAll users or installsWhat each user is worth on averageThe paying share or the price changes
ARPPUPaying users onlyHow much a payer spendsPlan mix or the price changes

The two are linked by one identity. Take 50,000 installs, 250 payers and $5,000 of revenue: ARPU is $0.10, ARPPU is $20 and the paying share is 0.5%. Check: $0.10 = $20 × 0.005.

That identity tells you where a change came from. If ARPU rises and ARPPU is flat, more users are paying. If ARPU is flat and ARPPU rises, payers spend more. The ARPU calculator covers the ARPU side.

When ARPPU misleads

  • A stricter paywall. If fewer people pay and the low spenders leave, ARPPU rises while total revenue falls.
  • A small payer base. With 20 payers, one large or annual purchase moves the average noticeably.
  • Uneven renewal months. A month heavy with annual renewals spikes ARPPU. Compare like periods, month against the same month a year earlier.
  • Price and country mix. A price change, or a shift toward countries with different localized pricing, moves ARPPU with no change in user behavior.

When ARPU misleads

  • A launch or channel that adds free installs. The denominator grows, ARPU falls, and payers behave exactly as before.
  • Installs versus active users. ARPU per install and ARPU per active user are different numbers. Fix one definition and keep it.
  • Old renewals in a new cohort. Revenue from customers acquired months ago added to this week's installs makes the cohort look better than it is.

Read ARPU, paying share and ARPPU together. App conversion rate covers how to measure the paying share, and subscription metrics covers the rest of the set. In ActivationPal, all three come from the same date range.

Frequently asked questions

What is a good ARPPU for an app?

There is no universal number, because ARPPU follows your price points. An app that only sells a $10 monthly plan cannot average much above $10 per payer in a month unless it sells other things. Compare against your own earlier periods, by country and by install cohort.

Should I report ARPPU or ARPU?

Report both. ARPU shows the business trend across everyone who installed. ARPPU is the better guide for pricing and plan-mix decisions, since it ignores users who never see a reason to pay.

How is ARPPU different from LTV?

ARPPU is a snapshot of revenue per payer in one period. LTV is the revenue a user brings over their whole lifetime, so it depends on retention and churn too. See app LTV for the calculation.

How do I raise ARPPU?

Change what payers buy: the plan mix, the price, localized prices by country, and add-ons or one-time purchases. Test one change at a time and watch the paying share alongside ARPPU, since a higher price can lift one and cut the other.