Will Shopify Google Analytics Update Fix Tracking Accuracy?
Australian ecommerce brands lose confidence in their own numbers more often than most executives would like to admit. Forrester’s 2024 Marketing Survey found that most B2B marketing leaders share this doubt.
Sixty-four percent say they don’t trust their own company’s marketing measurement when making decisions. Shopify merchants who rely on the Google and YouTube app know this problem firsthand.
Native connectors between ecommerce platforms and reporting tools rarely produce matching figures.
On 17 August 2026, Google is rolling out a Shopify Google Analytics update that adds new ecommerce events and a clearer way to trace where each data point originates. This guide sets out what changes, and whether it actually closes the reporting gap.
What the Shopify Google Analytics Update Changes
The Shopify Google Analytics update applies to any merchant using the Google and YouTube app to connect their store to a Google Analytics 4 property.
- The app listens for Shopify’s own backend events, like product_viewed or checkout_completed, then maps each one to the standard event name Google Analytics expects, such as view_item or purchase.
- From 17 August 2026, this mapping expands to cover more of the customer journey and includes new fields on events the app already sends.
- Merchants don’t need to change anything to receive the new events and fields, since the update applies automatically to any store already connected through the app.
- Merchants with customised event or destination mappings should double-check those settings before the rollout, as new default events could interact with existing customisations in ways worth catching early.
New Google Analytics Events for Shopify Stores
Four new events join the set the Google and YouTube app already sends, each covering a stage of the shopper journey Google Analytics previously could not see through this connector.
| New Event | What It Tracks |
| view_item_list | Fires when a shopper views a collection page. |
| remove_from_cart | Fires when a shopper removes an item from their cart. |
| view_cart | Fires when a shopper opens their shopping cart. |
| add_shipping_info | Fires when a shopper enters shipping or address details during checkout. |
Existing Ecommerce Events Now Include More Data
Alongside the four new events, five events the app already sends are gaining extra parameters, adding detail that previously required custom tracking to capture.
| Event | New Parameters Added |
| view_item | Value, currency, SKU, coupon, variant ID, and quantity. |
| add_to_cart | SKU, variant ID, and coupon. |
| begin_checkout | SKU and variant ID for every item in the cart. |
| add_payment_info | Value, payment type, item-level data, and coupon. The previous non-standard total field is now remapped to the standard value field. |
| purchase | Coupon, SKU, variant ID, market ID for localisation, and affiliation data showing which hostname generated the sale. |
Why Richer Ecommerce Data Matters
This level of detail matters most for merchants selling across multiple markets or managing complex product catalogues. It lets Google Analytics segment revenue by variant, promotion, or storefront without merchants having to build custom event tracking themselves.
Agencies managing several Shopify accounts should find fewer gaps between what a client’s Google Analytics property shows and what their own product catalogue can explain.
Understanding the “shopify_event_name” Parameter
Every event the Google and YouTube app sends as part of this update will carry a new parameter called shopify_event_name. Its value shows the original Shopify event that triggered it, for example collection_viewed or cart_viewed.
Google documents the full list in its developer reference for the app’s event parameters. In practice, this gives analysts a direct line back to the source event inside Shopify, rather than having to infer it from the Google Analytics event name alone.
For agencies managing several Shopify clients, this parameter also helps confirm the source of incoming data.
It flags whether an event actually came from the Google and YouTube app, rather than a separate custom tag or a Google Tag Manager container running alongside it.
How the Google Analytics Update Affects Shopify Tracking Accuracy
Extra detail in the data doesn’t automatically mean more accurate reporting, and the numbers bear that out.
The Scale of the Gap
The existing Google and YouTube app connector has a well-earned reputation for inaccuracy. It is one of the main reasons Tell No Lies recommends server-side tracking to Shopify clients in the first place.
The gap between what the app reports in Google Analytics and what Shopify’s own backend records can be considerable. One analysis of live ecommerce deployments found Google Analytics capturing barely two-thirds of revenue. Ad blockers explain part of that shortfall.
Why Richer Data Doesn’t Close the Gap
Richer event data does not change how that data gets collected. The update simply adds detail to events the app already fires through the customer’s browser, so it remains exposed to the same causes of data loss:
- Ad blockers
- Cookie consent declines
- Script failures that stop the tag from firing altogether
Google itself acknowledges that Google Analytics and Shopify’s backend will never report matching revenue figures. A few factors drive that mismatch:
- Differences in attribution windows
- Timezone handling
- Refund processing
Tell No Lies’ Assessment
Tell No Lies is cautiously optimistic that these additions will improve the quality of the data that does get through. Extra parameters on the purchase and checkout events, for example, should reduce the amount of manual reconciliation required for basic reporting.
We intend to run structured testing once the update rolls out, comparing event volumes and revenue totals against Shopify’s backend.
Only then will we draw conclusions on whether it meaningfully narrows the gap Shopify tracking accuracy has long struggled with.
Do Shopify Merchants Still Need Server-Side Tracking
Server-side tracking sends conversion data straight from a server to Google Analytics or Google Ads, bypassing the shopper’s browser altogether. Because the transaction never touches client-side JavaScript, ad blockers, browser privacy settings, and consent banners can’t interfere.
Our guide to privacy regulations and browser restrictions covers why browser-based signals have grown less reliable.
One thing has changed, though not through this update. In July 2026, Google switched on a server-to-server connection for the same app, sending the checkout_completed event straight from Shopify’s servers to Google Analytics through the Data Manager API. Purchases that a blocked or failed browser tag would previously have lost now arrive regardless.
That connection covers the purchase event and nothing else. Every event in this update, including all four new ones, still travels through the same browser-based tag, so a shopper who blocks it stays invisible for everything up to the moment they buy.
Merchants running paid media, especially alongside Meta or TikTok, should still invest in server-side tracking for Shopify.
This update improves the richness of the data. Server-side architecture still does the work of closing the tracking gap.
Reducing Google Analytics Data Discrepancies After the Update
Merchants and agencies can take several practical steps to manage Google Analytics data discrepancies once the update goes live. Start by comparing GA4 event volumes against Shopify’s own admin reports for the same date range.
Do this day by day rather than as a weekly aggregate, since a single bad day can hide inside an otherwise reasonable average.
Use the shopify_event_name parameter to separate data collected before the update from data collected after it. This makes it easier to spot whether certain event types are more prone to shortfalls than others.
It is also worth revisiting how attribution, refunds, and multi-touch reporting are configured in GA4. Discrepancies caused by these settings will persist no matter how much event detail the app now sends.
Our guide to marketing attribution covers how attribution model choices affect reported revenue.
Filtering “shopify_event_name“ in GA4 Reports
This parameter can be registered in GA4, which then makes it available inside Explore reports for filtering and comparison.
Isolating Specific Events
Analysts can build a report that isolates events carrying a specific shopify_event_name value, such as cart_viewed. This makes it possible to track that behaviour over time, independent of other cart-related events.
Excluding Events You Don’t Need
The same parameter also supports exclusion. Merchants who want to keep their GA4 property free of certain new event types, perhaps because a separate tool already tracks that behaviour, have another option.
They can create a data filter based on shopify_event_name instead of disabling the app’s data stream altogether. This keeps the rest of the update’s benefits intact while avoiding duplicate or unwanted event data.
What This Means for Google Analytics 360 Billing
The additional events introduced by this update will increase the total event volume flowing into affected GA4 properties.
For most merchants on the free tier of Google Analytics, this carries no direct cost. Google Analytics 360 customers are billed in part on event volume, though. A rise in events captured per session could translate into a higher monthly bill.
The size of that increase depends on how active a given store’s customer journey is and how many of the new events fire per session. 360 customers should monitor billing closely in the months following the rollout, rather than assume costs will stay flat.
How to Prepare for Shopify Google Analytics Update
A few steps before 17 August 2026 will make the transition smoother:
- Review the current event and destination configuration inside the Google and YouTube app, to confirm existing conversion actions still map to the correct events once new ones appear.
- Update GA4 dashboards and reports to accommodate the new parameters. This matters most for custom reports that currently rely on the old add_payment_info total field, since the update remaps it to value.
- Register shopify_event_name as a custom dimension ahead of time, so filtering is available from day one rather than only for data collected after the dimension is created.
- Once the update is live, monitor event volumes for the first few weeks. A sudden spike or drop in a specific event type usually flags a configuration issue, and it’s easier to fix early than after months of skewed reporting.
Prepare Your Shopify Analytics for the Update
The Shopify Google Analytics update adds meaningful detail to the data Australian merchants receive through the Google and YouTube app. The new shopify_event_name parameter also gives analysts a genuinely useful tool for tracing and filtering that data.
What it doesn’t do is fix the structural reasons Google Analytics and Shopify’s backend rarely agree on revenue. Merchants who already rely on server-side tracking to close that gap should keep doing so.
Those who haven’t made the move yet should see this update as a reminder of why that shortfall exists.
Tell No Lies helps Australian Shopify merchants and agencies audit their tracking setup and diagnose the source of reporting discrepancies.
We also build the server-side architecture needed for tracking they can actually trust.
Contact Tell No Lies today to prepare your Shopify tracking setup for this update.