Average revenue per user or customer divides revenue in a period by the relevant user or customer count for that period. The arithmetic is simple; the definition is not. Timing, free accounts, refunds, taxes, usage, multi-seat contracts, currency, and customer mix can move the average without any individual price changing.

VISUAL LESSON

What you will learn

  1. 01Define the ARPU numerator and denominator.
  2. 02Calculate weighted portfolio ARPU.
  3. 03Explain cohort and mix effects.
Customer cohorts of different sizes and revenue blocks flow into a weighted average calculation, segment comparison, and trend panel
Portfolio ARPU is weighted by customers and revenue; a simple average of segment averages can be wrong.

ILLUSTRATIVE WORKED EXAMPLE

Work an illustrative weighted ARPU example

Starter customers$12,000 revenue
300 × $40
Growth customers$12,000 revenue
80 × $150
Enterprise customers$18,000 revenue
20 × $900
Portfolio ARPU$42,000 ÷ 400
$105
Illustrative example—not a benchmark. Replace every sample value with your own campaign, market, and measurement data.

PRACTICAL INTERFACE MAP

Move from billing ledger to an explainable ARPU trend

Contract01Define revenue and user

Record period, currency, recognized or collected revenue, discounts, refunds, taxes, free users, active rule, accounts versus seats, and exclusions.

Calculate02Build totals and cohorts

Reconcile revenue and customer counts, divide portfolio totals, then segment by plan, acquisition cohort, region, product, and customer age without averaging averages.

Explain03Decompose the change

Separate price, expansion, contraction, churn, new-customer mix, usage, currency, credits, and data corrections; pair ARPU with distribution and retention.

Conceptual walkthrough. Labels, controls, and availability can vary by account, region, plan, and interface version; verify the current screen before acting.

STEP-BY-STEP LESSON

Revenue contract → weighted portfolio → cohort mix → growth decision

DefineRevenue and active user
CalculateTotals, not averages
ExplainPrice, mix, retention

THE LEAD ATLAS METHOD

Lead Atlas Data can research business contacts matched to the growth plan's categories, locations, and target market while the company calculates ARPU from its own billing and customer evidence.See how custom list research works ↗
01

Write the metric contract

Choose calendar period, currency and exchange rule, collected versus recognized revenue, gross versus net revenue, discounts, credits, refunds, taxes, pass-through fees, free users, trials, employees, test accounts, inactive accounts, and the active-customer rule.

Decide whether user means paying customer, account, subscription, location, organization, seat, or end user. Rename the metric ARPA or average revenue per customer when that is more accurate.

02

Reconcile numerator and denominator

Tie period revenue to billing or finance and customer counts to the account or subscription source of truth. Handle mid-period starts, cancellations, pauses, multiple subscriptions, merged accounts, reactivations, annual prepayments, usage charges, and failed payments consistently.

Use average active customers during the period only when the business definition calls for it; otherwise publish the exact point-in-time or period-active denominator. Never switch silently between them.

03

Calculate the weighted portfolio

Add all eligible revenue and divide by all eligible users. For segment checks, multiply each segment's count by its average to reconcile to segment revenue, then add segment revenue and counts before dividing.

Do not take the simple average of plan-level ARPUs unless every plan has the same number of users. A small high-value segment should influence the portfolio in proportion to its customers and revenue.

04

Build cohort and distribution views

Show ARPU by acquisition cohort, customer age, plan, product, region, currency, sales motion, and channel where counts permit. Add median, percentiles, revenue concentration, and customer counts so one enterprise account does not hide the typical experience.

Mature cohorts to the same age and annotate pricing changes, migrations, credits, backfills, and acquisition shifts. A rising portfolio average can come from losing many low-priced customers rather than healthy expansion.

05

Explain the movement and decide

Bridge prior to current ARPU through new-customer mix, price, upgrades, downgrades, usage, expansion, contraction, churn, reactivation, discounts, refunds, currency, and corrections. Pair the result with gross margin, retention, concentration, and customer value.

Deliverable: metric contract, revenue reconciliation, active-user reconciliation, weighted calculation, plan and cohort tables, distribution view, movement bridge, data-quality notes, margin and retention guardrails, decision memo, and owner.

THE TAKEAWAY

Publish the revenue, denominator, period, and inclusion rules; calculate the portfolio as total revenue divided by total users; and show cohorts and distribution so mix does not masquerade as customer expansion.

OFFICIAL REFERENCES

Check the platform’s current instructions.

Platform labels, eligibility, and workflows can change. These official help pages were used to validate this lesson.