Shopify GTM is in the theme. Is checkout covered?
Usually not by GTM itself. Shopify's checkout and Thank you pages don't load your theme code, so a GTM snippet in the theme only covers the storefront. Checkout is covered by customer events: an app pixel such as the Google and YouTube app, or a custom pixel. You need to check which of those is in place and what it sends.
Symptom
Google Tag Manager is installed in theme.liquid and storefront tags work: page views, product views, maybe add to cart. But begin_checkout, add_payment_info or purchase are missing, partial, or come from somewhere you can't see in GTM. GTM Preview shows nothing once you reach checkout.
Possible causes
- Cause A: GTM only in the theme. Theme code doesn't run on Shopify's checkout pages, so GTM never sees checkout or purchase. Shopify's help on upgrading the Thank you and Order status pages describes customer events and pixels as the way to track checkout.
- Cause B: an app pixel covers checkout, GTM covers the rest. The Google and YouTube app, or another app, sends checkout events to GA4 through its own pixel. Purchases may be fine. The risk is overlap: storefront events sent by both the app and GTM.
- Cause C: a custom pixel exists but is incomplete. It subscribes to
page_viewedbut notcheckout_completed, or it maps the order ID, value or currency wrongly. - Cause D: pixel privacy settings. Each custom pixel has customer privacy settings. Depending on the permission chosen and the visitor's consent, Shopify may not run the pixel at all.
- Cause E: sandbox side effects. Custom pixels run in a sandboxed iframe. Code copied from the theme can behave differently there, for example sending the sandbox address rather than the real page as the page location.
How to check
- List the pixels. In Shopify admin, Settings, Customer events. Note each app pixel and custom pixel, whether it is connected, and its customer privacy settings.
- Read each custom pixel. Look for
analytics.subscribecalls and note which standard events they handle:checkout_started,payment_info_submitted,checkout_completedand so on. Check whether a GTM container is loaded inside the pixel, and whether it is the same container as the theme's. - Check the Google and YouTube app. Open the app and note which GA4 property and Google Ads account it is connected to. Compare them with the IDs in GTM.
- Run a real test order. Use a test payment method or a discount code that makes the order free, in a clean browser, and accept cookies. Keep DevTools open on the Network tab with "Preserve log" ticked, filtered on
collect. Pixel requests come from the sandbox iframe but still appear there. - Confirm in GA4. Find the test order in DebugView or Realtime, then the next day in an ecommerce report filtered by transaction ID. Compare the ID, value and currency with the Shopify order.
Illustrative custom pixel subscription, simplified and not a drop-in implementation:
analytics.subscribe('checkout_completed', (event) => {
const checkout = event.data.checkout;
window.dataLayer = window.dataLayer || [];
window.dataLayer.push({ ecommerce: null });
window.dataLayer.push({
event: 'purchase',
ecommerce: {
transaction_id: checkout.order?.id,
value: checkout.totalPrice?.amount,
currency: checkout.currencyCode
}
});
});
A real implementation also maps the line items, decides how tax, shipping and discounts are treated, and handles consent.
What the result means
- No pixel sends purchase, and the app isn't connected to GA4: cause A. Purchases are probably not reaching GA4 from the browser. Confirm with the test order.
- The app pixel sends purchase: checkout is covered, even though GTM isn't involved. Check for overlap with GTM on storefront events.
- A custom pixel fires, but the values are wrong: cause C or E.
- The pixel fires only after consent: cause D, or your banner. That may be correct, but it means unconsented purchases won't appear.
Limitation. In our public-page check of 975 Shopify stores on 14 November 2026, 74 had GTM in the theme with no custom pixel detected and no app pixel referencing that container. That does not prove those stores' purchase tracking is broken: the Google and YouTube app or another route may still send purchases. A public-page check can't confirm whether purchase tracking works. Only a test order can.
How to fix it
- Choose one route for checkout events: an app pixel, or a custom pixel. Don't run both for the same destination.
- If you use a custom pixel, subscribe to the checkout events you need, map the order ID, value, currency and items explicitly, and set the page location from the event context rather than the sandbox.
- Set the pixel's customer privacy settings to match your consent approach, and test with consent accepted and declined.
- Keep the theme GTM for storefront events if you like, but remove any storefront event that the app pixel also sends.
- Re-test with a fresh order after every change, and keep a record of the order number and what you saw.
What not to do
- Don't paste the full theme GTM container into a custom pixel without reviewing it. You can duplicate every storefront tag.
- Don't rely on GTM Preview inside checkout. It may not connect to a sandboxed pixel. Use the network log and DebugView instead.
- Don't test only on the storefront and assume checkout follows.
When to request help
Our Shopify tracking service checks the storefront and checkout paths, customer events, consent and the GA4 purchase end to end. The fixed-scope £495 Shopify Purchase Tracking Fix covers one store and one agreed GA4 purchase path.
Related guides:
- Shopify purchases not showing in GA4?
- Why is the same GA4 tag loading twice?
- Why are purchase events counted twice?
Not sure what's wrong?
Send us your store address. Mikael will look at the public pages and tell you what he can see, and what he can't.
Sources and updated date
- Shopify Developer docs: About web pixels
- Shopify Developer docs: Web Pixels API standard events
- Shopify Developer docs: checkout_completed
- Shopify Help Center: Custom pixels
- Shopify Help Center: Upgrading the Thank you and Order status pages
- Google for Developers: Measure ecommerce
Last checked against official documentation: 18 November 2026.