Average revenue per paying user (ARPPU): how to optimize it

Key takeaways

• ARPPU measures average revenue from paying customers only, giving you a clearer picture of monetization effectiveness than ARPU, which includes free users.
• Paddle data shows that offering localized pricing can drive 28% higher willingness to pay in markets like the Nordics, while local currency support improved conversions by 11% for TeamGantt.
• Paddle's flexible billing models enable credit packs, bundles, and quarterly/yearly subscriptions that increase customer lifetime value by 7x compared to monthly plans.
• The calculation is simple: Total revenue from paying users ÷ Number of paying users = ARPPU.
• Paddle customers see 88-90% payment acceptance rates (93-95% in Europe) compared to typical payment processors, meaning fewer declined transactions and more revenue captured.

What is ARPPU?

Average Revenue Per Paying User (ARPPU) measures the average revenue generated from each paying customer over a specific period. Unlike ARPU (Average Revenue Per User), which averages revenue across your entire user base, including free users, ARPPU focuses solely on those who actually spend money.

This distinction matters. When 95% of your mobile app users are free, or when your SaaS product has a generous freemium tier, ARPU gets diluted by users who contribute zero revenue. ARPPU cuts through that noise and tells you how effectively you're monetizing your paying segment.

ARPPU helps validate pricing decisions, identify which features drive upgrades, and understand the impact of different billing models. For app developers, where paying users might represent just 2-5% of your total user base, ARPPU reveals which in-app purchase combinations work, how your paywall performs, and where you have room to increase average order value.

How to calculate ARPPU

The formula is pretty straightforward:

ARPPU = Total revenue from paying users ÷ number of paying users

Let's look at two examples.

Say a project management tool generates $50,000 in monthly recurring revenue from 500 paying subscribers. Your ARPPU is $50,000 ÷ 500 = $100 per paying user per month.

Take, for instance, a fitness app that earns $80,000 in a month from in-app purchases and subscriptions combined. During that month, 2,000 unique users made at least one purchase. Your ARPPU is $80,000 ÷ 2,000 = $40 per paying user per month.

Common calculation mistakes to avoid

• Including free users in the denominator: This is the most frequent mistake. If you have 10,000 total users but only 500 are paying, your denominator should be 500, not 10,000. Including free users turns your ARPPU calculation into ARPU, which answers a different question.
• Confusing transactions with users: One user can make multiple purchases in a month. If 50 users each spend $50, then 10 of those same users spend another $10, you have $2,600 in revenue from 50 paying users, not 60. Your ARPPU is $2,600 ÷ 50 = $52, not $43.
• Mixing time periods: Users on annual plans pay upfront, but for monthly ARPPU calculations, you need to normalize that revenue. A customer paying $1,200 annually contributes $100 to your monthly ARPPU, not $1,200.

ARPPU vs. ARPU vs. other revenue metrics

Each revenue metric answers a different question. Here's when to use what:

• ARPPU: How effectively are you monetizing paying customers? AARPU is best for understanding pricing, packaging, and upsell opportunities.
• ARPU: What's your overall revenue efficiency across all users? ARPU is useful when ad revenue matters or when assessing total platform economics.
• CLV (customer lifetime value): How much revenue will a customer generate before they churn? CLV is critical for setting customer acquisition budgets.
• MRR (monthly recurring revenue): What's your predictable monthly income? MRR is essential for financial forecasting and runway calculations.

ARPPU sits between snapshot metrics like MRR and predictive metrics like CLV. It tells you how much value you're extracting from paying customers right now, which directly informs how you price, what features you gate, and where you invest in product development.

Why ARPPU matters for SaaS and apps

For SaaS companies, your pricing strategy lives or dies on ARPPU. When you see ARPPU increasing, it means your pricing tiers are working, customers are upgrading, or your feature packaging is driving value. When it declines, you've got a problem—maybe you're attracting lower-value customers, or your upsell motion isn't working.

ARPPU also reveals whether your billing model matches customer behavior. Seat-based pricing should show ARPPU growth as teams expand. Usage-based pricing should increase ARPPU as customers get more value from your product. If those patterns don't appear, your model might be misaligned with how customers actually use your software.

In mobile apps, where the vast majority of users never pay, ARPPU becomes your north star monetization metric. You can't optimize what you can't measure, and ARPPU measures the only thing that matters: how much paying users actually pay.

It helps you test paywall positioning (does showing it earlier increase or decrease ARPPU?), validate IAP pricing (are your bundles working?), and understand which user segments spend the most. Gaming companies often segment ARPPU to identify "whales"—high-value users who might represent 10% of payers but 80% of revenue.

How to optimize ARPPU

Increasing ARPPU is about giving customers more ways to pay, reducing friction in your payment flow, and capturing revenue you're already leaving on the table.

Offer flexible billing models

Monthly subscriptions are easy to start, but they leave money on the table. Customers on annual plans pay upfront, reduce churn, and contribute more to lifetime value. Paddle data shows that quarterly and yearly subscriptions increase customer LTV by up to 7x compared to monthly plans.

Your billing flexibility should match how different customer segments want to pay:

• Credit packs work well for consumption-based SaaS products where usage varies month to month.
• Seat-based subscriptions with proration let teams scale up or down without friction, keeping them in your paying customer base longer.
• Family plans and bundles increase ARPPU by capturing multiple users under one payment.
• One-time purchases alongside subscriptions capture customers who want specific features without committing to recurring payments.

Paddle's billing platform handles all of these models, letting you test different approaches without rebuilding your payment infrastructure.

Build smarter cancellation flows

When a customer tries to cancel, you have one last chance to keep them as a paying user. Paddle lets you build cancellation flows that offer alternatives: downgrade to a cheaper plan, pause instead of cancel, or accept a retention discount. Each of these options keeps the customer in your paying user base, which directly protects your ARPPU.

Losing a $100/month customer hurts more than you think—it's not just $100 of MRR, it's one fewer denominator in your ARPPU calculation, which can shift your average down if that customer was above your mean.

Get localized pricing and payments right

Willingness to pay varies dramatically by geography. Nordic customers pay 28% more than US customers for the same product. Brazilian customers pay 12% less. If you're charging everyone the same price in USD, you're either overcharging growth markets, which destroys conversion, or undercharging high-value markets, which leaves revenue on the table.

Paddle's hyperlocalized pricing adjusts prices based on regional willingness to pay, capturing more revenue from customers who can pay more while improving conversion in price-sensitive markets.

Currency matters too. TeamGantt saw a 11% increase in conversion after switching from USD-only pricing to charging customers in their local currency. When customers see prices in their own currency, they convert better. 

Payment methods create similar dynamics. In Germany, 77% of customers prefer PayPal over cards. If you only accept cards, you're losing German customers at checkout. Paddle data shows that customers offering at least 25 currencies see 24.8% faster growth, and those offering at least one alternative payment method see 21% faster growth. These aren't marginal gains.

Reduce payment failures

Failed payments destroy ARPPU. A customer who wants to pay but can't because their card was declined isn't churning because they want to, but rather because of a system failure. Paddle customers see 88-90% payment acceptance rates overall (93-95% in Europe), compared to lower rates from typical payment processors. Better acceptance means more revenue captured from paying customers who already said yes.

Strategic upsells and cross-sells

The easiest revenue to capture comes from customers who already pay you. They trust you, they see value, and they're already in your payment system.

Look for natural upsells. A customer who maxed out their storage needs more. A customer hitting API rate limits needs a higher tier. A team that started with 3 seats and now has 10 members needs to upgrade. Identifying these moments and making the upgrade frictionless increases ARPPU without requiring new customer acquisition.

Bundles work similarly. Instead of selling products separately, package them together at a slight discount to the sum of parts. Customers see better value, you capture more revenue per transaction, and ARPPU increases.

When to track ARPPU

For SaaS companies, monthly tracking makes sense. Your MRR billing cycle aligns with monthly measurement, and month-over-month changes reveal whether your pricing and product changes are working.

For companies with heavy in-app purchases, weekly or even daily tracking might make sense. Mobile game developers often track ARPPU by cohort (users who installed in the same week) to understand how monetization evolves in the days after install.

Segment your ARPPU wherever it makes sense:

• By acquisition channel: Which marketing channels bring high-ARPPU customers?
• By geography: Where are your highest-value customers located?
• By product tier: Are enterprise customers increasing ARPPU faster than SMB customers?
• By cohort: Are newer customers starting at higher or lower ARPPU than historical cohorts?

These segments turn ARPPU from a single number into a diagnostic tool that tells you where to invest.

The bottom line on ARPPU

ARPPU strips away the noise of free users and tells you what matters: how effectively you're monetizing the customers who actually pay. For freemium SaaS companies and apps where paying users represent a small fraction of your total base, ARPPU becomes the clearest signal of whether your pricing, packaging, and payment infrastructure are working.

Studocu, an edtech platform with 50 million monthly users, struggled with payment failures that were killing their ability to convert paying customers. After switching to Paddle's merchant of record solution, they increased revenue per user by 15% through better payment authorization rates and reduced false declines.

Read their full story.