KPI Tree

Stripe Metric

Revenue

Average Revenue Per User = Total Revenue in Period / Number of Active Paying Customers in Period

Average Revenue Per User measures the mean revenue generated by each active paying customer in your Stripe account over a defined period. Using Stripe charge, invoice and subscription data, it divides total recognised revenue by the count of distinct paying customers, giving a per-customer view of monetisation. It strips out volume effects so you can see whether each account is contributing more or less over time.

Full guide: definition, formula, and benchmarks
StripeRevenue

Average Revenue Per User

Average Revenue Per User measures the mean revenue generated by each active paying customer in your Stripe account over a defined period. Using Stripe charge, invoice and subscription data, it divides total recognised revenue by the count of distinct paying customers, giving a per-customer view of monetisation. It strips out volume effects so you can see whether each account is contributing more or less over time.

How to calculate average revenue per user

Average Revenue Per User = Total Revenue in Period / Number of Active Paying Customers in Period

Why average revenue per user matters for Stripe users

Total revenue can rise simply because you are adding customers, which hides whether the accounts you already have are getting more or less valuable. Average Revenue Per User isolates account-level monetisation, so a flat or falling figure during a growth phase is an early warning that expansion, pricing or plan mix is not keeping pace.

For a team running billing through Stripe, this metric connects pricing decisions to outcomes. It shows whether upgrades, add-ons and usage-based charges are lifting per-customer value, and it gives finance and product a shared number to plan around rather than relying on top-line revenue alone.

Understand and act on average revenue per user with KPI Tree

Sync your Stripe charges, invoices and subscriptions into your warehouse and compute Average Revenue Per User in KPI Tree by dividing recognised revenue by distinct active paying customers for each period. Place it inside a metric tree alongside customer lifetime value and average revenue per transaction so you can see which inputs move per-customer value and trace changes back to pricing or plan mix.

Assign RACI ownership so a revenue or finance lead is accountable for the number, with product and growth consulted on the levers that drive it. Set a monthly review cadence in KPI Tree, with a deeper quarterly look tied to pricing and packaging changes, so shifts are caught and acted on rather than noticed after the fact.

Get started with your Stripe data

Query using MCP
MCP

Pull metrics from Stripe directly through the Model Context Protocol.

Data Warehouse
SnowflakeBigQueryDatabricksRedshift

Connect your existing warehouse where Stripe data already lands.

Professional Services
FivetranSnowflakedbt

Our professional services team can build you turn-key AI foundations in a matter of weeks. Data warehouse on Snowflake/BigQuery, ELT with Fivetran, all modelled in dbt with a semantic layer.

Empower your team to understand and act on Stripe data

Map what drives your metrics, measure progress at any grain, prove what works statistically, and deliver personalised action plans to every team member.

Experience That Matters

Built by a team that's been in your shoes

Our team brings deep experience from leading Data, Growth and People teams at some of the fastest growing scaleups in Europe through to IPO and beyond. We've faced the same challenges you're facing now.

Checkout.com
Planet
UK Government
Travelex
BT
Sainsbury's
Goldman Sachs
Dojo
Redpin
Farfetch
Just Eat for Business