Average Revenue Per User (ARPU)

Average revenue per user (ARPU) is total revenue over a period divided by the number of users or accounts active in that period. It answers a plain question: on average, how much revenue does each user bring in? If a service earns a million dollars in a month from fifty thousand users, its monthly ARPU is twenty dollars. The metric is a staple of subscription, telecom, app, and media businesses, where revenue is spread across a large base of accounts and the per-user figure says more than the gross total. ARPU can be measured monthly or annually (the annual version is sometimes called ARPA, average revenue per account, when the unit is an account rather than a person), and the exact definition of 'user' — paying only, or all active — must be fixed, because it changes the number sharply.

ARPU matters because it separates two ways a business can grow revenue: getting more users, or getting more revenue from each user. Total revenue alone hides which is happening. A company can add users while ARPU falls, masking a weakening economic per account; or hold users flat while ARPU climbs through upsells, price rises, and better mix. Watching ARPU alongside the user count tells you which lever is moving and whether growth is healthy. It is also a quick gauge of monetization quality and a useful input to other economics: paired with retention it points toward customer lifetime value, and compared against acquisition cost it shows whether each user is worth what was paid to win them. As a single, comparable number, ARPU makes monetization legible.

ARPU is easy to confuse with two neighbors. The first is total revenue. Total revenue is the whole pie; ARPU is the average slice per user. They can move in opposite directions — revenue up because users are up while ARPU slides — so reading them together is the point. Total revenue tells you the size of the business, ARPU tells you the value of an average account, and the gap between their trends reveals whether you are growing by adding users or by monetizing them better. A business that celebrates rising revenue without checking ARPU may be buying growth at the cost of per-user economics, which is exactly the thing ARPU is there to expose.

The second neighbor is customer lifetime value (LTV). ARPU is a snapshot of average revenue per user in a single period; LTV is the total profit a user is expected to generate across the whole relationship. The difference is time and depth. ARPU looks at one month or one year and at revenue, not profit; LTV looks across the entire expected lifetime and usually nets out costs and discounts future value. So ARPU is an input to LTV, not a substitute for it: combine ARPU with how long users stay (retention or its inverse, churn) and with margins, and you move from a per-period revenue figure toward a per-customer lifetime profit figure. Using ARPU as if it were LTV — treating one month's revenue per user as the whole worth of the relationship — overstates short-lived users and understates loyal ones.

Using ARPU well starts with defining it precisely and consistently: pick the period, decide whether 'user' means paying accounts or all active accounts, and never switch the definition mid-comparison, because a shift from all-users to paying-users alone can transform the number without anything real changing. Then read ARPU against the user count to see whether growth comes from more users or more revenue per user, and segment it — by plan, cohort, geography, or acquisition channel — because a single blended ARPU averages over groups that may behave very differently, hiding a cheap segment dragging down a valuable one. Track it over time as a monetization health signal, and use it as a building block toward lifetime value rather than a stand-in for it.

The failures cluster around treating the average as the whole truth. A blended ARPU can mask wide variation, so a few high-value users prop up a base of near-zero ones. Mixing free and paying users in the denominator can make the figure look healthy or weak depending on the choice, so it must be stated. Reading ARPU without the user count hides whether revenue growth is real per-account improvement or just more accounts. And mistaking ARPU for lifetime value ignores retention, cost, and time. The discipline is to define it cleanly, segment it, pair it with user count and retention, and treat it as one honest lens on monetization — quick and comparable, but an average that needs context to mean anything.

Average revenue per user (ARPU) became a standard metric in the telecom and later subscription and app industries as a simple way to read monetization — total revenue divided by the user base.

Etymology: source.

Search interest for this term over the last five years:

View interest-over-time on Google Trends →

Areas of marketing where average revenue per user (arpu) is a core concern: