Revenue Per Visitor (RPV) is an ecommerce metric that measures the average revenue generated by every visitor to a website, regardless of whether they made a purchase. It is calculated as: RPV = Total Revenue ÷ Total Visitors . In A/B testing, it helps ecommerce teams connect a page change to purchase behavior, revenue quality, and customer trust.
Revenue Per Visitor (RPV) is an ecommerce metric that measures the average revenue generated by every visitor to a website, regardless of whether they made a purchase. It is calculated as: RPV = Total Revenue ÷ Total Visitors . There is also an equivalent formula: RPV = Conversion Rate × Average Order Value (AOV) .
In ecommerce experimentation, Revenue per Visitor (RPV) is useful for connecting website changes to commercial outcomes. It helps teams understand whether a test is improving purchases, revenue per visitor, checkout behavior, or customer confidence.
Revenue per Visitor (RPV) matters because ecommerce experiments are usually judged by revenue, purchase conversion rate, average order value, and customer trust. Understanding the term helps teams connect test results to business outcomes instead of vanity metrics.
For example, an ecommerce team may test a product-page trust badge, shipping message, or checkout layout. Revenue per Visitor (RPV) helps connect that change to measurable outcomes such as purchases, revenue per visitor, or add-to-cart rate.
Use Revenue per Visitor (RPV) when deciding which experiment metric matters most. Tie it to the customer journey stage being tested, then compare the result with revenue, purchase rate, and any downstream behavior that could offset the initial lift.
A common mistake is judging Revenue per Visitor (RPV) with only one surface-level metric. Ecommerce tests should also consider purchase quality, revenue per visitor, average order value, and whether the lift holds across devices and traffic sources.
Revenue Per Visitor (RPV) is an ecommerce metric that measures the average revenue generated by every visitor to a website, regardless of whether they made a purchase. It is calculated as: RPV = Total Revenue ÷ Total Visitors . In A/B testing, it helps ecommerce teams connect a page change to purchase behavior, revenue quality, and customer trust.
Revenue per Visitor (RPV) matters because ecommerce experiments are usually judged by revenue, purchase conversion rate, average order value, and customer trust. Understanding the term helps teams connect test results to business outcomes instead of vanity metrics.
Use Revenue per Visitor (RPV) when deciding which experiment metric matters most. Tie it to the customer journey stage being tested, then compare the result with revenue, purchase rate, and any downstream behavior that could offset the initial lift.
Visual editor, AI-generated variants with MidaGX, redirect testing, and GA4 integration — free forever in the Mida Sandbox. No credit card required.
Mida.so is a super lightweight A/B testing tool to help you experiment, analyze and implement conversion strategies in minutes.
