Revenue Per Visitor
Revenue Per Visitor (RPV) divides total revenue by total visitors, capturing conversion rate and AOV in one decision-ready number. Here's the formula, the benchmarks, and when to trust it over CR.
Revenue Per Visitor (RPV)
Total revenue divided by total visitors — a single metric that combines conversion rate and average order value.
Revenue Per Visitor (RPV) is the average revenue a store earns from every visitor, whether they buy or not. Because it folds both conversion rate (CR) and average order value (AOV) into one number, it tells you what a session is actually worth — not just how often a session converts.
That makes RPV the more decision-useful metric when you're comparing A/B test variants, judging traffic sources, or evaluating landing pages. A variant can lift CR while dropping AOV (or vice versa) and leave revenue flat; only RPV catches that trade-off in a single read.
Most stores still default to conversion rate as their primary scorecard metric. That works when AOV is roughly constant — but the moment you test pricing, bundles, free-shipping thresholds, upsells, or product-page layouts, AOV moves and CR-only reporting starts lying to you.
RPV is also more statistically stable than CR x AOV calculated separately, because it weights each visitor equally. That matters when you're calling test results: a single €800 order in a variant can inflate AOV and make a losing test look like a winner if you're not reading revenue at the visitor level.
RPV = Total Revenue / Total Visitors
Total Revenue
Total Revenue
Gross revenue across the period, typically net of refunds and discounts depending on how you define your reporting.
Total Visitors
Total Visitors
Unique visitors or sessions in the same period — pick one and stay consistent across reports.
A Shopify apparel store reviews last month's performance: a homepage redesign test landed and they want to know if the variant is actually earning more per visitor.
Total Revenue (variant): €84,000
Total Visitors (variant): 42,000
→ RPV = €2.00
Every visitor to the variant is worth €2.00 on average. If the control sat at €1.75 RPV over the same window, the variant is a ~14% revenue lift — even if its raw CR was only 1% higher, because AOV moved with it.
RPV varies sharply by vertical and price point, so internal trend is more useful than cross-industry comparison. Still, knowing roughly where your category sits helps you sanity-check a number before you build a forecast or a test plan on top of it.
Typical RPV ranges by ecommerce vertical (paid + organic blended traffic)
| Vertical | Conversion Rate | AOV | RPV (typical range) |
|---|---|---|---|
| Beauty & cosmetics | 2.5–3.5% | €45–€70 | €1.10–€2.45 |
| Apparel & fashion | 1.5–2.5% | €60–€110 | €0.90–€2.75 |
| Home & furniture | 0.8–1.6% | €150–€350 | €1.20–€5.60 |
| Consumer electronics | 1.0–1.8% | €120–€280 | €1.20–€5.05 |
| Food & beverage (DTC) | 3.0–4.5% | €35–€60 | €1.05–€2.70 |
| Health & supplements | 2.0–3.5% | €45–€90 | €0.90–€3.15 |
Segment RPV before acting on it. Branded search traffic can run 3–5x the RPV of cold paid social on the same store, so a blended number can mask both your best and worst sources. Break RPV out by channel, device, and new-vs-returning at minimum.
Frequently asked questions about Revenue Per Visitor
Conversion rate measures how often a visitor buys; RPV measures how much revenue a visitor produces on average. RPV captures both CR and AOV, so it reflects revenue impact directly. CR alone misses cases where a variant converts more people at a lower basket value.
Use RPV as your headline metric and AOV as a diagnostic. AOV only describes the people who already bought, while RPV describes every visitor — which is the population you're actually paying to acquire. AOV is useful for understanding why RPV moved, not for judging whether it did.
Either works, but you must be consistent. Per-session RPV is more common in analytics tools because sessions are the default unit; per-visitor RPV is more accurate for measuring cohort economics. Pick one definition for the whole organisation and document it.
The two usual causes are traffic mix and price point. A store leaning heavily on cold paid social or top-of-funnel content will have a much lower blended RPV than one driven by branded search. Segment by channel before concluding you have a site problem.
Yes, and you generally should. RPV is the recommended primary metric for revenue-impacting tests because it captures both CR and AOV in one signal. Just be aware that revenue distributions are skewed by large orders, so use a test engine that supports revenue metrics with proper variance handling.
Decide upfront whether RPV uses gross or net revenue and stick with it. Gross RPV is easier to compute in real time; net RPV (after refunds) is more honest for verticals like apparel where return rates can exceed 30%. For test analysis, match your refund window to your test window.
Not directly — RPV assumes a transactional model. For lead-gen, the equivalent is value per visitor (VPV), where you assign an expected revenue value to each lead based on historical close rate and contract value. The decision logic is the same.
Multiply expected visitors by your segmented RPV. Forecasting from blended RPV is risky because traffic mix shifts (a paid push lowers blended RPV without anything being wrong). Build the forecast channel-by-channel using each channel's RPV, then sum.
No — keep CR for funnel diagnostics. CR tells you where in the journey people drop off; RPV tells you the financial outcome. You need both: CR to identify the leak, RPV (or its variant lift) to confirm a fix actually moved revenue.
€1.50–€3.00 is a reasonable blended range for most mid-market Shopify stores, but the band is wide. Stores with high AOV (furniture, electronics) can sit at €4–€6 with much lower CR, while accessory-led brands may be healthy at €1.20. Internal trend matters more than the absolute number.
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.