Average Revenue Per User (ARPU)

Overview

Average Revenue Per User (ARPU) is qualifying revenue divided by the number of eligible users in the same period. In merchant analytics and performance measurement, the term should be tied to the merchant, customer or account, applicable commercial obligation, responsible system, and effective time.

The numerator may be recurring, billed, collected, or recognized revenue, while the denominator may count active, paying, subscribed, or all registered users. ARPU differs from Average Revenue Per Account (ARPA). The concept is closely connected to Average Revenue Per Account (ARPA), but each record should retain its own scope and status.

ARPU should state the revenue basis, eligible population, period, currency, refunds, and whether multiple accounts or identities belonging to one person are deduplicated. Operational reporting should preserve source revenue, user status, product, plan, geography, cohort, currency conversion, and period boundaries.

It is commonly used in consumer, software, media, and subscription businesses, but user definitions vary: registered, active, paying, or subscribed users produce different results. ARPU should state the revenue basis, eligible population, period, currency, refunds, and whether multiple accounts or identities belonging to one person are deduplicated.

Before using Average Revenue Per User (ARPU) for decisions, the metric owner should publish the formula and scope, reconcile source totals, segment material drivers, flag late data, compare complementary measures, and retain historical methodology versions. A dashboard value should remain traceable to the underlying orders, customers, invoices, or payments. The audit scope should also preserve its distinguishing context: is qualifying divided by the number of eligible users in.

In practice, a merchant reviewing Average Revenue Per User (ARPU) should be able to trace the displayed value or status back to the applicable customer or account, commercial terms, source events, payment or order references, responsible system, and any later correction. That evidence determines whether the next action is customer communication, fulfillment, collection, refund, configuration change, or financial adjustment. The audit scope should also preserve its distinguishing context: is qualifying divided by the number of eligible users in.