The JournalConversion Rate Optimization

Revenue Per Session Benchmarks (2026)

RPS benchmarks: Littledata Shopify median $1.94 (Home $2.58–Beauty $1.67), why RPS beats vanity CVR or AOV, and why panel medians do not multiply.

TL;DR: Revenue per session benchmarks start at Littledata’s Shopify median of $1.94 per session (top 20% above $4.06). Niche medians run Beauty $1.67, Fashion $1.79, Supplements $2.28, and Home $2.58. RPS is the scoreboard when conversion rate and average order value trade off. Do not multiply published medians into a fake target.

Introduction

Merchants ask for revenue per session benchmarks after a “win” that did not pay the rent. Conversion rate ticked up. Average order value looked healthier. Revenue stayed flat. The missing meter was usually revenue per session.

Revenue per session benchmarks matter when you decide whether a test, a channel, or a niche target is actually earning money per visit. This page sits next to Shopify conversion rate benchmarks, average order value benchmarks by industry, add to cart rate benchmarks by niche, and checkout conversion rate benchmarks.

  • Littledata’s Shopify panel puts all-store median revenue per session at $1.94, top 20% above $4.06, and top 10% above $6.18 across 421 stores, generated October 2, 2026 from 90 days ending September 26, 2026 (Littledata RPS).
  • Niche medians in the same panel: Beauty & Skincare $1.67, Fashion & Apparel $1.79, Health & Supplements $2.28, Home & Furniture $2.58 (Littledata RPS).
  • On your store, RPS (or revenue per visitor) is the meter that catches vanity CVR wins and vanity AOV wins. Shogun’s framing is explicit: a change that raises CVR while cutting AOV harder will show up as an RPV decline (Shogun).
  • The same Littledata hub still publishes purchase CVR median 1.4% and AOV median $110. Those are sibling scorecards, not ingredients you multiply across panel medians (Littledata hub).
  • There is no public dataset for device-split RPS on Littledata’s dedicated RPS page today, and no public dataset for feat. RPS. Refuse invented rows.

What Is Revenue Per Session Benchmarks

Revenue per session benchmarks are published reference points for how much purchase revenue a typical session generates, usually in US dollars, and always tied to a named merchant panel and time window.

The formula is direct. RPS equals purchase revenue divided by sessions. Closely related is revenue per visitor (RPV), which divides by visitors instead of sessions. Shogun and many CRO teams teach RPV ≈ conversion rate × average order value as a store-level identity: of the people who showed up, what share bought, and how much did buyers spend (Shogun). Littledata’s published meter is session-based. Label session vs visitor before you compare screenshots.

Community language already wants this meter. On r/shopify_growth, operators push back on blended Shopify conversion slogans and ask for category context instead of one hero percentage (r/shopify_growth). That thread is half a step from RPS. If CVR looks “good” in a low-AOV niche, RPS tells you whether the dollars followed.

This article owns the RPS ladder and the diagnostic rule. Niche dollars live in average order value benchmarks by industry. Sitewide conversion percentiles live in Shopify conversion rate benchmarks.

Why Revenue Per Session Benchmarks Matter

CVR and AOV can lie politely. RPS is ruder, which is why it is useful.

  • It is the net of the tradeoff. A free-shipping threshold, a bundle, or a discount can raise AOV while thinning conversion. If RPS falls, the “AOV win” failed (Shogun; free shipping threshold benchmarks).
  • Niche sets the dollar floor. Littledata’s Home median RPS ($2.58) is more than 50% above Beauty ($1.67) on the same tracking stack. Comparing both to one “good Shopify RPS” slogan is malpractice (Littledata RPS).
  • It explains the Beauty vs Home offset. Beauty’s higher purchase CVR (~2.6%) with lower AOV ($66) and Home’s lower CVR (~0.82%) with higher AOV ($239) are not contradictions. Their RPS medians ($1.67 vs $2.58) show how the mix lands (Littledata hub; Littledata RPS).
  • Channels inherit the same trap. A channel can convert often on tiny baskets or convert rarely on large ones. Scaling on CVR alone without RPS can buy the wrong traffic (Shogun).
  • Creator traffic still pays in RPS. Affiliates and co-branded storefronts on feat. send sessions into your economics. A partner channel with “great CVR” and weak RPS is still a weak channel.

How Revenue Per Session Benchmarks Work

Revenue per session benchmarks work when you read a labeled panel’s RPS ladder, then use store-level CVR and AOV as diagnostics—not as numbers you multiply from other people’s medians. Use Littledata for Shopify RPS percentiles and niche rows. Use Shogun’s RPV teaching for the test-readout rule. Keep session vs visitor labeled.

The RPS Identity Ladder

Layer What it answers Public anchor
Measured RPS How many dollars per session did we earn? Littledata median $1.94
Niche RPS Is our vertical’s floor different? Home $2.58 → Beauty $1.67
Store diagnostic Did a CVR/AOV tradeoff net positive? Your RPS (or RPV) before vs after
Refuse “Target RPS = panel median CVR × panel median AOV” Not valid across medians

Sources: Littledata RPS, Shogun.

On one store for one period, revenue ≈ orders × AOV and RPS ≈ (orders ÷ sessions) × AOV when you align definitions carefully. Across a panel, median CVR × median AOV does not equal median RPS. Different stores sit in different parts of each distribution. If you multiply Littledata’s 1.4% CVR by $110 AOV and call $1.54 “the” target, you invented a third number that is not the published $1.94 RPS median.

Shopify RPS by industry (Littledata)

Niche Median RPS Top 20% floor Stores
Beauty & Skincare $1.67 $4.48 33
Fashion & Apparel $1.79 $3.77 69
Health & Supplements $2.28 $3.58 33
Home & Furniture $2.58 $4.91 54
All Shopify stores $1.94 $4.06 421

Source: Littledata revenue per session. Sector rows publish only when at least 30 stores qualify. Food, Pet, Electronics, Jewelry, and other thin niches are unpublished here—same rule as the AOV and ATC spokes.

All-store RPS percentiles (Littledata)

Band Revenue per session
Bottom 10% $0.58
Bottom 20% $0.95
Median $1.94
Top 20% $4.06
Top 10% $6.18

Source: Littledata RPS. The mean ($2.97) sits above the median because high-RPS stores pull it. Prefer median and niche top-20% floors for planning.

CVR and AOV as sibling scorecards (same hub)

Niche Median purchase CVR Median AOV Median RPS
Beauty & Skincare ~2.6% $66 $1.67
Health & Supplements ~2.6% $76 $2.28
Fashion & Apparel ~1.3% $98 $1.79
Home & Furniture ~0.82% $239 $2.58
All stores 1.4% $110 $1.94

Sources: Littledata hub, Littledata AOV, Littledata RPS.

Read the three columns together. Do not multiply the first two published medians and expect the third. Home’s high AOV with low CVR still clears the highest niche RPS in this set. Beauty’s high CVR with low AOV lands near the bottom of the RPS niche ladder.

RPS vs RPV (session vs visitor)

Meter Denominator Common publisher
Revenue per session Sessions Littledata
Revenue per visitor Visitors / users Many CRO guides; Shogun RPV teaching

If your analytics shows more sessions than visitors, RPS will sit below RPV for the same revenue. When you paste a “good RPV” from a blog next to Littledata’s RPS ladder, you may be comparing different denominators. Keep the label on the chart.

Shogun’s considered-purchase note still helps: categories like Home & Garden, Consumer Electronics, and Autos often sit in a lower median CVR band (about 1.26%–1.39% in Shogun’s conversion report framing) while carrying higher baskets. That is an RPV/RPS story, not a broken store by default (Shogun).

What RPS does not replace

RPS does not tell you margin, refund rate, or LTV. A high-RPS channel that returns half the orders is not a win. Pair RPS with contribution margin and, for recurring catalogs, retention. It also does not replace stage meters: if RPS is weak, diagnose with ATC by niche, checkout completion, and cart abandonment reasons.

Device note

Littledata’s dedicated RPS page currently publishes the all-store and industry ladders without a mobile/desktop RPS split in the same payload. Mobile vs desktop still matters on sibling meters: session ATC and purchase CVR both skew by device on the hub. Segment RPS in your own GA4 or Shopify reports by device even when the public panel does not yet show that cut. There is no public dataset for niche×device RPS in this Littledata panel today.

How to Benchmark Revenue Per Session

Benchmark by locking the RPS definition, matching a niche row, then judging every CVR or AOV test on RPS direction.

  1. Write the formula on the dashboard. Purchase revenue ÷ sessions (RPS) or ÷ visitors (RPV). Do not switch mid-quarter (Littledata RPS).
  2. Match your niche median before the all-store median. Beauty $1.67 and Home $2.58 are different jobs (Littledata RPS).
  3. Put CVR and AOV beside RPS, not above it. Use Shopify conversion rate benchmarks and AOV by industry as context. Never multiply those panels’ medians into a synthetic RPS target.
  4. Score tests on RPS (or RPV) first. If AOV rises and RPS falls, the tactic failed as a revenue move (Shogun).
  5. Split channels and devices in your analytics. Public niche RPS is a floor check. Your paid social vs branded search RPS will diverge.
  6. Fix the funnel stage that is actually leaking. Weak RPS with healthy AOV usually points at conversion. Weak RPS with healthy CVR usually points at basket size. Use ATC, checkout, and shipping-threshold spokes accordingly.

Frequently Asked Questions

Q: What are revenue per session benchmarks in 2026? A: On Littledata’s Shopify panel, the all-store median is $1.94 per session, with top 20% above $4.06. Niche medians run Beauty $1.67, Fashion $1.79, Supplements $2.28, and Home $2.58 across the published sectors.

Q: What is a good revenue per session for a Shopify store? A: A good RPS beats your niche median without wrecking margin. Orientation: all-store top 20% starts near $4.06; Home top 20% near $4.91; Beauty top 20% near $4.48. Always keep the panel and niche label attached.

Q: Is revenue per session the same as revenue per visitor? A: Not always. RPS divides by sessions; RPV divides by visitors. Littledata’s public ladder is session-based. Shogun and many CRO guides teach RPV. Compare only when the denominator matches.

Q: Can I multiply average conversion rate by average order value to get RPS? A: On your own store for a single period, CVR × AOV is a useful diagnostic when definitions align. Across published panels, median CVR × median AOV is not median RPS. Use Littledata’s measured RPS ladder instead of inventing one.

Q: Why did my AOV go up while revenue per session fell? A: You likely filtered buyers or thinned conversion more than you grew baskets. Shogun’s RPV framing treats that as a failed revenue test even if AOV looks like a win. Re-check the offer, threshold, and traffic mix.

Conclusion

Revenue per session benchmarks turn two vanity meters into one money meter. Littledata’s Shopify median is $1.94, with Home near $2.58 and Beauty near $1.67. Use those ladders as floors. Use your own RPS to judge every CVR and AOV tradeoff. Do not multiply other people’s medians and call the product a target.

If you built the product and need people with an audience to sell it, start on feat. at https://www.feat.press.