How to Set Up GA4 Ecommerce Tracking on Shopify (2026 GTM Method)

It stopped working because Shopify deprecated the places your old code lived. Shopify made checkout.liquid unsupported for the Information, Shipping and Payment steps on 13 August 2024, then began sunsetting checkout.liquid, Additional Scripts and script tags for the Thank you and Order status pages. The Plus deadline was 28 August 2025; non-Plus stores have until 26 August 2026 (Shopify Help Center, 2025 to 2026). When that deadline passes Shopify auto-upgrades the store and removes the legacy code, so any GA4 or GTM snippet pasted into Additional Scripts simply stops firing, usually with no warning (Digital Position, 2025).

Purchase tracking is the first thing to break, because the purchase event historically fired on the Order status page. If your GA4 revenue went flat or dropped to near zero recently, this migration is the first thing to check.

The correct way is a Custom Pixel using Shopify's Customer Events (Web Pixels API). Shopify now routes all third-party tracking through this API, which runs your code in a sandboxed environment rather than directly on the page (Shopify Help Center, 2026). You write a small pixel that subscribes to Shopify's standard events and either pushes them to a GTM container loaded inside the pixel, or sends them straight to GA4 via the Measurement Protocol or gtag.

Shopify emits a consistent set of standard events you can subscribe to, including page_viewed, product_viewed, product_added_to_cart, product_removed_from_cart, cart_viewed, collection_viewed, search_submitted, checkout_started, payment_info_submitted and checkout_completed (Shopify Help Center, 2026). Your job is to translate those into GA4's ecommerce vocabulary.

Which GA4 events should map to which Shopify events?

Map them one to one against GA4's recommended ecommerce events (Google Analytics 4 Help, 2025):

• product_viewed maps to GA4 view_item
• collection_viewed maps to GA4 view_item_list
• product_added_to_cart maps to GA4 add_to_cart
• checkout_started maps to GA4 begin_checkout
• payment_info_submitted maps to GA4 add_payment_info
• checkout_completed maps to GA4 purchase

Each GA4 event needs the right parameters: currency, value, transaction_id (for purchase), and a properly structured items array with item_id, item_name, price and quantity. GA4 will not attribute revenue correctly without currency and value together, and it deduplicates purchases by transaction_id, so always send the Shopify order ID there (Simo Ahava, 2025).

Follow these steps. This assumes you already have a GTM container and a GA4 property.

1. In GTM, open Admin, then Install Google Tag Manager, and copy the head snippet. Remove the surrounding <script> and <noscript> HTML tags so you are left with raw JavaScript, because the pixel sandbox does not accept HTML (Analytics Mania, 2025).
2. In Shopify admin go to Settings, Customer Events, then Add custom pixel. Name it (for example "GTM"), set the permission and data sale settings, then paste the cleaned GTM loader code.
3. Below the loader, subscribe to Shopify's standard events and push a clean object into the dataLayer for each. For example, subscribe to analytics.subscribe("checkout_completed", ...) and build a GA4 purchase payload from the event's checkout object (order id, total price, currency, line items).
4. Repeat for product_viewed, product_added_to_cart, checkout_started and the others you want, mapping each to its GA4 event and parameters.
5. Save the pixel and click Connect so it goes live.
6. In GTM, create a GA4 Configuration (Google tag) and GA4 Event tags triggered by your custom dataLayer events, with the ecommerce parameters mapped from the dataLayer.
7. In your GA4 property, turn off the Enhanced Measurement "Page changes based on browser history events" option if you see duplicated or odd sandbox page paths, and confirm your storefront page_view is handled in one place only (Shopify Help Center, 2026).
8. Publish the GTM container and verify (see verification below).

The same pixel covers storefront pages outside checkout (home, product, collection, cart), since Customer Events fire across the whole journey. There is no longer any reason to split storefront tracking from checkout tracking the way checkout.liquid forced you to.

Verify in GA4 DebugView, not GTM Preview. This is the single most common point of confusion. Because the pixel runs in a sandbox with its own isolated dataLayer, GTM Preview mode and the GA4 Chrome debugger extension cannot see events pushed inside the pixel (Analytics Mania, 2025). Set debug_mode: true on your GA4 tags (or use your pixel's debug toggle), place a real or test order, and watch the event stream in GA4 DebugView. Confirm that purchase arrives once, with the correct transaction_id, value, currency and populated items array.

Then check, after 24 to 48 hours, that GA4's Monetisation reports show revenue within a few percent of Shopify's own order totals. We treat anything outside roughly two percent variance as a defect worth chasing, and we hold our own installs to 98 percent reconciliation against the source of truth.

These are the failure modes we see most often when a store says its GA4 revenue does not match Shopify.

• You never migrated off Additional Scripts. The old snippet stopped firing at the checkout extensibility deadline, so purchases simply vanished. This is the number one cause of a sudden revenue drop to near zero.
• Double counting from two purchase tags. A leftover GA4 tag plus a new pixel, or both a Shopify native Google channel and a custom pixel, can fire purchase twice. GA4 deduplicates by transaction_id, so if you do not send a consistent order id you will inflate revenue.
• Trusting GTM Preview. Preview mode bypasses the sandbox and shows nothing, leading people to assume tracking is broken when it is actually working, or worse, to "fix" something that was fine. Always confirm in DebugView.
• Missing currency and value. GA4 silently drops revenue attribution if either is absent, so the event shows up but reports no money.
• Thin or missing items array. Without item-level data you lose product performance reporting, even though top-line revenue may look right.
• Consent state not carrying through. Shopify's consent signal does not always survive the storefront to checkout transition, so Consent Mode can flip and quietly suppress tags (Shopify Help Center, 2026; Simo Ahava, 2025). If numbers look low rather than zero, check this.

If any of this sounds like your store, a structured GA4 tracking audit will isolate exactly where the data is leaking before you rebuild anything.

If your GA4 revenue does not match Shopify, or you are staring down a checkout extensibility deadline and are not sure what will break, that is exactly the kind of problem we fix every week. Our free conversion audit includes a tracking sanity check, so you will know whether your purchase data can be trusted before you make a single decision off it.