Mobile vs Desktop RPV Gap by Traffic Source
Mobile revenue per visitor sits well below desktop on almost every DTC store, but the size of the gap depends heavily on where the traffic came from. Here's how to read the per-source gap as a CRO diagnostic instead of an audience quirk.
Mobile vs Desktop RPV Gap by Traffic Source
The difference in revenue per visitor between mobile and desktop sessions, segmented by the channel that referred each session.
Mobile vs Desktop RPV Gap by Traffic Source is the practice of comparing revenue per visitor (RPV) across device categories, but split by acquisition channel — paid social, Google Shopping, brand search, email, direct — rather than looking at a single store-wide number. On most online stores, mobile RPV runs 30-60% below desktop. That store-level average hides the useful signal: TikTok traffic often converts at near-parity across devices because it's a mobile-native audience, while Google Shopping stays desktop-heavy because it competes on price comparison. Reading the gap per source tells you whether you have a mobile UX problem, an intent-mismatch problem, or a channel-mix problem.
The store-wide mobile-desktop RPV gap is one of the most misread numbers in DTC analytics. Every Shopify store shows one. Most teams shrug and blame "mobile users browse, desktop users buy." That framing is comfortable and it's often wrong.
The gap isn't a property of your audience — it's a property of the interaction between channel intent, device context, and your checkout UX. Split RPV by source and the picture changes: some channels arrive with near-identical device RPV, others sit 70% apart. That variance is the diagnostic. The channels that DO close the gap prove your mobile store can convert; the ones that don't tell you exactly where to look.
Typical mobile vs desktop RPV gap by traffic source, DTC stores €1M-€15M annual revenue
| Traffic source | Mobile RPV | Desktop RPV | Gap (mobile vs desktop) | Mobile share of sessions |
|---|---|---|---|---|
| TikTok Ads | €0.85 | €0.95 | -11% | 94% |
| Meta Ads (Instagram) | €1.10 | €1.70 | -35% | 88% |
| Meta Ads (Facebook) | €1.40 | €2.30 | -39% | 78% |
| Organic search (non-brand) | €1.20 | €2.10 | -43% | 70% |
| Organic search (brand) | €2.40 | €3.60 | -33% | 65% |
| Direct | €2.80 | €4.20 | -33% | 62% |
| Email (Klaviyo) | €2.10 | €4.80 | -56% | 72% |
| Google Shopping | €1.30 | €3.40 | -62% | 55% |
Two rows in that table matter more than the rest. TikTok's -11% gap tells you mobile CAN convert at desktop-adjacent rates on your store — the checkout works. Google Shopping's -62% gap tells you comparison-shopping intent doesn't survive the mobile experience, either because of tab-switching friction or because your PDP loses to a competitor's on a 6-inch screen. Neither is a demographic story.
Why the gap varies so sharply by source
Three variables drive per-source gap variance: buying intent at click, cross-device behaviour after click, and how well your mobile PDP + checkout handle that specific intent shape. TikTok clicks are impulse-adjacent and mobile-native, so intent and device match. Google Shopping clicks are deliberate price comparison, and comparison behaviour naturally migrates to desktop where users can hold five tabs open.
Email is the trickiest case. Most Klaviyo campaigns are opened on mobile — 70%+ typically — but the desktop RPV runs roughly double the mobile RPV. That's not because desktop email users are richer. It's because the mobile open triggers a "save for later" behaviour: the recipient opens the email on their phone, taps through, then closes it and re-visits on a laptop that evening to actually buy. The mobile session gets the visit; the desktop session gets the revenue. Reading the Klaviyo gap without accounting for that flow leads to bad conclusions.
Watch out for the cross-device attribution artifact
A narrow mobile-desktop RPV gap can be a genuine UX win — or it can mean your attribution setup is collapsing multi-device journeys onto whichever device closed the sale. If your gap suddenly narrowed after a GA4 config change, suspect the artifact before you celebrate. Compare it against Shopify's raw order-device data, which doesn't stitch sessions.
How to act on the gap you find
Rank your channels by gap size, then work top-down. The widest gaps are where mobile UX is losing the most revenue you're already paying to acquire. For paid social, the gap is often a creative-fit problem: the ad promises one thing, the mobile landing page delivers another, and desktop users are patient enough to reconcile the mismatch while mobile users bounce.
For Google Shopping, the fix is rarely in the ad — it's in the mobile PDP. Comparison shoppers need price, shipping, returns, and social proof visible above the fold on a phone. If your mobile PDP hides shipping cost behind an accordion and pushes reviews to a second scroll, Shopping's gap will stay stubborn no matter how much you optimise the feed. For brand search, a narrow mobile gap is usually a good sign; a wide one suggests loyal customers can't complete checkout on their phones and are waiting until they get to a laptop.
Mobile RPV as % of desktop RPV, by traffic source
Frequently asked questions
Mobile sessions include a heavy share of browsing, tab-switching, and interrupted intent — someone checks a product on the bus and buys from a laptop later. That's the baseline effect. On top of it sit real UX losses: smaller screens make comparison harder, form-fill friction is higher, and payment method availability sometimes differs. The 30-60% store-wide gap combines both.
TikTok is essentially a mobile-native channel — 94%+ of clicks are mobile — and the desktop cohort is small and self-selecting. When the two rates sit close, it means impulse intent survives your checkout on both devices. The deeper mechanic is covered in our spoke on why TikTok RPV barely moves between mobile and desktop, but the short answer is: near-parity is normal for TikTok, not a bug.
Google Shopping surfaces price-comparison intent, and comparison behaviour naturally moves to desktop where users open multiple tabs. Mobile Shopping traffic is also more likely to be top-of-funnel research. The fix isn't always to "fix mobile Shopping" — sometimes the gap is telling you the click is being served too early in the buying journey.
RPV by traffic source tells you which channels drive revenue efficiency. Splitting each channel by device tells you where the mobile experience is losing money you already paid to acquire. It's the difference between a channel-mix decision and a UX-priority decision.
No, that pattern is standard. Recipients open on mobile, mentally bookmark the offer, and complete the purchase on desktop later. It doesn't mean your mobile email experience is broken — it means email drives cross-device intent. Attribution that credits the first touch device will understate email's true mobile contribution.
For Meta, a gap of 30-40% is normal. Above 50% suggests the creative promises something the mobile landing page doesn't deliver — a creative-fit issue rather than a mobile UX issue. Below 20% is either exceptional UX or a sign your desktop cohort is small enough to be noisy.
Yes, always. Brand search behaves like direct traffic — loyal customers with intent — and its gap reflects mobile checkout friction more than acquisition quality. Non-brand search skews earlier-funnel and shows a wider gap for legitimate reasons. Combining them into one "organic search" row hides the signal.
Sometimes. If your gap narrowed sharply after a tracking change, you may be looking at a cross-device attribution artifact rather than a real UX improvement. Cross-check against Shopify's order-device data, which reports the final purchase device without session stitching.
Rank by absolute revenue at risk: (desktop RPV − mobile RPV) × mobile sessions per channel. That surfaces the channel where closing the gap unlocks the most euros, not just the biggest percentage. Usually it's paid social or Google Shopping, not email.
GA4 exposes RPV as a custom metric and lets you segment by device and source/medium, so you can build the table manually. It's tedious and the sampling on large date ranges introduces noise. Tools that import GA4 history and pre-compute per-source device splits — Metricuno included — remove the manual reconciliation.
Get an AI expert review of your site
Paste your URL — Metricuno's AI runs the same heuristic checks a senior CRO consultant would, scoring your page and prioritising the fixes that'll move conversion fastest.