Conversion Value per Visitor

What is Conversion Value per Visitor (CVR × AOV)?

Conversion Value per Visitor (often called Revenue per Visitor – RPV) measures the average revenue generated per website visit. It is computed as Conversion Rate (CVR) multiplied by Average Order Value (AOV), showing how effectively traffic turns into money.

Formula:

CVR: Purchases ÷ Sessions (or Users)
AOV: Revenue ÷ Orders
Conversion Value per Visitor (RPV): CVR × AOV (= Revenue ÷ Sessions)

Visual Snapshot:
If CVR = 2.5% and AOV = €60 → CV/Visitor = €1.50 (0.025 × 60).

Why it matters?

Full-funnel signal: Captures both likelihood to buy (CVR) and basket value (AOV) in a single KPI.
Channel comparability: Lets you compare traffic sources on money per visit, not just clicks.
Prioritization: Shows whether to focus on conversion UX or monetization (pricing, bundles).

CV/Visitor Level*	Interpretation
< €0.50	Weak monetization or low intent traffic
€0.50–€1.50	Typical for many DTC stores; opportunities in CVR or AOV
> €1.50	Strong monetization; consider scaling traffic

*Ranges vary by industry, price band, and device mix.

KPIQ Perspective

User view: “Traffic is coming, but revenue per visit feels low. Should I fix conversion or raise basket size?”
Technical view: KPIQ benchmarks CV/Visitor by device, channel, country, and price band; decomposes it into CVR × AOV; and then:
- Identifies which driver limits revenue (e.g., mobile checkout friction → low CVR; weak attach rates → low AOV)
- Runs what-ifs (e.g., +0.5pp CVR or +€5 AOV → +€X revenue/1k sessions)
- Flags data issues (missing returns/discounts → inflated AOV, bot/paid click noise → distorted CVR, gross vs. net revenue inconsistencies)

💡 KPIQ delivers results as:
- Driver breakdowns (CVR vs AOV) by channel/device
- Guided fixes for leaks (checkout, payment, shipping thresholds, bundles, cross-sell)
- What-if simulators linking lifts to € per 1,000 sessions

Actionable Insights

✅ Optimize mobile checkout (wallets, fewer fields) to raise CVR where traffic is largest.
✅ Increase AOV with bundles, quantity breaks, free shipping thresholds near current AOV.
✅ Personalize PDP cross-sell/upsell (attach-rate targets per category).
✅ Segment CV/Visitor by channel × device to spot high-impact leaks.
✅ Clean data: exclude refunds from revenue, include discounts, de-bot sessions.

Practical Example

Scenario: 40,000 sessions/month, revenue €60,000 → current CV/Visitor = €1.50.

Step 1: Decompose

Orders	1,000
CVR	2.5% (1,000 ÷ 40,000)
AOV	€60 (€60,000 ÷ 1,000)
CV/Visitor	€1.50 (0.025 × 60)

Step 2: What-if

If CVR rises from 2.5% → 3.0% (same AOV €60), CV/Visitor = €1.80 → +€0.30/visit. At 40,000 sessions, that’s +€12,000/month without more traffic. If instead AOV rises from €60 → €66 (same CVR 2.5%), CV/Visitor = €1.65 → +€6,000/month.

Related Metrics

Conversion Rate (CVR) → Probability to purchase.
Average Order Value (AOV) → Value per order.
Return Rate → Impacts net revenue and AOV integrity.

Key takeaway: CV/Visitor unifies CVR and AOV into a single monetization KPI. Prioritize fixes where the driver-level lift yields the biggest € per visit.

📖 Click to open the in-depth analysis

Foundations

CV/Visitor (aka RPV) = Revenue ÷ Sessions. It’s sensitive to traffic quality, UX friction, and merchandising strategy.

Key Concepts

Driver separability: Treat CVR and AOV as independent levers to avoid mixed signals.
Price-band effects: Higher-priced catalogs often trade CVR for AOV; optimize per category.
Net vs. gross: Use net revenue (discounts & refunds applied) for accuracy.

Advanced Methods

What-if mapping: Convert CVR/AOV lifts into € per 1k sessions for roadmap ROI.
Cohort & device split: Compare new vs. returning, mobile vs. desktop.
Attach-rate analytics: Track bundle, cross-sell, and quantity-break performance.

Common Pitfalls

Inflated AOV by excluding discounts/returns.
Bot traffic or invalid clicks depressing CVR denominator.
Blended averages hiding channel-level issues.

Item added to your cart