Troubleshooting
Shopify Custom Pixel / GTM Not Working? Trace the Event Before Rebuilding
Separate a missing Shopify event from a sandbox debugging limitation. Follow one event through Customer Events, GTM and the receiving platform.
- Published
- Reviewed
Diagnosis
- Causes, ranked by what to check first 5
First answer free, within one working day. Describe your case
Sounds familiar?
The symptom
The short version
Direct answer
Shopify documents loading GTM inside a custom pixel sandbox as an advanced configuration; adding and using custom pixels is unsupported by Shopify. Its guide also identifies a limitation in Google Tag Assistant’s Troubleshoot tag feature: it cannot detect tags inside custom pixels. Shopify recommends its Pixel Helper for checking those events. See the Shopify GTM custom pixel guide.
That limitation is a reason to change the inspection method. It is not evidence that delivery works either. The useful question is: what is the last handoff you can demonstrate for this particular event?
How I diagnose it
- Define the reproduction. Use an agreed test checkout and record which event should exist, when it should fire and which platform should receive it. Keep any test traffic out of advertising optimisation where the setup permits.
- Inspect Customer Events. Check pixel connection, the relevant consent state and Pixel Helper output. Record whether the source event appears and whether an exception follows it.
- Inspect the mapping inside the pixel. Follow that event into the sandbox’s dataLayer. Compare the source event name with the event the GTM trigger expects. Do not assume a storefront dataLayer inspection is the same evidence.
- Inspect the tag and request. Check the published container and the intended tag’s inputs. Find the outgoing request and verify the destination identifier, event name and required fields. Remove customer details from any shared capture.
- Inspect the receiver. Use the destination’s available event tools or import diagnostics, then check its reporting rules. Record a rejection or an unresolved result explicitly; an outgoing request alone is not acceptance.
For checkout_completed, Shopify documents that the event can occur on the first post-purchase upsell page instead of the Thank you page. If the page that should emit it never loads, the event is absent. That makes the actual checkout journey part of the reproduction. See the event reference.
What the evidence means
| Last confirmed observation | Next check | Avoid changing yet |
|---|---|---|
| Order exists; source event unconfirmed | Checkout journey, consent and Pixel Helper | Destination reporting settings |
| Source event exists; mapped event absent | Pixel error and dataLayer mapping | Attribution model |
| Mapped event exists; no request | Trigger, tag inputs and container version | Entire tracking architecture |
| Request exists; destination event absent | Destination ID and receiver diagnostics | Adding a second purchase sender |
| Destination event exists; report differs | Reporting delay, filters and attribution | Working event code |
For example, if a source event and mapped event are recorded but no request is observed, I investigate the tag handoff before proposing server infrastructure. This is a reasoning example, not a test result from a store.
Can you fix this yourself?
If you can isolate a single event-name mismatch and verify the destination after changing it, the repair may be small. Save the previous configuration and make one change at a time. If several apps and custom pixels send the same purchase, first agree which sender owns each destination.
This page is a documented diagnostic sequence reviewed on 26 October 2026. It does not present a paste-ready pixel, a live Shopify experiment or a claim that the same configuration works on every store.
Where to look
Causes, ranked by what to check first
Causes, ranked by what to check first5 causes
-
The inspection method cannot see the sandbox
Start here when only Preview looks wrong and destination events still arrive. -
The expected source event never occurred
A completed order in the admin is not proof that the browser reached the page that emits the checkout event. -
The pixel did not run for this consent state, or its code failed
Record the state and the first error before editing triggers. -
The event reached the pixel but not the intended GTM tag
Check the event name, mapped fields, container version and trigger conditions. -
The request went to the wrong destination or was rejected
Check the receiving property, dataset or conversion action and its diagnostics.
This is a troubleshooting order, not a measured ranking of how often each fault occurs.
One clear problem, fixed.
I fix the broken event mapping, GTM trigger or delivery step in your existing Shopify tracking setup.
I trace an agreed test order from the Shopify event to the receiving platform and document the result.
$350 · 3 working days after access
Urgent, within 24 hours: +25%.
When several systems disagree, or a cheaper fix already failed.
If the fault spans the checkout, browser tags and server delivery, I scope the connected repair separately and agree the events, destinations and acceptance checks before work starts.
I prove the cause in your own data, rebuild the broken tracking, and add a daily check so it does not silently break again.
From $1,500
Questions
Questions this symptom raises
Does an empty Tag Assistant view mean GTM is broken?
No. Shopify documents that Tag Assistant's Troubleshoot tag feature does not detect tags inside custom pixels. Check Customer Events with Shopify Pixel Helper and follow the actual request before concluding that delivery failed.
Should I paste a second GTM container into the theme?
First inventory the senders already installed. Adding another purchase sender can create duplicates while leaving the original fault unresolved.
Is this a tested replacement pixel I can paste into my store?
No. This is a diagnostic sequence based on Shopify documentation, reviewed on 26 October 2026. It does not include a replacement script or claim a live test on your configuration.
Does the $350 fix include moving the whole store to server-side GTM?
It covers one agreed fault in the existing setup. A new architecture or a connected rebuild is scoped separately, from $1,500. Discussing the task is free.
Read more, or check a neighbouring symptom.
All symptoms- Service Google Tag Manager cleanup & repair
- Article GA4 on Shopify: the Google & YouTube App vs a Custom Web Pixel
- Article Fix the GA4 Purchase Event on Shopify (Step by Step)
- Troubleshooting Drop in GA4 Users Following Consent Mode Setup on Shopify
- Troubleshooting Shopify Checkout Tracking Broken: Diagnosis
Hi, I’m Daniil.
I work with you from defining the problem to implementation and handover. You talk to the person who does the work. I work in English and Russian; written correspondence in Spanish with translation support.
Tried it and still stuck?
Describe what's wrongThe first answer is free, within one working day. Or write directly: next@taskfordaniel.com