Around October 31, 2026, Shopify merchants started noticing that Shopify Analytics reported far more Google Ads traffic and far less Organic Google traffic than it did a week earlier, while Google Analytics 4 (GA4) barely moved. The total Google traffic in their reports stayed roughly the same. What changed was how Shopify classifies a block of Google traffic, and the change affects attributed sales as well as sessions. This guide walks through what merchants report, what Shopify’s own documentation says about the October updates, why Shopify and GA4 never match exactly, and how to check the split against a second source before you change anything.
What merchants started seeing around October 31
A fresh thread on r/shopify (November 9, 2026) reported the change in detail. The store owner shared a before and after comparison of daily sessions, October 24 to 30 versus October 31 to November 7:
- Shopify Analytics, Google Ads: 37 daily sessions before, 101 after.
- Shopify Analytics, Organic Google: 101 daily sessions before, 46 after.
- GA4, Google Ads: 94 before, 97 after (effectively flat).
- GA4, Organic Google: 55 before, 51 after (effectively flat).
In other words, Shopify Analytics flipped roughly 55 daily sessions from organic to paid, and GA4 did not move. The same store owner then checked historical orders: in a sample of 74 orders that GA4 identifies as Google Ads traffic, Shopify now labels 39 as organic, and all 39 carried identifiable Google Ads campaign IDs in the original GA4 data. So the same report change cuts both ways: a store’s own campaign data says paid, and a platform report says organic. The thread is a real, recent report of the behavior, not a statement from Shopify itself.
Not a traffic jump: the total stayed flat
The first thing to check is the sum, not the split. Before the change this store’s Shopify Analytics showed 37 Google Ads sessions plus 101 Organic Google sessions, 138 Google sessions a day. After the change it showed 101 plus 46, 147 Google sessions a day. The total barely moved. When one platform’s paid and organic rows shift against each other and the combined total stays stable, while a second platform shows no change at all, the most likely explanation is that traffic did not change and the platform changed how it groups the traffic.
That matters because the natural reaction to a report like this is to conclude that organic collapsed or that ads doubled. On the evidence in the thread, neither happened.
What Shopify’s documentation says about the October updates
Shopify’s own help center describes two related updates in this window, and both are worth knowing before you reconcile numbers:
- In September 2026 the Performance by marketing channel report was rebuilt to include all traffic that reaches your store, grouped by marketing channel, instead of only traffic attributed to a marketing activity. Shopify notes that sessions, sales and orders in that report can now be higher than before, and that it now includes rows it did not include before, such as organic and referring traffic. Performance by marketing campaign replaced Performance by UTM campaign, and Performance by marketing channel now covers what Performance by referring channel used to provide.
- Shopify also documents that referring channel, referring medium and traffic type use updated values from October 18, 2026. Visits without an identified marketing source are listed under their referring channel instead, so those rows can change across that date. Identified ad products keep the same marketing channel classification for dates before and after October 18. The accounting for discrepancies guide explains how to compare a marketing report to a copy from before the change.
Merchants report seeing the visible Google Ads versus Organic re-bucketing around October 31, and the exact date a store sees it can vary, so treat the reported date as late October 2026 until you confirm what your own store shows. Shopify Support told the merchant in the thread that the updated marketing channel classification can affect orders and attributed sales, not just sessions, and that historical reports may reflect updated classifications depending on the available advertising information.
The likely cause: static UTM strings versus Google click IDs
The most likely explanation, proposed by one commenter and matching the session totals, is a change in how Shopify reads Google’s URL parameters. Google’s Google and YouTube app appends strings like utm_medium=product_sync and utm_campaign=sag_organic to Merchant Center product feed URLs. When a paid click lands on a product from a Shopping or Performance Max campaign, Google auto-tagging also appends a gclid click identifier to the same URL. GA4 prioritizes the gclid identifier, which is why it has been classifying those sessions as paid Google Ads all along. Under this theory, Shopify previously evaluated the literal UTM strings and bucketed those same sessions as Organic Google, and an updated classifier now groups them as Google Ads.
This explanation is not confirmed. It was proposed by one commenter, the original poster called it plausible but asked for documentation and did not receive any, and another commenter pointed out that the sag_organic campaign name alone does not prove a visit came from a free listing. The store’s own historical orders also cut against it: Shopify still labels 39 Google Ads orders as organic, and its customer journey data shows SEO visits with no UTM parameters for the same orders. The theory fits the session totals, it does not explain the historical orders, and Shopify has not confirmed it. Treat it accordingly and confirm against your own order-level data, as described below.
Why Shopify and GA4 never match exactly, even on a normal day
Part of the confusion is that Shopify Analytics and GA4 are different products with different rules, and their numbers disagree even when nothing changed:
- Attribution models. Shopify Analytics attributes conversions by first or last interaction, with last non-direct click as the default; GA4 uses its own channel grouping and modeling. The same order can be credited to a different channel in each tool.
- Sessions and users. Shopify counts cookie-based sessions with its own rules; GA4 builds sessions and users on its event model. Definitions differ, so session totals differ.
- Checkout events. GA4 depends on purchase events firing from your store. When a customer pays through an off-site payment method such as a bank link and never returns to the thank-you page, GA4 can miss the sale entirely while Shopify has the order. This is a recurring pattern for European stores, and it makes GA4 look worse than it is and undercounts the ads that brought the sale.
- Realtime views. GA4 Realtime is a 30-minute rolling view, so it is the wrong tool for confirming a change like this. Verify with daily reports first, using the same date range in both tools.
None of this means one tool is wrong. It means each number answers a different question, and the answer to what changed on October 31 should come from data you can check, not from whichever split the platform shows today.
How to reconcile the split
If your own reports show the same pattern, work through these steps before drawing any conclusion:
- Compare totals first. Add the paid and organic rows for the same platform and period. If the combined total is stable and a second platform is stable, the traffic did not change.
- Use the same date range and the same attribution model in both tools. A report that spans September 21 to 23, 2026 can also reflect Shopify’s session measurement update, and one that spans late September can reflect both that and the marketing report rebuild.
- Export your current reports now. Save a fixed copy of the channel, campaign and order reports for the before and after periods, with the exact date ranges and model used. You will need them if the labels change again.
- Check a sample of orders at the order level. Match order IDs against GA4 purchase events, the session source and the Google Ads campaign association. A campaign association does not by itself mean that campaign deserves the whole sale, but it tells you which rows Shopify and GA4 are classifying differently.
- Ask Shopify support to confirm, in writing, what the update did to your store and whether historical rows change when you rerun a report. The distinction between newly recorded sessions and reclassified historical rows decides whether your old revenue reports are still comparable.
- Do not rewrite historical ROAS or change budgets on this evidence yet. Reconcile first, then relabel the reporting if the data supports it.
An independent second source
The reason this thread stayed confusing is that every commenter compared Shopify Analytics with GA4, and both of those are platform reports with their own classification rules. A useful habit is to keep one independent record of arrivals and campaigns that neither platform controls the labels of.
Hitsteps is web analytics that runs on any website, including Shopify (via one tracking snippet or the Shopify app), and it keeps its own copy of the arrival data: traffic sources, referrers, UTM campaigns with first-touch and latest-touch attribution, landing pages, and the visitor journeys that followed. That means when Shopify re-buckets a channel name, you still have your own record of which links and campaigns the visits actually came from, recorded at the time they arrived. For stores where Commerce is enabled (it is opening gradually), Hitsteps adds a separate verified orders lane (Shopify, WooCommerce or your own store server) that records orders, status changes, items, discounts and refunds as financial proof, kept apart from browser behavior. The guide chapter on ecommerce and Shopify and the traffic sources and campaigns chapter document exactly how that works.
To see the relevant concepts in the product: UTM campaign tracking shows first-touch UTM and latest UTM touch for each visitor with the same tagging fields Shopify uses; traffic source analytics organizes referral, search, campaign, AI referral and direct or unknown signals and connects each source to landing pages. If you use GA4 today, our comparison page lays out the differences honestly. And if you have ever wondered why two analytics tools show different numbers, an older post here covers that exact question.
None of this fixes Shopify’s report, and Hitsteps does not claim consent exemptions. It just gives you an independent copy of the data, so a re-bucketing in a platform report is something you can check instead of something you have to trust.
Bottom line
What merchants reported around late October 2026 is a reclassification of Google traffic in Shopify Analytics, most visible on Google Ads versus Organic Google rows, with the combined totals and GA4 staying roughly flat. Shopify’s own documentation describes the report rebuild in September 2026 and channel and referring values updated from October 18, 2026. Before you react: compare totals, match a sample of orders between Shopify and GA4, export fixed copies of the reports, and confirm with Shopify support what reached your store. Keep one independent source of arrival data so the next label change does not cost you a weekend.
One next step
If you want to see what a visitor session looks like when the arrival data and the behavior stay together, the Hitsteps live demo plays back a simulated shopper visit as a session replay with a heatmap preview. It runs on example data from a made-up shop, needs no signup, and nothing is recorded while you watch.
