Adjusting Pre-Peak RPV Lift For BFCM Mobile Traffic Share
BFCM week runs ~75% mobile on Shopify while October sits near 60%. If your winning variant over-indexed on desktop, here's how to reweight the RPV lift before you commit a peak-week number.
Quick answer
Split your October RPV lift into mobile and desktop lifts, then re-average using BFCM's expected device mix (roughly 75% mobile / 25% desktop on Shopify) instead of October's ~60/40. If your winner over-indexed on desktop, the reweighted lift will land lower than the blended October number — sometimes by 30-50%. Commit the reweighted figure, not the raw one.
Adjusting Pre-Peak RPV Lift For BFCM Mobile Traffic Share
Reweighting an October RPV lift by BFCM's expected device mix so the peak-week projection reflects mobile-heavy traffic, not October's blend.
A pre-peak A/B test measures revenue per visitor under October's device split — typically around 60% mobile, 40% desktop on Shopify. BFCM week shifts materially: mobile share climbs to 75%+ as shoppers buy from bed, on lunch breaks, and off push notifications. If your winning variant lifts desktop RPV by +6% but only +1% on mobile, the blended October lift (+3%) overstates what you'll see during peak, when three in four sessions are the weaker-performing segment.
The adjustment: compute per-device lifts separately, then re-average them using BFCM's expected device mix. The result is a device-weighted RPV lift you can plug into a revenue forecast without over-promising.
This matters most when your winning variant touches a UI element that behaves differently across devices — a sticky add-to-cart bar, a size-guide modal, PDP image gallery, or checkout accelerator placement. Anything hover-dependent or above-the-fold-on-desktop-but-buried-on-mobile will produce asymmetric lifts you can't afford to average away.
Why the October blend overstates peak-week lift
October traffic on most Shopify stores runs about 58-62% mobile, 38-42% desktop. Shoppers researching gifts and building carts still use desktop meaningfully. BFCM changes the context: promotional pushes from email and SMS hit phones, social ad clicks land in in-app browsers, and the desktop-at-work pattern collapses on a Friday holiday.
The empirical result across Shopify apparel and beauty stores: mobile share climbs to 72-78% during BFCM week, peaking Black Friday morning and Cyber Monday evening. A test winner that quietly relied on desktop performance loses ground when the mix shifts under it.
The trap
A blended +3% October lift with a device split of +1% mobile / +6% desktop reweights to roughly +2.25% at a 75/25 BFCM mix. That's a 25% haircut on your peak-week revenue commit — the difference between hitting your number and missing by six figures on an €8M store.
How to detect the device-lift gap in your test
In your experimentation tool, segment the RPV lift by device before you declare a winner. Look at three numbers: mobile RPV lift, desktop RPV lift, and the mobile share of sessions in the test window. If mobile and desktop lifts are within 1 percentage point of each other, the reweighting is cosmetic and you can skip it.
If the gap is 3 points or more, reweight. Also check whether either device segment reached significance on its own — a +6% desktop lift on 400 desktop conversions is a very different signal than the same lift on 4,000. Pair the device split with the confidence interval per segment before you trust the split at all.
The reweighting math, worked on an apparel example
The formula: adjusted_lift = (mobile_share_bfcm × mobile_lift) + (desktop_share_bfcm × desktop_lift). Nothing more. You're replacing October's device weights with peak-week weights and re-blending the per-device lifts you already have.
Worked example. A Shopify apparel store tests a new PDP size-guide component from Oct 5-22. Blended RPV lift: +3.1%. Segmented: mobile +1.4%, desktop +5.8%. October mix in the test: 61% mobile. Expected BFCM mix: 76% mobile (from last year's GA4 data). Adjusted lift = (0.76 × 1.4%) + (0.24 × 5.8%) = 1.06% + 1.39% = +2.45%. That's the number that goes into the peak-week revenue forecast, not the +3.1%.
Pull your peak device mix from GA4, not intuition
Filter last year's GA4 sessions to Nov 24 - Dec 2 (or your equivalent BFCM window), then look at Device Category share. If you migrated to GA4 mid-2023, import the historical range so you're not extrapolating from four weeks of data. This is exactly what the historical import step of a pre-peak audit is for.
What to do once you have the adjusted lift
Feed the adjusted lift into your peak-week revenue forecast in place of the raw October figure. The full pipeline is covered in Forecasting Black Friday Revenue From A Pre-Peak RPV Test — this adjustment is the device-mix step inside that model.
Then hand finance the reweighted number, not the blended one. The CFO-ready BFCM revenue commit from a +3% October RPV test walks through how to frame the adjusted figure alongside a confidence band, so the commit survives contact with a mobile-heavy peak week instead of unravelling in the Monday post-mortem.
Common questions about device-weighted RPV forecasts
Use your own store's prior-year GA4 data for the Nov 24 - Dec 2 window if you have it. In the absence of that, 74-78% mobile is the typical range for Shopify apparel, beauty, and accessories stores. Electronics and home goods skew slightly less mobile-heavy (68-73%).
Ideally yes. If the desktop segment isn't significant on its own, the +5.8% you're plugging into the reweighting formula is noisy. Report the adjusted lift as a range using each segment's confidence interval, not a single point estimate.
Run the reweighting anyway — a directional adjusted lift beats a blended figure that's structurally wrong. Widen your confidence band to reflect the shorter runtime and communicate the adjusted number as a range to finance.
Treat tablet as its own segment if it's more than 5% of sessions; otherwise bucket it with desktop, since tablet UX behaves closer to desktop for most Shopify themes. Check whether your winning variant renders identically on tablet before deciding.
Then the reweighting works in your favour — the BFCM projection will be higher than October's blended lift. Same math, different direction. This is why device-segmenting the lift is worth doing even when you expect a favourable result.
BFCM shifts channel mix too — more email, SMS, and paid social, less organic search. Those channels also skew mobile. The device reweighting captures most of that indirectly, but if a specific channel drives a different device pattern (paid social is nearly 90% mobile), forecast at the channel × device level for higher-stakes commits.
Yes, though the effect is usually smaller. Mobile AOV runs 8-15% below desktop on most Shopify stores. If your peak-week AOV forecast uses October's blended figure, apply the same device-mix reweighting for a cleaner revenue projection.
Most experimentation tools store device as a dimension automatically — re-slice the results retroactively. If yours truly can't, you can approximate by pulling the RPV delta per device from GA4 for the treatment and control cohorts, though the noise is higher.
It applies to both. Conversion rate typically has a wider device gap than RPV (mobile CVR is often 40-55% of desktop CVR), so the reweighting has an even larger effect on CVR-based forecasts. Reweight whichever metric you're using as your headline lift.
When mobile and desktop lifts are within one percentage point of each other, or when your BFCM mobile share is expected to be within three points of your October share. Below those thresholds the adjustment moves the forecast by less than 0.3 points — noise, not signal.
Test ideas before you ship them
Run unlimited A/B tests, attach hypotheses to outcomes, and build a searchable archive of what works — and what doesn't.