Average Revenue Per Account (ARPA)
Abbreviation: ARPA
Pronunciation: AV-ur-ij REV-uh-noo pur uh-KOWNT (AR-puh)
Also known as: Average Revenue per Account, ARPA
Definition
Average Revenue Per Account (ARPA) is the revenue attributed to a defined set of customer accounts divided by the number of eligible accounts in the same period. It is useful for B2B or account-based models where one account can contain several users. The metric is meaningful only when revenue type, account definition, eligibility, period, currency conversion, refunds, and treatment of free or inactive accounts are consistent.
Overview
Meaning and scope
Average Revenue Per Account (ARPA) is the revenue attributed to a defined set of customer accounts divided by the number of eligible accounts in the same period. It is useful for B2B or account-based models where one account can contain several users. The metric is meaningful only when revenue type, account definition, eligibility, period, currency conversion, refunds, and treatment of free or inactive accounts are consistent.
Mechanism and operation
Average revenue per account divides eligible revenue for a period by the number of accounts included under an explicit counting rule. It helps businesses compare account monetization across cohorts, product tiers or periods. Account is not necessarily equivalent to an individual user: one customer organization might pay for many seats. Analysts need to choose recognized revenue versus billed amounts, monthly versus annual periods, and the definition of an active or paying account. Averages conceal distribution, so a few large enterprise accounts may raise ARPA while the typical small account remains unchanged. Discounts, refunds, multi-currency conversion and midperiod account changes can also move the result without a corresponding change in customer demand.
Practical payment example
A platform divides revenue by active customer accounts for a defined period, keeping account-level ARPA separate from user-level figures.
Operational checks
State the numerator, eligible account population, reporting cutoff and conversion method; compare ARPA alongside medians, account counts and churn rather than treating it as a complete health indicator. ARPA differs from Average Revenue Per User (ARPU), which divides by users rather than accounts. A company calculates it by dividing qualifying revenue for a period by the number of qualifying accounts under a documented rule. Reporting should define the time window, revenue source, active-account rule, free accounts, trials, credits, refunds, currencies, and late data. Analytical errors commonly come from changing definitions, inconsistent denominators, duplicate events, late data, mixed currencies, outliers, hidden exclusions, and optimizing one metric while damaging margin or customer experience.
Distinctions and limits
ARPA measures revenue per account, not per person, invoice, transaction or seat. It is also not the same as customer lifetime value.
Related reading
Related definitions: Average Revenue Per User (ARPU), Billing Account.
Example
A platform divides revenue by active customer accounts for a defined period, keeping account-level ARPA separate from user-level figures.
Comparison
The definition becomes actionable in merchant analytics and performance measurement only when the relevant merchant, customer, product or plan, transaction context, system owner, and lifecycle state are explicit. ARPA differs from Average Revenue Per User (ARPU), which divides by users rather than accounts.
Key Takeaway
ARPA measures revenue per eligible account, so the account hierarchy, revenue basis, denominator, time period, and currency rules must be explicit.
Sources
- Subscription Analytics — Stripe (2026-08-02)
- Supported Analytics Metrics — Stripe (2026-08-02)