Google told Shopify merchants by email that the Google & YouTube app will start sending four new events to GA4 on August 17, 2026: view_item_list, view_cart, remove_from_cart, and add_shipping_info. None of them travel the server-side path Google built for purchase data in July. They land in the browser, the same layer where a merchant’s own GTM tags may already fire cart and checkout events. The email doesn’t say how the two coexist.
What Google Told Merchants
The message merchants received reads: “Starting August 17, 2026, the Google & YouTube app will update how it shares shopping insights from your Shopify store with Google Analytics,” according to ppc.land’s report of August 8. ppc.land quotes that email as its source for the change.
A write-up from Spilno Agency, published August 5, lists the same four events and adds a further layer: five already-tracked events gain new parameters too. view_item picks up value, currency, sku, coupon, variant_id, quantity. add_to_cart adds sku, variant_id, coupon. begin_checkout adds sku and variant_id. add_payment_info adds value, payment_type, an item list, coupon, and remaps a non-standard total field to value. purchase adds coupon, sku, variant_id, market_id, affiliation.
What Changes for Shopify Stores on August 17?
Starting August 17, 2026, the Google & YouTube app adds four events to what it sends into GA4: view_item_list, view_cart, remove_from_cart, and add_shipping_info. Per ppc.land, all four run client-side, through the browser, unlike purchase, which moved to a server-to-server feed in July. Google’s message names no rule for reconciling any of them against tracking a merchant already runs.
One Event Got a Safety Net. The New Four Have None on Record.
When purchase started arriving through Google’s Data Manager API in July, it shipped with a reconciliation rule. ppc.land’s earlier report described it: “Automatic deduplication is built into the integration. GA4 matches transaction IDs from both the browser and the Shopify server, so an order should not be counted twice.”
Google’s email specifies no equivalent key for the four new events: browser events sitting next to browser events a merchant’s own pixels or GTM containers may already send. A store with no custom instrumentation on cart or checkout has nothing to double. Google’s email doesn’t address the overlap, so on our reading the store that built its own funnel tracking is the one at risk of double counting.
| Event | Fires when | Transport |
|---|---|---|
| view_item_list | Shopper views a collection page | Browser |
| view_cart | Shopper visits the cart page | Browser |
| remove_from_cart | Item deleted from the cart | Browser |
| add_shipping_info | Address entered at checkout | Browser |
The Label That Does the Sorting: shopify_event_name
From August 17, every event the app sends, new and existing, carries a parameter called shopify_event_name, holding the original Shopify event name behind the GA4 one. Spilno Agency gives collection_viewed and cart_viewed as examples. Neither report describes the parameter as a deduplication key like the purchase transaction ID, and nothing in Google’s email ties it to a merchant’s own tags. On our reading its practical use is a filter: app-sent events carry the parameter, a merchant’s own tags don’t, so a report can separate them.
Where the Missing Revenue Comes From
The server-side purchase feed exists because the browser alone was undercounting. ppc.land’s June reporting put client-side tracking’s miss rate at 10 to 20 percent of actual Shopify revenue. The same report notes that because upper-funnel events still rely on the browser, ad blockers “can still break the session ID thread”. Server-side purchase closes the revenue gap, not the attribution one: “GA4 will record the revenue. It may not correctly attribute that purchase to the originating ad campaign.” The four August 17 events sit inside that unresolved layer too.
Upstream of all this sits a separate question. The app only reports what happens once a shopper is already in the store, so campaign identity has to arrive on the inbound link. That’s what tagging campaign links with UTM parameters is for: a clean UTM on the link tells GA4 which campaign sent the shopper, whatever the app records after they land.
Consent Stays Unaddressed
Google’s email says nothing about consent for the four new events, which isn’t the same as saying none is required. Per ppc.land, on the server-to-server purchase feed Shopify’s backend has “no native mechanism to carry that consent signal unless it has been explicitly built into the integration.” Napkyn, writing on July 14 before this change was announced, flagged a separate limit: “While Consent Mode is supported in theory, the app doesn’t give you granular control over how consent is collected or passed, unlike a full CMP.” Napkyn’s advice to merchants running their own tags was blunt: “If you previously used hard-coded or GTM-based tags in Shopify (like in checkout.liquid template via custom pixels), remove them to avoid double tracking.” That advice predates the August 17 change and addresses the app’s existing events; it doesn’t speak to the new ones.
A related but unconnected date sits one day later: Content API for Shopping stops accepting programmatic product uploads on August 18, a Google Merchant Center change with its own migration path and an extended-access form, unrelated to the Shopify app’s event list.
