Revenue per visitor (RPV) is the revenue your store makes for each visit: total revenue divided by the number of visitors (or sessions) in the same period. It is also equal to conversion rate × average order value. RPV tells you what a visit is worth, so you can compare traffic sources and decide how much you can pay to bring one more visitor to your store.
How do you calculate revenue per visitor?
RPV = revenue ÷ visitors
Or, with the two parts that drive it:
RPV = conversion rate × average order value (AOV)
Both give the same answer, as long as you use the same period and the same definition of a visitor. Before you calculate, decide three things and keep them fixed:
- Which revenue. Gross sales, or sales after refunds? In GA4, "purchase revenue" is revenue from purchases minus refunds. Shopify's sales reports have their own gross and net figures. Choose one.
- Which visitor. Sessions (every visit counts) or users (each person counts once). Revenue per session is usually lower than revenue per user, because people come back.
- Which period. Revenue and traffic must cover the same dates. Use full weeks or full months, so weekdays and weekends are balanced.
A worked example
The numbers below are made up to show the math.
A store has 40,000 sessions in a month, 800 orders and $48,000 in revenue.
- RPV = $48,000 ÷ 40,000 = $1.20 per session
- Conversion rate = 800 ÷ 40,000 = 2%
- AOV = $48,000 ÷ 800 = $60
- Check: 2% × $60 = $1.20
Now two changes, each tested alone:
| Change | Conversion rate | AOV | RPV |
|---|---|---|---|
| Starting point | 2.0% | $60 | $1.20 |
| A bundle raises AOV by 10% | 2.0% | $66 | $1.32 |
| A faster page raises conversion by 10% | 2.2% | $60 | $1.32 |
Both changes give the same lift. That is the point of RPV: it shows the result of the whole visit, not of one step.
Split it by traffic source
The store's $1.20 is an average. Split by source, it looks like this (same made-up store):
| Source | Sessions | Revenue | RPV |
|---|---|---|---|
| Meta ads | 20,000 | $18,000 | $0.90 |
| Organic search | 10,000 | $12,000 | $1.20 |
| Direct | 6,000 | $8,400 | $1.40 |
| 4,000 | $9,600 | $2.40 | |
| Total | 40,000 | $48,000 | $1.20 |
Half the visits come from Meta ads, and they are worth less than the average. If you want to raise the store's RPV, start there.
Use RPV to set a maximum cost per visit
If a visit from Meta ads is worth $0.90 in revenue and your margin after product, shipping and payment fees is 40%, each visit brings $0.36 of margin on the first order. Paying more than $0.36 per click loses money unless buyers come back and order again. Our break-even ROAS calculator works the same idea from the ad side.
RPV vs conversion rate vs AOV
| Metric | Formula | Question it answers | What it hides |
|---|---|---|---|
| Revenue per visitor | Revenue ÷ visitors | What is one visit worth? | Whether the change came from more buyers or bigger orders |
| Conversion rate | Orders ÷ visitors | Did the visit turn into a sale? | How much each buyer spent |
| Average order value | Revenue ÷ orders | How big is each order? | How many visitors never bought |
| ARPU | Revenue ÷ active users | What is each user worth over a period? | Visit-level behavior; fits subscriptions and apps better |
Use conversion rate to judge the path to purchase, AOV to judge the cart, and RPV to judge the result.
Where to find RPV in Shopify and GA4
- Shopify. Shopify Analytics shows total sales and sessions for the same date range, so you can divide one by the other, per channel or per device. Note that Shopify changed how it counts sessions from 21 to 23 September 2026: sessions no longer end at midnight UTC, some sessions without a pageview now count, and identified bots are removed by default. Your session count, and so your conversion rate and RPV, can change across those dates even if sales did not.
- GA4. GA4 has per-user metrics such as ARPU and average purchase revenue per active user. For revenue per session, build an exploration with purchase revenue and sessions by source or device and divide them. GA4 excludes known bots automatically, and you can't see how much traffic it removed.
- A spreadsheet. If the tools disagree, export revenue from your store and sessions from one analytics tool, by source, and calculate RPV per row. Write the definition at the top of the sheet.
Why RPV can mislead you
- Mixed denominators. Comparing revenue per session from one tool with revenue per user from another gives you two different metrics with one name.
- Refunds and returns. A promotion can lift RPV this month and return orders the next. Check net revenue when returns are high.
- Bots and junk traffic. Fake visits push RPV down. A sudden drop in RPV with a jump in sessions is often bot traffic, not lost buyers.
- The blended average. A good month on email can hide weak paid traffic, as in the example above.
- Small numbers. With a few hundred sessions, a single large order moves RPV a lot. Wait for enough orders before you decide.
- Taxes, shipping and currency. Include or exclude them the same way every time, and convert currencies before you compare stores or markets.
Is there a good RPV benchmark?
Not one you can use. RPV depends on your price (a $300 product and a $20 product have very different RPVs), your niche, your share of returning buyers and your traffic mix. Published benchmarks also mix sessions and users. Compare your RPV with your own past months, between your traffic sources, and before and after each change you make.
How to raise revenue per visitor, step by step
- Split before you fix. Calculate RPV by source, device, landing page and new vs returning visitors. Pick the segment with many visits and low RPV.
- Fix the traffic first. If an ad promises one thing and the page shows another, people leave. Send each ad to the product or page that matches its promise.
- Fix the path to purchase. Fast pages on mobile, a clear price and offer above the fold, reviews near the button and few checkout steps. Our guide to raising e-commerce conversion rates goes through each one.
- Raise the order value. Bundles, "buy 2, save more" offers, a free-shipping threshold just above your current AOV, and an add-on after purchase.
- Measure full weeks. Change one thing at a time and compare at least one full week before and after, on the same denominator.
Can you estimate a competitor's RPV?
Not exactly. Only the store owner sees its real sales and sessions. You can get a rough order of size by dividing an estimated monthly revenue by estimated visits.
Example from SearchTheTrend data for September 2026:
| Product | Estimated monthly revenue | Store visits | Rough revenue per visit |
|---|---|---|---|
| Omnilux Contour Face | $610K–$1.5M | 260K | About $2.35–$5.77 |
| The Sauna Pod 2.0 | $350K–$860K | 110K | About $3.18–$7.82 |
Read this with care. Both inputs are estimates. The revenue is for that one product, while the visits are for the whole store, so this is not the store's real RPV. And estimated visits are not the same as sessions in your own analytics. Use it only to compare the size of different markets, for example to see whether a niche earns cents or dollars per visit. To learn how traffic estimates are made, see our guide on how to estimate website traffic.
How to do this with SearchTheTrend
- In Products, filter by niche and country and open a product. You see its estimated monthly revenue range, store visits and market by country, month by month.
- In Brands, open a competing store to see its monthly visits, best-selling products, tech and the Meta ads it runs.
- Put two or three competitors side by side and divide revenue by visits for a rough range, as in the table above.
These numbers describe other stores, not yours. Your own RPV always comes from your store and analytics data. The free plan needs no card.
FAQ
How do you calculate revenue per visitor?
Divide the revenue of a period by the number of visitors or sessions in the same period. It is also equal to conversion rate multiplied by average order value.
Is revenue per visitor the same as revenue per session?
Not exactly. A visitor can come back several times, so revenue per session is usually lower than revenue per unique visitor. Pick one denominator and use it every time you compare.
What is a good revenue per visitor?
There is no single good number, because RPV depends on your price, niche and traffic mix. Compare it with your own past months and between your traffic sources, not with a general benchmark.
What is the difference between RPV and AOV?
Average order value is revenue per order, so it only looks at buyers. RPV is revenue per visit, so it also counts the people who did not buy.
Can I see a competitor's revenue per visitor?
Not the real number, because only the store owner sees its sales and sessions. You can make a rough estimate by dividing an estimated revenue range by estimated visits, as long as you treat it as an order of size, not a fact.