Short answer
To calculate revenue per visitor (RPV), divide total revenue by the number of visitors in the same period: RPV = revenue ÷ visitors. It is the same as conversion rate × average order value. If a store makes $50,000 from 25,000 visitors, RPV is $2.00. For lead generation, use the average value of a lead instead of order value.
Key takeaways
- RPV = total revenue ÷ visitors, which equals conversion rate × average order value.
- For lead gen, RPV = lead conversion rate × value per lead, where value per lead comes from close rate and deal value.
- RPV is a better primary A/B test metric than conversion rate because it catches changes in order value and lead quality.
- Decide up front how you handle refunds, very large orders, subscriptions and sessions versus users, and use the same rules for both versions.
- Take revenue and visitors from the same tool with the same definitions, or the number will be off.
What is the formula for revenue per visitor?
Revenue per visitor = total revenue ÷ total visitors, for the same pages and the same dates. It tells you how much money, on average, each visit or visitor brings in, whether they bought or not.
RPV = revenue ÷ visitors
RPV = conversion rate × average order value
The two formulas give the same answer. Conversion rate is orders ÷ visitors, and average order value (AOV) is revenue ÷ orders. Multiply them and the orders cancel out, leaving revenue ÷ visitors. The second version is useful because it shows why RPV moved: more people bought, people spent more, or both.
In lead generation and call funnels the same number is often called value per session or value per visitor. The idea is identical, only the value of a conversion comes from leads or calls instead of orders.
How do you calculate RPV for an ecommerce store?
Take revenue for a period, divide it by visitors for the same period, then check it against conversion rate × AOV.
Example
Say a store had 40,000 visitors last month, 1,000 orders and $80,000 in revenue. These are round, made-up numbers to show the math.
- Conversion rate = 1,000 ÷ 40,000 = 2.5%
- AOV = $80,000 ÷ 1,000 = $80
- RPV = $80,000 ÷ 40,000 = $2.00, and 2.5% × $80 = $2.00 as well
Every visitor to the store is worth about $2.00 on average, including the 97.5% who didn’t buy.
How do you calculate RPV for lead generation?
Replace order value with the value of a lead: RPV = lead conversion rate × value per lead. Value per lead is usually the share of leads that become customers multiplied by what a customer is worth to you. If you get paid per lead or per qualified call, use that payout instead.
Example
Say a landing page gets 10,000 visitors a month and 400 of them submit the form, a 4% lead rate. Sales closes 10% of leads, and a new customer is worth $500 in revenue.
- Value per lead = 10% × $500 = $50
- RPV = 4% × $50 = $2.00 per visitor
- Check: 400 leads × 10% = 40 customers × $500 = $20,000, and $20,000 ÷ 10,000 visitors = $2.00
The catch is that close rate takes time to measure. During a test, you often use a proxy that you can see sooner, such as qualified leads or booked calls, and confirm with closed revenue later.
How does RPV compare with the other metrics?
Each common metric answers one question and misses something. RPV is the one that combines how many people convert with how much each conversion is worth.
| Metric | Formula | What it tells you | What it misses |
|---|---|---|---|
| Conversion rate | Orders or leads ÷ visitors | How many visitors take the action | How much each order or lead is worth |
| Average order value | Revenue ÷ orders | How much buyers spend per order | How many visitors buy at all |
| Value per lead | Close rate × customer value | What a typical lead is worth | How many visitors become leads |
| Revenue per visitor | Revenue ÷ visitors, or conversion rate × AOV | How much each visitor is worth on average | Profit margin and long-term value, unless you add them |
Why is RPV a better primary A/B test metric than conversion rate?
Because a variant can raise conversion rate and still lose money. A bigger discount, a cheaper default option or a looser form can bring in more orders or leads that are each worth less. Conversion rate calls that a win. RPV doesn’t, because the value of each conversion is already inside it.
Example
Say the control converts at 2.5% with an AOV of $80, so RPV is $2.00. The variant pushes a cheaper bundle and converts at 2.8%, but AOV drops to $68. Variant RPV is 2.8% × $68 = $1.90. Conversion rate is up 12%, revenue per visitor is down 5%.
There is a trade-off. Revenue varies much more from visitor to visitor than a yes or no conversion does, so RPV is a noisier metric and usually needs more traffic to reach a clear result. I still use it as the primary metric for tests that can change what people spend, and I keep conversion rate and AOV as secondary metrics so I can explain the result. See A/B test sample size for how traffic affects that.
Once you have the RPV difference between two versions, turning it into yearly money is a separate step, covered in how to calculate the revenue impact of an A/B test.
What are the common mistakes when calculating RPV?
Most RPV mistakes come from deciding the rules after you see the data. Settle these before the test starts and apply them to both versions.
- Refunds and cancellations. Gross revenue on the day of purchase can flatter a variant that attracts buyers who later return the product. Use net revenue where you can, and if returns take weeks, read the result again after the return window closes.
- Outliers and whales. One very large order can decide a test on its own. Pick a rule in advance, for example capping each visitor’s revenue at a high percentile or excluding wholesale orders, and report the result with and without it.
- Subscriptions and lifetime value. If people subscribe, first-order revenue understates what a customer is worth, and a change that brings in more trials of lower quality can look good for a month. Use first-payment RPV as the test metric, add guardrails such as trial-to-paid or early cancellation, and check longer-term value when the data exists.
- Sessions versus users. RPV per session and RPV per user are different numbers, because one person can visit several times. Most A/B testing tools split traffic by visitor, so per-visitor RPV matches how the test was split. Whatever you choose, never compare a per-session number with a per-user one.
- Mixing tools. Revenue from your store backend divided by sessions from your analytics tool mixes two different definitions. Take both from the same source.
- Taxes, shipping and discounts. Decide whether revenue includes them and keep it the same everywhere. A free shipping test changes shipping revenue, so the definition matters.
How do you get revenue per visitor from GA4?
GA4 gives you the two parts: a revenue metric and a visitor metric. You divide them yourself, unless the per-user metric it already offers fits your definition. According to Google’s GA4 metrics reference:
- Purchase revenue is revenue from purchases, in-app purchases and subscriptions, minus refunds.
- Total revenue adds ad revenue on top of that, also minus refunds.
- Sessions counts sessions that began on the site. By default a session times out after 30 minutes of inactivity.
- Average revenue per active user (ARPU) is total revenue divided by active users, counting users whether they bought or not.
So for revenue per session, build a report or exploration with Purchase revenue and Sessions for the same pages and dates, and divide. For revenue per user, ARPU is close, but it is per active user and includes ad revenue, so check that it matches what you want before you use it. Refunds only come off if your setup actually sends refund events to GA4.
How do you get revenue per visitor from Shopify?
Multiply Shopify’s conversion rate by its average order value, or divide sales by sessions, and know what each number includes. Shopify’s analytics reference defines:
- Conversion rate as sessions that completed checkout ÷ sessions.
- Average order value as (gross sales minus discounts) ÷ orders, excluding post-order adjustments such as returns.
- Sessions as online store visits, counted only when visitors consent to cookies through the cookie banner.
Conversion rate × AOV gives revenue per session before returns, taxes and shipping. Two things to watch. First, AOV ignores returns, so it is a gross figure, and you need net sales for a refund-adjusted number. Second, if sessions are only counted with cookie consent, but orders are counted either way, dividing total sales by sessions can overstate RPV. Use the same report for both parts, and compare periods with the same setup.
How should you use RPV day to day?
Track it by page, device and traffic source, and use it as the primary metric for tests that can change what people spend. A blended RPV for the whole site hides most of what matters. Paid social traffic on mobile and returning visitors on desktop can be worth very different amounts, and a test usually only touches one of them. I write the RPV definition into every test plan: which revenue, which visitors, which refund rule, which outlier rule. Then nobody argues about the number when the test ends.
If you want tests planned and read on revenue per visitor, see A/B testing or book a call.
FAQ
What is a good revenue per visitor?
There is no universal benchmark, because RPV depends on price point, traffic source and business model. A store selling $500 products and one selling $15 products will have very different RPVs. Compare your RPV with your own past numbers, by page, device and traffic source, and try to raise it.
Is revenue per visitor the same as average revenue per user?
Close, but not always. Revenue per visitor is usually revenue divided by everyone who visited. GA4’s ARPU divides total revenue, including ad revenue, by active users only. Check the definition before you compare the two.
Should RPV be calculated per session or per user?
Either can work if you stay consistent. For A/B tests, per visitor usually fits better, because most testing tools split traffic by visitor. Per session is common in lead gen reporting, where it is often called value per session.
Why did my conversion rate go up but RPV go down?
Because the extra conversions were worth less. A discount, a cheaper default option or a looser lead form can bring in more orders or leads with lower value. RPV shows that trade-off, which is why it is a better primary metric for most tests.
Sources
I’m George (Djordje) Peric, a CRO designer, CXL certified in Conversion Optimization and Ecommerce Marketing. I design ads, landing pages and funnels and A/B test them.