Revenue Per Visitor
Revenue Per Visitor blends conversion rate and average order value into a single metric — often a better A/B test decision metric than CR alone.
Revenue Per Visitor
Revenue Per Visitor (RPV) is total revenue divided by total visitors, blending conversion rate and average order value into one number.
Revenue Per Visitor measures how much money each visit to your store generates, on average. Because it multiplies conversion rate by average order value, it captures both "did they buy?" and "how much did they spend?" in a single figure.
That makes RPV a more decision-useful primary metric than conversion rate for most A/B tests and traffic-source comparisons. A variant that lifts CR but tanks AOV (or vice versa) shows up clearly in RPV — whereas CR alone would mislead you into shipping a variant that loses money.
RPV sits inside the wider family of ecommerce metrics, alongside conversion rate, AOV, and sessions. What sets it apart is that it's a composite — you don't have to pick between volume and value when judging a change to your store.
Most analytics tools report RPV at the session level, so the denominator is sessions rather than unique users. That's the right grain for CRO work, because a test variant is shown per session, not per person.
RPV = Total Revenue / Total Visitors
Total Revenue
Total Revenue
Gross revenue in the period, typically net of refunds and discounts depending on your reporting convention.
Total Visitors
Total Visitors (or Sessions)
Number of sessions or unique visitors in the same period. Use sessions for A/B test analysis.
A Shopify apparel store runs a homepage test for two weeks. The control variant receives 40,000 sessions and generates €120,000 in revenue.
Total Revenue: €120,000
Total Sessions: 40,000
→ RPV = €3.00
Each session is worth €3 on the control. If the variant lifts RPV to €3.30, that's a 10% revenue lift per visitor — meaningful even if conversion rate barely moved, because basket size went up.
There's no universal "good" RPV — it scales with your price point. A jewellery brand with a €280 AOV and a 1.5% conversion rate posts a higher RPV than a beauty store with a €45 AOV and a 3% CR, even though both can be excellent businesses. Compare RPV against your own historical baseline and segmented benchmarks below.
Typical Revenue Per Visitor ranges by ecommerce vertical (Shopify / WooCommerce stores, €1M-€15M revenue band).
| Vertical | Median AOV | Median CR | Median RPV |
|---|---|---|---|
| Beauty & skincare | €48 | 2.8% | €1.34 |
| Apparel & accessories | €72 | 2.1% | €1.51 |
| Home & furniture | €140 | 1.4% | €1.96 |
| Jewellery | €220 | 1.1% | €2.42 |
| Food & beverage (DTC) | €38 | 3.2% | €1.22 |
| Consumer electronics | €185 | 1.3% | €2.41 |
Two caveats. First, RPV is sensitive to mix shifts — a sudden burst of paid social traffic at lower intent will drag RPV down even if your site didn't change. Always segment by channel before drawing conclusions. Second, refunds and partial returns can lag the original session by weeks, so a rolling RPV figure is more honest than a single-week snapshot.
Frequently asked questions
Conversion rate only tells you what share of visitors bought. RPV multiplies that by how much they spent, so it reflects both behaviours. Two variants with identical CR can have very different RPV if one nudges customers toward bundles or larger sizes.
Use RPV when the test can plausibly affect basket size — pricing, bundles, recommendations, free-shipping thresholds, PDP layout. Use CR when the test is purely about funnel completion (e.g. a checkout fix) and AOV can't move. When in doubt, RPV is the safer default.
No. AOV is revenue divided by orders (only buyers count). RPV is revenue divided by visitors (everyone counts, including non-buyers). RPV is always much lower than AOV because most visitors don't buy.
GA4 reports it directly as "Average purchase revenue per user" or you can build it as a calculated metric: purchase_revenue / sessions. For test analysis, prefer sessions over users so each exposure to a variant counts.
It depends entirely on price point. €1.20-€2.50 is a typical median range for stores in the €1M-€15M band, but a jewellery brand at €4 RPV is normal and a low-AOV food brand at €0.90 can still be healthy. Benchmark against your own trend first.
Convention varies. Most tools report it on gross revenue including shipping; some exclude tax. Pick one definition and stick with it across all your reports — comparing inconsistent definitions across channels is the most common reporting error.
It normalises for the volume difference between channels. Paid search might drive 50k sessions at €2.80 RPV while email drives 8k sessions at €6.10 RPV. RPV instantly tells you which channel is more efficient on a per-visit basis, independent of spend.
Top-of-funnel paid traffic is usually lower intent than organic or direct, so adding it dilutes the average. The site didn't get worse — your mix changed. Segment RPV by channel to see what actually moved.
It's possible but less common, because SaaS revenue is recurring and visit-level attribution is messy. SaaS teams usually look at MRR per visitor or lead value instead. RPV is most natural for transactional ecommerce.
RPV has higher variance than CR because of AOV outliers (one €600 order can swing the average), so you typically need 30-50% more sessions than a CR-based test to hit significance. Plan for two to four weeks of full-traffic exposure per variant for most mid-sized stores.
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.