RPS vs AOV: Which Metric Should Drive Your EC Decisions?

"We ran a campaign to lift average order value (AOV), but revenue barely moved." If you run an EC store, you have probably hit this mismatch. The usual cause is that you were watching AOV alone and the other half — conversion rate (CVR) — quietly slipped.

AOV (average order value) and RPS (revenue per session) both measure revenue, but they cover different ranges. AOV is the spend per buyer; RPS is the revenue per visitor. The bottom line: measure pricing moves with AOV, judge channel and campaign efficiency with RPS — and remember the two are linked by RPS = AOV x CVR. That is where this article starts.

We cover how RPS and AOV differ, the formula that links them, when to use each, and the classic "raised AOV but RPS fell" pattern — all from an EC operator's point of view.

TL;DR#

1. AOV = spend per buyer, RPS = revenue per visitor

   AOV is the average value of one order (revenue / orders). RPS is revenue per session (revenue / sessions). The denominator — orders vs visits — changes the meaning.

2. They are linked by RPS = AOV x CVR

   RPS is average order value times conversion rate. Look at AOV alone and you miss the CVR gap, misreading revenue efficiency.

3. AOV for pricing moves, RPS for channel comparison

   Measure cross-sell and bundle tactics with AOV. Compare the overall efficiency of channels and ads with RPS, which also reflects how well visitors convert.

1. How RPS and AOV differ#

RPS and AOV sound alike, but the denominator of the division is different.

• AOV (Average Order Value) = revenue / orders. How much a buyer spent in one order — the "spend per buyer."
• RPS (Revenue Per Session) = revenue / sessions. How much revenue each visit produced — the "revenue per visitor."

The difference is the denominator. AOV counts only people who bought, while RPS divides by all visits, including non-buyers. So AOV is "unit price," and RPS bundles in "how well it sells."

Picture two stores both with an AOV of 5,000 yen. If one converts 1 in 100 visitors and the other 1 in 20, the revenue per visit is wildly different. AOV is 5,000 yen for both, but RPS diverges sharply. AOV alone cannot show that "how well it sells" gap.

2. The formula linking RPS and AOV#

RPS and AOV connect cleanly through conversion rate (CVR).

RPS = AOV x CVR

Here is why. AOV is "revenue / orders" and CVR is "orders / sessions." Multiply them and orders cancel out, leaving "revenue / sessions" = RPS. In other words, RPS is average order value multiplied by conversion rate.

The chart above fixes AOV at 5,000 yen and varies only CVR. At a CVR of 2.0%, RPS is 100 yen; at 5.0%, it is 250 yen. With the same unit price, 2.5x the conversion rate means 2.5x the RPS. Look at AOV and conclude "our unit price is high enough," and if CVR is low, revenue per visit stays small. Only RPS reveals that gap.

3. Which metric to use, and when#

AOV and RPS are not "one is better" — you pick by what you want to measure.

Roughly: use AOV for tactics that move the unit price itself, and RPS to compare whether channels or campaigns are good. And the more a tactic moves AOV, the more you must sanity-check with RPS whether the total actually grew — which leads to the next trap.

4. The trap: raising AOV can lower RPS#

Tactics that raise AOV often lower conversion rate (CVR). Push the unit price up too hard and more people hesitate to buy.

The chart above compares before and after one tactic. Before: AOV 4,000 yen x CVR 5.0% = RPS 200 yen. The store then forced a high-priced bundle, lifting AOV to 6,000 yen (+50%). But the higher hurdle cut CVR in half to 2.5%, and as a result RPS fell from 200 to 150 yen.

Watching AOV alone, this looks like a "+50% unit-price win." But by RPS, revenue per visit actually dropped. Unless you sanity-check a pricing move against RPS, paired with the CVR decline, you can mistake a revenue-losing tactic for a success. The real pass/fail of an AOV-lifting tactic is decided by RPS, not AOV.

RevenueScope solution

Misjudging by AOV alone, and failing to track how RPS moves before and after a tactic, share one root: AOV, CVR, and RPS are not visible together on one screen. Most analytics tools show AOV and CVR on separate screens and never surface RPS (= AOV x CVR) at all.

RevenueScope lines up RPS, AOV, and CVR for every channel on the same screen. It computes the AOV x CVR product (= RPS) automatically, so you can instantly separate a channel with "high unit price but low revenue per visit" from one with "modest unit price but high conversion and top RPS."

RevenueScope dashboard (demo data shown). AOV, CVR, and RPS line up on one yardstick, exposing the gap between unit price and revenue efficiency.

In the screen above, Google search has the highest AOV here at 5,000 yen, but its CVR of 2.5% holds RPS to just 125 yen. The email newsletter, with a slightly lower AOV of 4,600 yen, rides a 7.5% CVR to the top RPS on the screen at 345 yen. "High-AOV channel" does not mean "efficient," and lining AOV up next to RPS shows it instantly. After a pricing move, check on the same screen whether RPS rose — and you avoid the trap from section 4. That is the next step in using AOV and RPS to grow revenue.

5. FAQ#

Q. RPS or AOV — which should be the KPI?

Both. They play different roles, so one is not enough. Track day-to-day pricing tactics (cross-sell, etc.) with AOV, and judge the overall quality of channels and campaigns with RPS. If you must pick one, RPS — which includes CVR and reflects "revenue per visit" — is closer to whole-business efficiency.

Q. Should I prioritize channels with high AOV?

AOV alone cannot decide. High AOV with low CVR still means low RPS. Rank channel priority by RPS (= AOV x CVR), not by AOV.

Q. Do RPS levels vary by industry?

Yes. Product price and purchase frequency move RPS a lot. In practice, tracking "is it rising?" across your own channels and periods is more useful than comparing to other companies. The basics of RPS are covered in RPS (revenue per session): the metric, formula, and how to pull it in GA4.

Conclusion#

RPS and AOV both measure revenue, but cover different ranges. Three takeaways:

• AOV is spend per buyer, RPS is revenue per visitor — the denominator (orders vs visits) changes the meaning
• RPS = AOV x CVR — look at AOV alone and you miss the CVR gap, misreading efficiency
• AOV for pricing moves; RPS for channel comparison and final checks — the more a tactic moves AOV, the more you sanity-check the total with RPS

Raising the unit price looks attractive, but the pass/fail is decided by RPS, not AOV. Lining up AOV, CVR, and RPS on one screen — and seeing the gap between unit price and revenue efficiency — is where growing revenue begins.

Related articles#

• RPS (revenue per session): the metric, formula, and how to pull it in GA4
• AOV (average order value): formula and how to raise it
• RPS vs CVR: which metric should you use to evaluate ads?
• Lifting CVR and AOV together: a revenue-breakdown framework
• Simulating simultaneous CVR and AOV improvement

References#

• Google Analytics Help "Ecommerce reports (average order value, conversion rate)" Help 2026
• RevenueScope "RPS (revenue per session): definition and formula" /en/news/rps-revenue-per-session-guide 2026