RPV Drivers
RPV has two arithmetic levers — conversion rate and AOV — and a short list of upstream inputs that actually move them. Here's the framework for deciding what to pull on first.
RPV Drivers
The operator-controllable inputs that move Revenue Per Visitor: conversion rate, AOV, and the upstream UX and merchandising factors behind each.
RPV drivers are the levers you can actually pull to raise Revenue Per Visitor. Arithmetically, RPV decomposes into two terms: conversion rate (CVR) and average order value (AOV). Every initiative that moves RPV does so by moving one or both.
Beneath those two arithmetic levers sits a layer of qualitative inputs — traffic quality, product-page persuasion, checkout friction, and pricing and bundling logic. Treating RPV as a single number to 'improve' is how teams chase the wrong work. Treating it as a tree of named drivers is how you pick a test that has a chance of mattering.
Revenue Per Visitor sits at the top of the tree as the outcome metric. It's useful because it captures both 'did they buy' and 'how much did they spend' in a single number, which makes it more honest than conversion rate alone for stores running bundles, upsells, or tiered pricing.
But you don't optimise an outcome — you optimise the inputs. The job of this framework is to give you a finite list of inputs you can write a hypothesis against, ranked by how much they typically move RPV on a Shopify or WooCommerce store in the €1M-€15M range.
The two arithmetic levers: CVR and AOV
RPV equals conversion rate multiplied by average order value. That identity is the entire framework's backbone. A 10% lift in conversion rate and a 10% lift in AOV both produce roughly a 10% lift in RPV — but they come from completely different teams and tests.
Conversion rate is usually the faster lever for apparel and beauty stores with sub-2% baselines: removing checkout friction or fixing a broken PDP can move CVR meaningfully in a single sprint. AOV is the slower but more durable lever — bundle architecture, free-shipping thresholds, and cross-sell logic compound over months. See RPV vs Conversion Rate and RPV vs AOV for the deeper trade-off between the two.
The four upstream input categories
Traffic quality sits upstream of both levers. A paid campaign that drives high-intent searchers from branded queries will out-convert and out-spend the same budget poured into a broad prospecting audience. Before you blame the PDP, segment RPV by channel and source — if cold paid social converts at one-third the rate of organic, your driver is acquisition, not on-site.
On-site, three input categories do the heavy lifting: product-page persuasion (imagery, social proof, size and fit, stock urgency), checkout friction (number of fields, payment methods, shipping clarity), and pricing architecture (bundles, thresholds, quantity discounts). Each maps cleanly to either CVR or AOV — sometimes both.
Diagnose before you test
Before picking a driver to work on, segment RPV three ways: by device (mobile vs desktop), by channel (paid vs organic vs email), and by new vs returning. The biggest gap is usually your highest-leverage driver. A 40% mobile RPV deficit points to checkout friction; a 60% paid-social deficit points to traffic quality.
Picking the right driver to work on
Order the drivers by expected impact, not by what's easiest to ship. For a typical apparel store at €2M revenue with 1.8% CVR and €72 AOV, checkout friction and PDP changes routinely deliver 5-15% CVR lifts, while bundle and threshold work tends to deliver 4-8% AOV lifts. Traffic-quality fixes are bigger but slower — and they live with the performance team, not CRO.
Pick one driver per sprint, write a hypothesis that names the input and the expected lever it moves, and instrument the result on RPV — not just the lever. A checkout test that lifts CVR 8% but drops AOV 9% (because you removed the upsell step) is a loss, and only an RPV view catches it.
Typical RPV lift by driver category (apparel/beauty, €1-15M revenue)
Frequently asked questions
There isn't one universal answer — it depends on where your funnel is leaking. For most stores with sub-2% conversion rate, checkout friction is the highest-impact driver because the traffic and intent are already there. For stores with healthy CVR but low AOV, bundle architecture and free-shipping thresholds usually deliver more.
Conversion rate, in most cases. CVR lifts compound across all customers immediately and the tests run faster because the baseline event (purchase) happens more often than the qualifying event for AOV tests (multi-item carts). Once CVR plateaus, shift attention to AOV. The RPV vs AOV breakdown covers the full trade-off.
Traffic quality sits upstream of both arithmetic levers. A high-intent visitor from branded search converts at 3-5x the rate of a cold paid-social click and often spends more per order. If RPV is dropping while on-site metrics are stable, the driver is almost always a shift in traffic mix.
Yes, and these are the highest-leverage tests. A clearly communicated free-shipping threshold typically lifts AOV (people add to qualify) and CVR (the offer reduces cart abandonment). Bundle pricing on the PDP often works the same way.
Conversion Rate only captures whether a visit ended in a purchase, not the size of that purchase. RPV captures both, so it's harder to game with discount-driven CVR lifts that hurt margin. For stores running upsells, bundles, or tiered pricing, RPV is the more honest top-line metric.
It varies massively by vertical. Apparel and beauty stores in the €1M-€15M band typically run €1.20-€2.50 RPV; higher-AOV categories like furniture or electronics often see €4-€10. The useful benchmark is your own RPV trend over time, segmented by device and channel.
Review the driver tree monthly and reorder priorities quarterly. The underlying inputs don't change, but their relative impact does — once you've harvested the checkout wins, PDP and pricing climb the list. A frozen roadmap means you're optimising last quarter's bottleneck.
Discounting is a CVR lever, but usually a destructive one for RPV because the AOV hit cancels the conversion gain. Targeted discounts (first-time buyer, threshold-triggered, cart-abandonment) can be net positive; site-wide discounts almost never are. Always measure the net effect on RPV, not on CVR alone.
Set up RPV as a custom metric (purchase revenue / sessions) and segment by device, channel, and landing-page template. Most useful: a weekly RPV view broken down by your top 10 landing pages — that's where driver-level diagnosis happens fastest.
A free-shipping threshold positioned ~15-20% above your current AOV is usually the highest-ROI single test. It moves both arithmetic levers, requires no dev work on Shopify or WooCommerce, and reaches significance quickly because every cart qualifies. Most stores see a 4-8% RPV lift within 3-4 weeks.
Get an AI expert review of your site
Paste your URL — Metricuno's AI runs the same heuristic checks a senior CRO consultant would, scoring your page and prioritising the fixes that'll move conversion fastest.