How I Track Average Revenue Per User in Baremetrics
A SaaS dashboard can look healthy while the engine underneath starts to cough. Baremetrics ARPU is one of the fastest signals of drift. ARPU shows whether each paying customer is worth more over time, or whether growth is getting thinner wi...
A SaaS dashboard can look healthy while the engine underneath starts to cough. Baremetrics ARPU is one of the fastest signals of drift. ARPU shows whether each paying customer is worth more over time, or whether growth is getting thinner with every new signup.
This guide explains how Baremetrics defines ARPU, how to set up tracking, how to read the number by segment and which traps distort the result. Definitions come from the Baremetrics ARPU help article and the Baremetrics ARPU academy guide.
What Baremetrics ARPU Measures
ARPU means average revenue per user. Baremetrics describes the metric as the average amount of money you make from a customer. The formula is short.
ARPU = MRR / active customers
The academy guide gives a worked example. A business with 3,459 dollars of MRR and 146 customers has an ARPU of 23.69 dollars. The guide also says to exclude free and trial users, because they generate no revenue, and to account for upgrades, downgrades and churn.
Use the metric as the average weight each customer adds to the revenue bridge. When the weight rises, pricing, packaging and expansion are likely working. When the weight falls, look closer.
| Metric | What the metric shows | Why you use the metric |
|---|---|---|
| ARPU | Average revenue per paying user | Tracks monetization quality |
| ARPA | Average revenue per account | Fits multi-seat and team billing |
| MRR | Total recurring revenue each month | Shows subscription scale |
| LTV | Revenue expected over the customer lifetime | Judges acquisition spend |
MRR shows the size of the pie. ARPU shows the average slice. LTV shows how long the meal lasts. The table gives a quick way to separate ARPU from nearby metrics.
ARPU Versus ARPA
Teams often confuse the two terms. The academy guide says ARPA measures revenue per company or billing account. The guide says ARPA suits B2B SaaS with seat-based or account-level pricing, where one account holds many seats. For consumer products, the two numbers are often the same.
Pick the metric matching your billing unit. If a customer is a company paying for ten seats, ARPA explains the sales story. If you charge per user, ARPU explains the user-level economics. Enterprise plans often justify tracking both.
How to Set Up ARPU Tracking in Baremetrics
Baremetrics calculates ARPU from live billing data, not from a stale spreadsheet. Confirm supported billing platforms and plan limits on the official Baremetrics site before you start.
- Connect the billing source. MRR and customer counts then flow in automatically.
- Check customer definitions. Count active paying customers only. Exclude free users and trials.
- Open the trend view. Compare ARPU against MRR and customer growth on the same chart.
- Create segments. Split by plan, region, acquisition source or signup date.
- Set a review rhythm. Check the numbers at the same time each month.
Segmentation depth depends on the plan. The Baremetrics pricing page lists autogenerated segments on the Launch plan and unlimited segmentation from the Growth plan. The page showed conflicting price figures when checked, so confirm costs on the official pricing page.
Pair ARPU with trend dashboards. The Baremetrics post on SaaS metrics dashboards shows why context helps. A flat ARPU line beside a rising customer count tells a different story from the same line beside falling upgrades.
What Drives ARPU Up or Down
Two forces dominate. The first is price. The academy guide says ARPU depends heavily on where you set prices. If all plans sit at low prices, ARPU stays low. The second is plan mix. A cheap entry plan can coexist with a high ARPU when most customers sit on higher tiers.
| Driver | Effect on ARPU | Example action |
|---|---|---|
| Price increase | Raises ARPU if churn stays stable | Test a new price on new signups first |
| Plan mix shift | Moves ARPU toward the dominant tier | Highlight a popular mid tier |
| Add-ons | Raises revenue per customer | Offer a la carte features |
| Heavy discounting | Lowers ARPU | Cap discount length |
| Free plan changes | Changes the paying base | Adjust limits and communicate early |
| Failed payment recovery | Protects MRR | Retry failed charges quickly |
Ways to Increase ARPU
The academy guide lists several tactics. Test one tactic at a time and watch churn.
- Tweak pricing: offer multiple plans and highlight a popular tier.
- Rethink free plans: make small feature changes and tell free users early.
- Add a la carte features: give users more ways to spend.
- Prioritize high-value accounts: provide faster, one-on-one support to your biggest accounts.
- Target higher-budget personas: aim acquisition at customers with bigger budgets.
- Recover failed payments: reduce involuntary churn, which erodes ARPU.
The guide also offers a useful scale check. An ARPU of 25 dollars needs about 3,333 customers to reach one million dollars of ARR. An ARPU of 50 dollars needs about half as many customers. Use the math to judge whether your pricing matches your growth goal.
Analyze ARPU Without Fooling Yourself
Ask two questions. Why did ARPU move, and who moved the number? Segment analysis answers both.
Beware a common trap. ARPU can rise while the business weakens. When lower-paying customers churn first, the average goes up even though total revenue health gets worse. Watch ARPU beside churn, expansion and customer count.
Read ARPU by Segment
Segments turn one blended average into a map. Build a small grid and fill the cells each month. Each cell answers one question about where revenue per customer rises or falls.
| Segment cut | Question to ask | Warning sign |
|---|---|---|
| Plan tier | Do upper tiers keep their share of customers? | Customers drift to the cheapest plan |
| Billing interval | Do annual buyers pay less per month? | Deep annual discounts lower ARPU |
| Region | Does price power differ by market? | One market sits far below the rest |
| Acquisition source | Which channel brings higher payers? | A cheap channel brings low payers |
| Signup month | Do newer cohorts pay less than older ones? | Each cohort starts lower |
Start with the cut closest to a decision you face. If you plan a price change, start with plan tier. If you plan a marketing shift, start with acquisition source. Narrow questions produce usable answers.
Sample size matters. A segment with a handful of customers swings wildly when one account joins or leaves. Wait for enough history before you act on a small group.
Link ARPU movements to events. Note every price change, plan launch, discount campaign and billing update on a simple timeline. When ARPU shifts, check the timeline first. Many sudden moves trace back to a refund wave, a failed payment spike or a plan migration.
Build a Monthly ARPU Review
Keep the review short and repeatable. Use the same questions each month.
- Which segment improved ARPU, and was the gain healthy?
- Did new customers arrive at a lower price point than current customers?
- Did any large account downgrade or cancel?
- Did a discount campaign pull in smaller buyers?
- Did a billing change or refund wave shift the average?
Answer with data. If annual prepay discounting brought in smaller customers, do not celebrate yet. If core plans expanded and churn held steady, lean in and repeat the playbook.
For a wider frame, read the Baremetrics post on important metrics for SaaS reporting. ARPU gets sharper beside the full revenue picture.
Using ARPU in Pricing Decisions
Pricing tests need a baseline. Record ARPU by plan before any change. After the change, track new signups apart from existing customers. Existing customers may keep old prices, so the blended ARPU moves slowly.
The academy FAQ gives a benchmark example. A product with an ARPU of 15 dollars compared with similar tools averaging 80 dollars signals a pricing or positioning problem. Treat the example as a prompt for research, not a rule. Compare with direct competitors on the same plan features.
The FAQ also suggests Recover for SaaS businesses at 10,000 dollars of MRR and above. The pricing page lists payment recovery as an add-on. Confirm availability and cost before you plan around the feature.
Common ARPU Mistakes
- Counting free or trial users in the customer base.
- Mixing monthly and annual revenue without normalizing.
- Reading one blended number without segments.
- Celebrating a rise caused by low-paying churn.
- Confusing ARPU with ARPA in team plans.
- Changing the customer definition mid-year.
FAQ
What is the Baremetrics ARPU formula?
Baremetrics divides MRR by active customers. Exclude free and trial users from the customer count.
What is the difference between ARPU and ARPA?
ARPU measures revenue per user. ARPA measures revenue per account. ARPA fits B2B plans with many seats per account.
Is a higher ARPU always good?
No. ARPU can rise when low-paying customers leave. Check churn, expansion and total MRR beside the average.
How often should you review ARPU?
Review monthly, and after any pricing, plan or discount change.
Can you segment ARPU in Baremetrics?
Yes. Baremetrics supports segments such as plan, region, acquisition source and signup date. Segment limits depend on the plan, so check the pricing page.
Why does ARPU fall after growth?
New customers may sign up on cheaper plans or with discounts. Review the plan mix and the acquisition source of new cohorts.
Conclusion
Baremetrics ARPU is a simple ratio with deep use. Define customers carefully, exclude free users, segment by plan and source, and read the number beside churn and expansion. Confirm plan features on the official Baremetrics pages. Pull your last 12 months, segment one customer group and read the story under the average. The money often hides there.
