What Is ARPPU? The Difference from ARPU and How to Use It in Paying-User Analysis


ARPPU is a metric that frequently appears when analyzing revenue for games, SaaS, and subscriptions. It is often confused with the similarly named ARPU, but "who you put in the denominator" differs, and so does what becomes visible.
This article explains the meaning and calculation of ARPPU, organizes the difference from ARPU, and then covers how to use ARPPU in paying-user analysis and how to think about improving it, in a way that even first-timers can understand.
ARPPU (Average Revenue Per Paying User) is a metric showing the average revenue generated per "paying user" over a given period.
The key point is that the denominator holds "only the users who are paying." By excluding free users and narrowing to customers who actually spend money, it looks at "how much unit revenue each person generates," making it easy to grasp the 'quality' of paying customers and the strength of monetization. It is especially valued in freemium-type services that have many free users.
ARPPU = total revenue for the period ÷ number of paying users for the period
For example, if monthly total revenue is 10 million yen and there are 1,000 paying users, ARPPU is 10,000,000 yen ÷ 1,000 = 10,000 yen. No matter how many free users there are, they are not included in this calculation.
Align the period—monthly, quarterly, annual, etc.—with the nature of your business. What matters is matching the periods of the "revenue" in the numerator and the "number of paying users" in the denominator. If they are misaligned, you will not get the correct unit value, so be careful.
The metric most often confused with ARPPU is ARPU. The difference between the two lies in the "denominator (who you divide by)" of the formula.
Let's think with a concrete example. Suppose there is a freemium service with 10,000 free users and 1,000 paying users, and monthly revenue of 10 million yen.
Even for the same revenue, ARPU and ARPPU differ greatly in order of magnitude. Because free users heavily dilute ARPU, ARPPU is more suitable when you want to see the "reality of paying customers." Neither is superior to the other; the basic approach is to use them properly: "ARPU to see the efficiency of the whole business, ARPPU to see the unit value of paying customers."
The true value of ARPPU shows when you analyze paying users in depth. Let's organize the representative perspectives for using it.
Freemium-type revenue can be captured as the multiplication "total number of users × paying rate × ARPPU." (Paying rate × ARPPU ultimately equals ARPU.) Breaking it down this way lets you consider the levers for growing revenue in three parts—"increase the number of users," "raise the paying rate from free to paid," and "raise ARPPU (the paying unit value)"—so you can see where there is room to grow.
Overall ARPPU is merely an average and does not reveal the breakdown. Decomposing it by plan, by spending tier, or by length of use shows whether a small number of high-unit-value users are pushing up ARPPU, or whether a broad layer is supporting it. Especially in games and the like, there are many cases where a tiny number of high spenders (so-called whales) raise the overall ARPPU, and looking only at the average can lead you to misread the reality.
If ARPPU is rising, it is a sign that upselling, moving to higher plans, or selling higher-priced offerings is working. However, it is important to view it together with the paying rate and churn rather than ARPPU alone. For instance, a trade-off can occur where, as a result of encouraging high-value spending, the spending hurdle rises and the paying rate falls.
Because ARPPU is "the unit value per paying customer," measures to improve it converge on the direction of "getting existing payers to spend more."
However, if you chase ARPPU too hard and skew toward high-priced plans, there are risks that the paying rate itself drops or that the hurdle for new payers rises. It is important to keep the perspective of maximizing overall revenue while watching the balance among ARPPU, paying rate, and number of users.
ARPPU is a metric showing the average revenue per paying user, calculated as "total revenue ÷ number of paying users." It differs from ARPU, which also includes free users, in "who you place in the denominator," and in freemium models, ARPPU—which sees the reality of paying customers—is especially effective.
In paying-user analysis, you can decompose revenue into "number of users × paying rate × ARPPU" to spot room for growth, or break it down by segment to grasp the existence of a high-unit-value layer. When raising ARPPU through upselling or plan design, aim to optimize overall revenue while watching the balance with the paying rate and churn.

The Pareto principle (80/20 rule) is an empirical rule that about 80% of results come from about 20% of the elements. Le...

A beginner-friendly guide to calculating NPS (Net Promoter Score). Learn the single survey question, how to sort respond...

CTR and CVR explained. CTR measures “whether it got clicked (the entrance)” and CVR measures “whether it led to a result...