Preparing for Shopify’s Automated GA4 Event Updates in August 2026
Spilno Agency reports that starting August 17, 2026, Shopify's Google & YouTube app will push four additional events to Google Analytics 4 — without requiring any merchant action.
A silent GA4 pipeline change lands August 17. Two weeks later, a second deadline kills post-purchase tracking for non-Plus stores.
That automation is the problem. Stores running their own tracking layers will see duplicate events, inflated counts, and broken funnel metrics unless they audit before the date.
Four new events close the funnel gap
The app currently sends view_item, add_to_cart, and purchase. Four events fill the missing links:
- view_item_list — category and collection browsing.
- view_cart — cart page views.
- remove_from_cart — item removals.
- add_shipping_info — shipping-step completion.
Without these, the funnel from browse to checkout had structural holes. After August 17, the full sequence arrives server-side through the app. Every event will now carry a new shopify_event_name parameter — the only reliable way to separate app-sent events from those fired by your own GTM container, custom Web Pixel, or third-party tracking app.
Five events already collected gain new parameters: sku, variant_id, coupon, payment_type, and market_id. The first two enable product-level reconciliation with inventory systems. The last three open end-to-end analysis of promo codes, payment gateway conversion, and multi-country Shopify Markets performance.
Collision risk: what breaks
Deduplication does not happen automatically. Unlike the purchase event — where GA4 deduplicates via transaction_id — the four new events have no built-in merge logic. If your store fires view_cart, remove_from_cart, or view_item_list through GTM, a custom pixel, or a third-party app, those events will start arriving twice after August 17. Consequences: inflated event counts, distorted funnel rates, incorrect remarketing audience sizes.
A secondary break: the app's add_payment_info event currently sends a non-standard total parameter. It switches to the standard value field. Any GA4 custom definition, Looker Studio report, BigQuery query, or exploration relying on total will silently zero out. Collection continues. The metric just disappears.
August 26: script tags retire for non-Plus stores
Nine days later, a separate deadline hits. Script tags stop executing on the Thank You and Order Status pages for all stores not on Shopify Plus. Any JavaScript placed in Additional Scripts — Google Ads conversion tags, Meta pixel, GTM containers, COD confirmation logic — goes dark.
Shopify's documentation for non-Plus merchants directs manual upgrade to Checkout Extensibility. Unlike Plus stores, which received automatic migration with 30-day notice, no managed upgrade is promised for standard plans. Attribution stacks relying on post-purchase script injection will fail silently: reported ROAS drops while actual sales hold steady.
Binary summary
| Advantage | Risk | |
|---|---|---|
| Aug 17 — GA4 events | Full-funnel data without GTM buildout | Duplicate events if custom tracking exists |
| Aug 17 — new parameters | SKU, variant, coupon, payment, market-level analytics | total → value migration breaks legacy reports |
| Aug 26 — script tags | Cleaner checkout extensibility | Post-purchase tracking dies on non-Plus stores |
Action: Audit every event your store fires today. Tag each one with its source — GTM, Web Pixel, third-party app, or the Google & YouTube app itself. After August 17, use the shopify_event_name parameter to isolate duplicates. Before August 26, confirm nothing in Additional Scripts depends on post-purchase page access. Two deadlines, two weeks apart, two different failure modes.