Average revenue per user (ARPU)
DEFINITION
Average revenue per user (ARPU) is a metric that measures the average revenue a subscription business generates per user or account over a given period, calculated by dividing total revenue by the total number of users in that period.
TABLE OF CONTENTS
RELATED TERMS
Average revenue per user, or ARPU, is a metric that measures the average amount of revenue a business generates per user or account over a defined period, typically a month or a year. It is calculated by dividing total revenue for the period by the total number of users during that same period. ARPU is one of the most widely tracked metrics in subscription and usage-based businesses because it condenses pricing, packaging, and upsell performance into a single, comparable number. A rising ARPU can signal successful upsells, price increases, or a shift toward higher-value customers, while a falling ARPU can point to discounting, downgrades, or growth concentrated in lower-tier plans. A subscription billing platform such as Recurly can surface the revenue and account data needed to calculate ARPU on a recurring basis, helping finance and growth teams track the trend without manually reconciling it each period.
Why ARPU matters for subscription businesses
ARPU gives a subscription business a quick read on how much value it extracts from its user base, and tracking it over time shows whether that value is growing or eroding. Because ARPU blends pricing and mix together, it is a useful top-line health check even before digging into more granular metrics like plan-level revenue or expansion revenue. ARPU also matters for forecasting and benchmarking. Multiplying ARPU by an expected user count gives a quick revenue projection, and comparing ARPU across customer segments, acquisition channels, or plan tiers helps a business identify where its highest-value users come from. Because ARPU is a single blended average, it works best alongside other metrics rather than as a stand-alone indicator of business health.
How to calculate ARPU
The standard formula is: ARPU = Total revenue in period / Total number of users in period For subscription businesses, this is often refined to a monthly view: Monthly ARPU = Total monthly recurring revenue (MRR) / Total active users (or accounts) in that month
Define the time period for the calculation, such as a calendar month.
Add up total revenue recognized or billed during that period, excluding one-time fees if you want a recurring-revenue-only view.
Count the total number of active users or accounts during the same period.
Divide total revenue by total users to get ARPU for the period: Imagine a subscription business with $200,000 in monthly recurring revenue and 4,000 active accounts in a given month.
<!-- end list -->
ARPU = $200,000 / 4,000 = $50 per account per month.
If the business grows to 5,000 accounts the following month but MRR only rises to $220,000, ARPU falls to $220,000 / 5,000 = $44 per account, even though total revenue increased, because growth came from lower-value accounts.
How to use ARPU
ARPU is most useful when it is tracked consistently and broken down rather than viewed as one blended number:
Track ARPU trend over time (month over month or quarter over quarter), not just a single snapshot, to catch shifts early.
Segment ARPU by plan tier, acquisition channel, or customer cohort to see where revenue per user is strongest or weakest.
Pair ARPU with active user counts so that a rising ARPU driven by churn of low-value users is not mistaken for genuine expansion.
Use ARPU alongside customer acquisition cost (CAC) to sanity-check whether the revenue per user justifies the cost of acquiring that user.
Watch for distortion from one-time charges or highly variable enterprise deals, which can skew a blended ARPU figure away from what a typical user actually pays.
ARPU vs ARPPU
ARPU divides revenue by all users, including those on free tiers or trials who are not currently paying, while ARPPU, average revenue per paying user, divides revenue only by users who are actively paying. For a business with a free tier or freemium model, ARPU will always be lower than ARPPU, since the denominator includes non-paying users. ARPU is useful for understanding overall monetization across the full user base, while ARPPU isolates how much paying customers specifically contribute, which is often the more relevant number for businesses evaluating pricing and packaging decisions for their paid tiers.
Benefits and examples
Simple, comparable benchmark. ARPU condenses pricing and mix into one number that is easy to track over time and compare across segments or against.
Early signal for pricing and packaging issues. A declining ARPU trend often surfaces before other metrics show a problem, giving teams time to investigate.
Supports revenue forecasting. Multiplying a stable ARPU by a projected user count gives a fast, directional revenue estimate for planning purposes.
Example use case. A subscription business notices ARPU declining over three consecutive months despite steady user growth. Digging into the segmented data, the team finds that new signups are concentrated in a discounted introductory plan, prompting a review of the discount's duration and eligibility rules.
Frequently asked questions
What is a good ARPU? There is no universal benchmark, since a good ARPU depends heavily on the industry, pricing model, and target customer segment.
Does ARPU include one-time charges? It can, but many businesses calculate a recurring-revenue-only version of ARPU to keep the metric focused on ongoing subscription value rather than one-time fees like setup charges.
How often should ARPU be calculated? Most subscription businesses calculate ARPU monthly, aligned with their billing cycle and MRR reporting, though some also track it quarterly or annually for longer-term trend analysis.
Why would ARPU go down even if total revenue goes up? ARPU falls when user count grows faster than revenue, which typically happens when new growth is concentrated in lower-priced plans or free tiers relative to the existing user base.
