What is usage revenue?
Usage revenue is the total billed for metered usage in a period. On Stripe, that is every metered line item on your invoices: the API calls, tokens, minutes or gigabytes a customer used, priced by the usage-based price on their subscription.
It leaves out everything billed up front. Platform fees, seat prices and other licensed prices belong in MRR. On a hybrid plan, the flat fee is MRR and the metered part is usage revenue.
The usage revenue formula
Worked example
A hypothetical API product charges $0.50 per 1,000 calls. Three customers, October invoices:
| Customer | Plan | Calls used | Usage revenue |
|---|---|---|---|
| A | Pay as you go | 2,400,000 | $1,200.00 |
| B | Pay as you go | 600,000 | $300.00 |
| C | $99 platform fee + usage | 150,000 | $75.00 |
| Total usage revenue | $1,575.00 | ||
Customer C’s $99 platform fee is not usage revenue. It is billed up front at a set price, so it counts in MRR.
What moves usage revenue
Usage revenue changes for three reasons, and each needs a different response:
- Customers use more or less. The most common cause. A fall here is often the first sign of churn on a usage plan.
- Customers join or leave. New metered subscriptions add usage; canceled ones stop it.
- Prices change. A new unit price or tier changes revenue with no change in usage.
Why it moves before anything else
On a usage plan, churn rarely starts with a cancel. Usage fades first, the invoice drops a period later, and the subscription often stays active the whole time. Usage revenue is where that fade first shows in money. Pair it with the idle customer rate and the churn indicators in product usage to catch it earlier.
Usage revenue vs MRR
| Usage revenue | MRR | |
|---|---|---|
| What it counts | Metered line items only | Subscription prices normalized to monthly |
| Billed | In arrears, after the period closes | Usually up front |
| Moves when | Customers use more or less | Customers join, upgrade, downgrade or cancel |
| Best for | Spotting usage growth and fading accounts | Planning and reporting predictable revenue |
Common usage revenue mistakes
- Adding platform fees. A flat fee billed up front is MRR, not usage revenue. Mixing them hides fading usage behind a fee that keeps paying.
- Reading it by usage date. Usage revenue follows the invoice. Usage from late in one period lands on that period’s invoice, not the next.
- Treating one month as a trend. Usage swings with seasons and projects. Compare each month with the customer’s own recent average.
- Watching the total only. A growing total can hide many small accounts going quiet. Check metered ARPU and the idle rate too.
Frequently asked questions
What is usage revenue?
Usage revenue is the money billed for what customers used in a period: API calls, tokens, minutes, gigabytes. It is the total of the metered line items on your invoices. Flat fees and seat prices are not part of it.
Is usage revenue part of MRR?
It depends on the tool. Stripe’s Billing overview leaves metered products out of MRR, with usage MRR offered only as a preview (Stripe docs, checked Oct 18, 2026). North Metric’s MRR counts metered usage as the average of each usage customer’s last 3 metered invoices. Usage revenue is the raw monthly total, before any averaging.
Why does usage revenue lag behind real usage?
Metered usage is billed in arrears. Usage in the first week of a monthly period reaches an invoice only when that period closes, so a drop in usage shows in usage revenue up to a full period later. Our guide to metered billing on Stripe explains the timing.
Is higher usage revenue always better?
Higher is better, but read it next to customer counts. Usage revenue can rise because a few large customers grew while many small ones faded. Check metered ARPU and the idle customer rate to see which it is.
From metric to action
North Metric flags paying customers whose usage is falling, before the drop reaches revenue. See how usage drops are caught.