RPV Calculator
An interactive RPV calculator that returns revenue per visitor, conversion rate, and AOV from three inputs — and compares two variants side by side for A/B test readouts.
RPV Calculator
A tool that computes revenue per visitor (RPV) from sessions, orders, and revenue — and derives conversion rate and AOV in the same view.
Revenue per visitor (RPV) is the single metric that ties conversion rate and average order value together: it tells you how much money each session is worth, regardless of which lever moves. This calculator takes three inputs you already have in GA4 or Shopify Analytics — visitors, orders, and revenue — and returns RPV alongside the implied conversion rate and AOV.
It's designed for two jobs. First, day-to-day reporting: replace a spreadsheet column with a faster read. Second, A/B test readouts: compare control and variant RPV directly so a CR win that quietly cannibalises AOV doesn't get shipped by accident.
Revenue per visitor calculator
Visitors (sessions)
Use sessions, not unique users, to match GA4 ecommerce reports.
Orders
Completed transactions in the same window as visitors.
Revenue
$
Gross revenue (pre-refund) over the same period.
Revenue per visitor (RPV)
$1.76
Implied conversion rate
2.20%
Implied average order value
$80.00
Use the same date window for all three inputs. If you segment by channel, run the calculator once per channel — blended RPV hides paid-vs-organic gaps that matter for budget decisions.
The calculator is intentionally minimal because RPV itself is minimal: one division. The value comes from looking at the three outputs together. A rising RPV with a flat conversion rate means AOV did the work; a rising RPV with flat AOV means more sessions are converting.
The formula behind the number
RPV = Revenue / Visitors
RPV
Revenue per visitor
Currency value of an average session.
Revenue
Gross revenue
Total transaction revenue in the period, pre-refund.
Visitors
Sessions
Sessions in the same period — not unique users.
A beauty SKU landing page receives 12,000 sessions in a week, generates 240 orders and €9,600 in revenue.
Revenue: €9,600
Visitors: 12,000
→ €0.80 RPV
Equivalent to a 2.0% conversion rate at a €40 AOV. To double RPV to €1.60 you need either CR to 4% (hard) or AOV to €80 (often easier via bundles or a tiered shipping threshold).
RPV's algebraic identity — RPV = CR × AOV — is why it's the cleanest A/B readout metric. A variant that lifts CR by 8% but drops AOV by 10% looks like a win on a conversion dashboard and a loss in the bank account. RPV catches that in one number.
Typical RPV ranges by vertical
Indicative RPV ranges for Shopify and WooCommerce stores in the €1M-€15M revenue band
| Vertical | Typical AOV | Typical CR | Typical RPV |
|---|---|---|---|
| Apparel & accessories | €60-€90 | 1.8%-2.5% | €1.20-€2.20 |
| Beauty & skincare | €35-€55 | 2.5%-3.8% | €0.90-€2.00 |
| Home & decor | €80-€140 | 1.4%-2.2% | €1.20-€3.00 |
| Consumer electronics | €120-€250 | 0.8%-1.6% | €1.00-€4.00 |
| Food & supplements (subscription) | €40-€70 | 3.0%-5.0% | €1.50-€3.50 |
| Jewellery & watches | €150-€400 | 0.6%-1.2% | €1.20-€4.50 |
Two stores in the same vertical can land on very different RPVs because traffic mix differs more than people expect. Branded organic and email traffic typically convert at 3-5× the rate of cold paid social, so a store leaning on Meta prospecting will look weak on blended RPV even when the site is fine.
Using the calculator for A/B test readouts
Run the calculator twice — once for control, once for variant — using the same time window and the same exposed-visitor count your test tool reports. The variant with the higher RPV is the commercially better experience, even if the conversion rate moved the other way.
Two practical guardrails. First, only compare RPV between variants that received roughly equal traffic; uneven splits inflate variance. Second, RPV is noisier than CR because revenue has a long tail — one €600 order in a 5,000-visitor cell shifts RPV visibly. Wait for statistical significance on RPV itself, not just on CR.
Don't ship a CR win that lost revenue
The classic trap: a sticky 'Add to cart' bar lifts conversion rate 12% but cuts AOV 15% because shoppers checkout before adding the second item. RPV drops. Always read the RPV delta before calling a winner — and if CR and AOV move in opposite directions, hold the test open longer.
Frequently asked questions
For most Shopify stores in the €1M-€15M band, blended RPV sits between €1.20 and €3.00. Below €1 usually points to a tracking gap or a heavy paid-prospecting mix; above €3 is typical of high-AOV or subscription brands.
Use sessions. GA4 ecommerce reports, Shopify Analytics, and most A/B test tools count sessions, so dividing revenue by sessions keeps RPV comparable across reports. Mixing unique users with session-level revenue will understate RPV.
AOV only looks at people who bought (revenue ÷ orders). RPV looks at everyone who landed (revenue ÷ visitors). RPV captures both who converted and how much they spent, which is why it's the better single-number readout.
Yes, and you should. Per-page RPV often reveals that a heavily-trafficked PDP is dragging blended RPV down. Use the visitors and revenue for that page specifically, pulled from GA4 landing-page reports.
Revenue has a long tail — one large order disproportionately moves daily RPV on lower-traffic days. Look at rolling 7- or 14-day RPV instead of daily. Weekly RPV is also less distorted by paid-campaign launches that briefly skew traffic mix.
Run the calculator on each variant's exposed visitors, orders, and revenue using the same window. Variant RPV is the right call metric — if it's higher than control and the test reached significance on revenue, ship it. If CR and AOV moved in opposite directions, hold longer.
By default, no — the calculator uses gross revenue, matching how Shopify and GA4 report it. If you want net RPV, subtract refunded revenue from the revenue input. For decision-making on tests, gross RPV is fine; for finance reporting, use net.
RPV is a session-level metric; LTV is a customer-level metric. RPV tells you how well the site monetises traffic right now; LTV tells you how much that customer is worth over time. Both matter, but you optimise the site against RPV.
RPV will be zero too, and the implied AOV becomes undefined (you can't divide by zero orders). Widen the window or pick a page with at least one transaction before reading the calculator output.
Yes — run the calculator once per channel using visitors, orders, and revenue filtered to that source. Paid social RPV is usually 30-60% lower than organic or email RPV; seeing that gap is what justifies budget reallocation conversations.
Test ideas before you ship them
Run unlimited A/B tests, attach hypotheses to outcomes, and build a searchable archive of what works — and what doesn't.