Google emailed Shopify merchants during the first week of August 2026 to say that from 17 August 2026 the Shopify to GA4 integration will start sending four additional events: view_item_list, remove_from_cart, view_cart and add_shipping_info. Edward Upton, CEO at Littledata, published the notification on LinkedIn on 6 August 2026 and said only the purchase event travels server-side, which PPC Land reported on 8 August 2026.
That leaves nine days between the notification and the switch-on for any merchant running custom Shopify tagging to check whether the app is about to duplicate events they already collect.
Four GA4 events start flowing from Shopify on 17 August 2026
Google's email lists each new event against the shopper action that triggers it. These are the four, exactly as the notification describes them.
| GA4 event | Shopper action that triggers it, per Google's notification |
|---|---|
| view_item_list | Viewing a collection |
| remove_from_cart | Removing items from the cart |
| view_cart | Looking at the shopping cart |
| add_shipping_info | Providing shipping or address details at checkout |
All four are part of the standard GA4 ecommerce specification, which is why so many stores already fire them through a hand-built container.
Only the purchase event is server-side, according to Littledata's Edward Upton
Upton wrote on 6 August 2026: "Only the purchase is server-side. Every event in that list is still browser-based, so ad blockers and consent banners break the session thread before the order arrives." The distinction decides how much of the data survives. A purchase recorded server-side lands in GA4 regardless of what the browser did, while the four new events depend on the shopper's browser executing a tag, which ad blockers and unconsented sessions prevent. The result is revenue GA4 can count sitting on top of a journey it may not have recorded.
The cart and collection events have no deduplication protection
PPC Land's write-up lists deduplication as the first limitation: only purchases get transaction ID matching, and the cart and collection events carry no equivalent identifier. Any store that added view_item_list, remove_from_cart, view_cart or add_shipping_info through its own Google Tag Manager container is therefore looking at the same interaction being recorded twice from 17 August, once by the tag it configured and once by the app. Duplicated add-to-cart and cart-view data corrupts funnel reporting, and it also corrupts every GA4 audience or conversion built on top of those events.
The notification leaves four things unaddressed
Beyond transport and deduplication, PPC Land lists the gaps the email does not cover.
- No market_id mapping, so Shopify Markets cannot be split into separate regional GA4 properties.
- No support for subscriptions or post-purchase upsells.
- No merchant control over what is included in the server-side orders.
- No stated opt-in, so the change is scheduled to apply without merchant action.
The absence of a stated opt-in is the operationally important one. A merchant who does nothing still gets the four events.
What to check before 17 August 2026
The check is small and specific: open the GTM container and list every ecommerce tag that fires view_item_list, remove_from_cart, view_cart or add_shipping_info, then decide which source to keep. Keeping the custom tag makes sense for stores that enrich those events with parameters the app will not send. Keeping the app version makes sense for stores whose custom tags were only ever filling the gap. What does not make sense is keeping both and finding out in September why cart metrics doubled. A clean GA4 setup is worth more here than an exhaustive one.
What this means for Thai marketers
The source does not state a country-by-country rollout, so there is no basis for saying whether Thai stores switch on at a different time or at all on 17 August 2026. What is safe to say is that the exposure follows the tagging, not the market: a Bangkok store running the Google and YouTube app with its own GTM ecommerce tags on top has the same duplication risk as any other. Thai ecommerce teams that inherited a container from a previous developer are the ones most likely to be double-firing without knowing it, because nobody in the current team wrote those tags. For stores where the same team also handles organic performance, this is a reasonable moment to look at the whole Shopify measurement setup rather than only the four events, since collection page tracking sits directly on top of collection page traffic.
Frequently asked questions about the Shopify GA4 change
Do I have to do anything to get the new events?
No, the notification lists no opt-in requirement and no configuration step. Google's email says the Google and YouTube app will update how it shares shopping insights from 17 August 2026, and merchants who take no action still receive the four events.
Will my existing GTM tags be turned off automatically?
The source does not say that they will, and nothing in the notification describes the app switching off a merchant's own tags. That is precisely why the duplication risk exists: two independent collection paths for the same event, with no transaction ID to reconcile them.
Is this live in Thailand?
The source does not state any regional staging. PPC Land reports a single date, 17 August 2026, with no country list and no note about phased rollout, so a Thai store should plan for the same date as everyone else unless Google says otherwise.
Are the four new events server-side like the purchase event?
No. Upton stated on 6 August 2026 that only the purchase is server-side and every event in the new list is still browser-based, which means ad blockers and consent banners can prevent them from being recorded at all.
What happens to my historical funnel data?
The source does not address historical data. Practically, a funnel report spanning 17 August will mix two collection regimes, so any before-and-after comparison of cart or collection metrics needs the date break noted rather than read as a trend.
Where to start
Nine days is enough time to audit one container. Open the GTM workspace, search for the four event names, and write down which ones already fire. If any of them do, decide now which source wins rather than letting September's reporting decide for you. Anyone who wants help reading a Shopify container before the date can get in touch.
