CRO Glossary
Revenue Per Visitor (RPV)
A metric that divides total revenue by total visitors, capturing both conversion rate and order value in one number.
Revenue per visitor (RPV) blends two things that conversion rate alone ignores: how often people buy, and how much they spend when they do. It's calculated as total revenue divided by total visitors in a given period or test variant, which makes it a useful single metric for e-commerce experiments where a change might lift conversions but shrink average order value, or vice versa.
Teams lean on RPV when optimizing for profitability rather than just click-through or sign-up counts. A pricing page test, for example, might show variant B converting fewer visitors into buyers but pushing more of them toward higher-tier plans — RPV reveals whether that trade-off is actually worth it, while conversion rate alone would flag it as a loser.
The catch is that RPV tends to have much higher variance than binary conversion metrics, since revenue is often skewed by a small number of large purchases. This means experiments measured on RPV typically need larger sample sizes or variance-reduction techniques to reach reliable conclusions, and outliers (like one whale customer) can swing results dramatically if not handled carefully.
Many CRO teams report RPV alongside conversion rate and average order value as a trio, so a lift in one can be contextualized against the others rather than read in isolation.
Related terms
Shrinkage Estimator
A statistical adjustment that pulls noisy per-variant or per-segment estimates toward an overall average to reduce overfitting to randomness.
Flicker Test
A diagnostic check to confirm whether users briefly see the original page before a variant renders in client-side experiments.
Pre-Experiment Bucketing Audit
A review process confirming users are being randomly and evenly assigned to experiment variants before launch.
Above-Fold Exclusion Rule
A test-design rule that deliberately prevents changes to above-the-fold elements so an experiment isolates below-the-fold effects.
Flicker-Free Testing
A technical setup that prevents users from briefly seeing the original page before a test variant loads.
Orthogonal Test Design
A test structure where multiple variables are changed independently so their individual effects can be measured without interference.
See this in the wild
ABWatcher watches how top teams apply revenue per visitor (rpv).
Live A/B tests at 1,000+ high-converting brands, with plain-English hypothesis and takeaway.