Why Isn't My GTM Tag Firing? A 6-Step Debugging Checklist

A tag that won't fire is the most common Google Tag Manager problem, and almost always one of a handful of causes. Work this checklist top to bottom in GTM Preview (Tag Assistant) and you'll find it fast. Each step tells you exactly what to look at and what "good" looks like.

1. Are you testing the right version?

The most common "it works in Preview but not live" cause: the change was never published. Preview runs your latest workspace draft; the live site runs the last published version.

• If it works in Preview but not in production, click Submit → Publish.
• Confirm the right container ID (GTM-XXXXXXX) is installed on the page.
• Hard-refresh (the old container can be cached) and re-check.

2. Did the trigger actually match?

Select the event in the timeline and open the Tags tab. Your tag is either under "Tags Fired" or "Tags Not Fired." If it's not fired, click it to see which trigger condition failed, GTM shows the condition and the actual value side by side.

• Wrong event. A Custom Event trigger for add_to_cart won't fire if your site pushes addToCart. Names are case- and spelling-sensitive.
• Condition mismatch. "Page Path equals /thank-you" fails on /thank-you/ or /thank-you?id=1. Use contains or a regex when appropriate.
• Click/Form trigger never sees the interaction. JavaScript-driven buttons and embedded forms often don't emit native events, you may need a dataLayer push instead.

3. Is the data there yet? (timing & race conditions)

A tag can fire on the right event but send nothing because the value it needs didn't exist yet. Open the Variables tab for that event and check your variable has a value, not undefined.

// BAD: tag fires on Page View, but user_id is pushed a moment later.
dataLayer.push({ event: "page_view" });
setTimeout(() => dataLayer.push({ user_id: "abc" }), 500);  // too late

// GOOD: push context before the tag that needs it.
dataLayer.push({ user_id: "abc" });
dataLayer.push({ event: "page_view" });

4. Is a blocking trigger (exception) stopping it?

Exceptions silently win. If your tag has a blocking trigger and its condition is true, the tag will not fire even when its firing trigger matches. In the not-fired tag detail, check for a blocking trigger and whether it evaluated true.

• A site-wide "don't fire on staging" exception that's matching production.
• A "exclude internal traffic" rule catching more than intended.

5. Is consent holding the tag?

With Consent Mode and consent checks, a tag can be intentionally held until the user grants permission. That's correct behavior, but it looks identical to a broken tag if you don't know to check.

• In the tag detail, look for a consent status showing the tag is waiting.
• Accept the consent banner in Preview and confirm the tag then fires.
• Verify your CMP actually pushes the consent update, if it never does, tags stay held.

6. The tag fired, but did the hit leave the browser?

"Tag fired" means GTM ran the tag, not that the request succeeded. For the full truth, open the browser's Network tab and filter for the vendor endpoint:

Network tab filter:  collect
GA4 success looks like:  POST https://www.google-analytics.com/g/collect?v=2&tid=G-XXXX&en=purchase ...  → 200/204

• No request at all? An ad/tracking blocker may be stopping it, or the page navigated before it sent (see form tracking).
• Request present but wrong params? Back to step 3, your variables are empty or mismapped.

The 60-second triage

1. Published? Live ≠ Preview. Publish and hard-refresh.
2. Trigger matched? Check Tags Not Fired → which condition failed.
3. Variable populated? Variables tab for that event, not undefined.
4. Exception blocking? Look for a true blocking trigger.
5. Consent holding? Accept the banner, re-test.
6. Hit sent? Network tab → vendor endpoint → 200/204.