Guide 24 · Debugging · GA4 + Tag Manager
The tag is not firing: check the trigger before you rebuild the tag
A tag that never fires is usually a trigger that never matches. Read the trigger's conditions against the event, and Preview will name the one that failed.
After the steps below, the trigger condition that failed is named, the trigger is fixed to match the real event, and the tag fires on the next test.
Download the check: the debugging check (JSON) (MD5 0947401041fbce05d4bbb87c8afa4ece, 444 bytes). It lists the checkpoints from this guide and the worked check, with the figures recomputed. The file was built for this guide and validated structurally — it was not exported from a live container or a live property.
What you need
- Tag Assistant Preview, connected. The debug view shows the tag under Tags Not Fired, with the reason.
- The tag, open in Tag Manager. Its trigger, listed under Triggering.
- The trigger, open on its conditions. The type and every condition, read exactly as saved.
- The event, done once in Preview. The action the trigger should match, so Preview can judge it.
The trace
The worked check: the figures below were recomputed before publication, and the note under the table shows the working.
| Check | Figure |
|---|---|
| Tags in the container | 7 |
| Tags that fired on the test event | 6 |
| Tags that did not fire | 1 |
| Trigger conditions on the tag that did not fire | 3 |
| Conditions that matched | 2 |
| Conditions that did not match | 1 |
Seven tags were in the container and 6 fired on the test event, so 7 minus 6 is 1 tag that did not fire. That tag's trigger had 3 conditions: 2 matched and 1 did not, so 3 minus 2 is 1 failed condition — a page path that did not match. Fixing that one condition fired the tag.
- Find the tag under Tags Not Fired. Start Preview, connect your site, and do the action. In the debug view, select the event and look under Tags Not Fired. If the tag is there, click it: Preview shows which trigger condition did not match. That condition is the whole diagnosis.
- Open the trigger and read every condition. In Tag Manager, open the tag's trigger. Read the trigger type first — Page View, Click, Custom Event, Form Submission — then each condition. A trigger is a list of conditions, and all of them must be true for the tag to fire.
- Compare each condition with the real event. For the failed condition, compare what the trigger waits for with what actually happened. A Click trigger waiting for Click Classes to contain buy-now never fires on a button whose class is buy_now. A Page View trigger waiting for Page Path to equal /checkout never fires on /checkout?step=2 if the match is exact.
- Check the trigger type itself. A Custom Event trigger waiting for purchase never fires on a page view, and a Form Submission trigger never fires on a form that submits without reloading the page. If the type is wrong, no condition fix will help — change the type to the event that actually happens.
- Fix one condition, then repeat the event. Change the condition Preview named, save, and repeat the same action in the same Preview session. The tag should move to Tags Fired. If a different condition now fails, fix that one too — work through them one at a time, not all at once.
Dead ends
DEAD END — REBUILDING A TAG WITH A GOOD TRIGGER. A tag under Tags Not Fired is not a broken tag; the trigger did not match. Deleting the tag and building it again with the same trigger produces the same result, and the afternoon is gone.
DEAD END — A CONDITION THAT MATCHES NOTHING BY DESIGN. A trigger waiting for a page path that no longer exists, or a click text that changed in the last redesign, can never match. If the condition names a page or a button that is gone, the trigger is out of date, not misconfigured.
DEAD END — TWO TRIGGERS, ONE TAG, ONE WRONG. A tag with two firing triggers fires when either matches, but some builders read only the first. If the first trigger can never match and the second can, the tag still fires — and the confusion comes from reading half the list. Read every trigger on the tag.
End state
The failed condition named, fixed, and proven: the tag moves from Tags Not Fired to Tags Fired on the same event in the same Preview session. The tag was never broken — its trigger was waiting for an event that never happened.
Sources
- Tag Manager Help — Preview and debug containers — The debug interface showing what triggered, or did not trigger, a tag's firing status for each event
- Analytics Help — Monitor events in DebugView — DebugView as the next check once the tag fires, to confirm GA4 received the event
Checked 11 November 2026. The click paths above are the ones in Google's help pages, opened 11 November 2026. What was run: the trigger counts, recomputed — 7 tags, 6 fired and 1 not fired, with 3 trigger conditions of which 2 matched and 1 failed, so 3 minus 2 is 1 failed condition. No step in this guide was run inside a live Analytics property or a live Tag Manager container, because both need a Google sign-in and this site does not sign in as anyone. Google moves menu items without warning; if a path on this page no longer matches, the linked help page is the current map.