Few things discarded a boardroom gathering akin defending Google Analytics 4 figures that don’t align alongside the store-reported numbers. It erodes rely and leaves everyone alongside an incomplete, misleading picture, and complete the former 12 months I’ve established it harder to get GA4 to do the job it’s set up for. It’s challenged me and my squad to keep a much nearer check, alongside alerts on the tracking we depend on to fairness success.
So, onward of this year’s holiday season, I audited GA4 at eight U.K. ecommerce brands, putting its Q4 numbers for 2024 and 2025 next to shop orders. I expected gaps, but not ones this big, or this fine hidden.
Between Christmas Day 2025 and Jan. 4, 2026, GA4 told a U.K. retailer its income was downward 68% a day on the twelvemonth before. The retailer’s own command records showed a autumn of 13%.
GA4 recorded 81% of the store’s web orders in Q4 2024, 41% in Q4 2025 and fair 32% complete the Christmas period.
Six of the eight stores let me equivalent GA4 to their own command records. At three, GA4 told a extremely distinct story. At two, the biscuit banner had been switching itself off for days or weeks at a time, and GA4 gave no sign item was missing. At the third, GA4 recorded no purchases for five weeks, afterward loaded them in delayed and counted hundreds twice. A fourth store’s GA4 was inundated alongside bots this September.
Most are setup problems that could happen at any store, including yours.
What I Compared
For six brands, I compared GA4 orders alongside web orders, week by week anywhere I could. At two stores, the counts contain several phone or backing orders the phase couldn’t distinct out. I checked all fig against its source. Retailers A to D are the four stores alongside the biggest problems, and Retailer A is the one from the opening. (Disclosure: I activity for a digital agency that has worked immediately alongside all eight brands.)
See also: Why Your Search Data Doesn’t Agree (And What To Do About It)
5 Pitfalls To Look Out For In GA4
A Steady Gap
One brand’s GA4 recorded 76% of its web orders in the two Q4 2024 and Q4 2025, and another’s between 72% and 84% all week of Q4 2025. That’s the form biscuit consent produces, alongside a akin portion of shoppers declining tracking all week.
What to appearance for: A grasp charge (GA4 orders as a portion of shop orders) that stays in the identical collection all week. Allow for it, and use GA4 for trends, not totals.
A Cookie Banner That Switched Itself Off
Retailer A’s GA4 sessions dropped out in blocks of days, and all obstacle ended on the 14th of the month.
Retailer B’s blocks ended on the 20th. Its GA4 recorded 94% of the store’s orders in Q4 2024 and 36% in Q4 2025, and showed income downward 69% during the store’s net revenue rosy 18.5%.
The logic was the biscuit banner, twice over. Both stores moved to a new consent setup in 2025, so a portion of shoppers stopped being tracked: the dependable benevolent of gap. Each consent scheme additionally covered a set figure of leaf views a month, and formerly they ran out, the banner stopped showing until the next billing date. At Retailer B, GA4 recorded up to 68% of orders in weeks the banner stayed up and between 10% and 22% in weeks it switched off. GA4 kept receiving several data, so nothing looked broken, and the missing days peruse akin a decline in sales.
In the Black Friday billing cycle, Retailer A’s allowance ran out on December 1, and GA4 didn’t regain until December 15.
What to appearance for: Sessions dropping out in blocks that commencement or end on the identical date all duration during shop orders transport on. Size your consent scheme for highest traffic and create certain its bounds warnings attain marketing, not fair developers.
A Blackout And A Late Backfill
From Oct. 28 to Dec. 4, 2025, Retailer C’s shop recorded 2,215 orders, and GA4 recorded no purchases at all.
On Dec. 9, GA4 recorded 1,261 orders in one day, 1,000 of them alongside command numbers from inner the gap. Blackout orders were being loaded in late, and all but five went to Unassigned.
What to appearance for: Days alongside sessions but no purchases, and abrupt runs of purchases in Unassigned.
The Same Order Counted Twice
Google’s direction on transaction IDs says GA4 “deduplicates acquisition events alongside the identical transaction ID,” although lone from the identical user. At Retailer C, 657 of the 3,365 command numbers GA4 recorded in Q4 2025 had additional than one acquisition event, adding 735 purchases to its total. Across the quarter, the errors nearly canceled out: GA4 recorded 4,100 purchases against 4,501 shop orders. Check lone the quarterly total, and it looks fine.
What to appearance for: In a GA4 exploration, catalog the acquisition event figure for all transaction ID. Anything complete one is twice counting.
Visitors Who Weren’t Shoppers
Its known bot-traffic exclusion filters out “known bots and spiders,” but another bots that run a site’s code akin a browser figure as visitors.
Retailer D’s GA4 recorded 23,187 sessions on September 27, 2026, and 25,622 the next day, against 300 to 900 a day in mid-September. Almost all were direct, desktop Chrome visits averaging concerning a second of engagement. Search Console clicks didn’t move.
What to appearance for: Session spikes that orders don’t follow. Exclude them from reports and obstacle them at your firewall, sparing verified crawlers akin Googlebot.
Use Search Console As An Early Warning
Search Console counts a click whenever a outcome sends person to a leaf exterior Google, any the site’s tags are doing. Divide GA4’s Google integrated sessions by Search Console clicks all week, and a tracking nonaccomplishment shows up as a abrupt drop.
In Retailer C’s blackout, Google sent 4,244 clicks in the week of November 3, and GA4 recorded 57 Google integrated sessions.
See also: Why Is Organic Traffic Down? Here’s How To Segment The Data
What It Does To Budget Decisions
Retailer A’s Q4 web orders rosy from 5,874 to 7,686 during GA4 showed them falling by a third. GA4 additionally had Google Ads’ come back on expend falling from 8.07 to 4.79 and integrated hunt income nearly halving. Matched to shop orders in a premium multi-touch attribution tool, Google Ads’ come back rosy from 4.42 to 7.93 on 20% small spend, and income attributed to integrated and straightforward visits rosy 58%. The attribution models differ, but they shouldn’t item in contrary directions. Cutting either conduit on GA4’s numbers would have pulled prosperity from channels that were working, which is why I fairness them together against shop orders.
Retailer C’s GA4 put income from Google, paid and organic, downward 86% during the store’s net revenue rosy 4.8%.
See also: Google Ads Budget Misallocation Is More Common Than You Think – And Harder To Spot
A Check To Run Before The Holidays
- Export weekly web orders for Q4 2024 and Q4 2025, without marketplace, subscription, and manual orders.
- Pull GA4 purchases for the identical weeks as distinct transaction IDs on acquisition events. Avoid the transactions metric, which counts refunds as fine as purchases.
- Divide GA4 purchases by shop orders. A stage change, a near-zero week, or a week complete 100% is a tracking problem.
How To Explain GA4’s Pitfalls To Stakeholders
Agree on the origin of fact before the holidays. Orders and income arrive from the store; GA4 explains behavior and trends; ad platforms study what they claim.
Lead alongside the grasp rate. “GA4 recorded 41% of our web orders this quarter, downward from 81% final year” is a declaration any backing director understands.
Explain the consent gap in plain terms. In the U.K., the ICO’s guidance on consent expects a consent scheme to create it “as uncomplicated to refuse consent as it is to accept,” so several shoppers volition continually decline, and GA4 volition continually undercount. In the U.S., opt-out signals specified as California’s Global Privacy Control Act chiefly power promotion tags, during browser privacy features and ad blockers part distant at analytics.
Give promotion perspective of item that moves its figures. Consent limits, checkout updates, and tag changes frequently sit alongside developers. Put shop and GA4 income side-by-side and date all change, so a autumn in GA4 isn’t peruse as a autumn in sales.
Move Purchase Tracking Server-Side
Most GA4 setups document a acquisition in the shopper’s browser, anywhere a checkout update, a manuscript error, an ad blocker, or a refresh can endure it or figure it twice.
Instead, dispatch the acquisition from the store’s own scheme whenever the command is created, through the Measurement Protocol or a server-side tagging receptacle fed by the store, keyed on the command number. It no longer depends on the confirmation page; a refresh can’t copy it, and all event matches a shop order. Moving browser tags to a server receptacle doesn’t do this on its own, since the acquisition motionless starts in the browser. Pass the shopper’s GA4 client ID and meeting ID alongside it, captured at checkout, so GA4 can associate the command to the visit. Keep the browser tag for behavior: Google says the Measurement Protocol is meant “to augment automatic collection,” not substitute it.
Server-side tracking doesn’t alter your consent obligations, so the dependable gap stays. If you’re starting now, I’d dispatch it to a distinct GA4 asset through Q4, so nothing is counted twice, fairly than switching complete in November.
Count Orders Where They Happen
GA4 is motionless the finest liberated tool most ecommerce teams have for understanding behavior, but it isn’t a document of sales. Before you cut or shove expend this holiday season, figure your orders anywhere they happen: in the store.
More Resources:
- How To Track AI Traffic In GA4 Without Undercounting It
- Designing A Measurement Framework Before You Touch GA4
- How To Track User Journey In GA4 To Make SEO Wins More Visible
Featured Image: PeopleImages/Shutterstock
