Why does my GTM form tag show nothing in Tag Assistant even though I think it fired?

Tag Assistant's live Preview connection runs inside the page itself. A form with Wait for Tags enabled that does a full-page reload on submit destroys that connection the instant the browser navigates, and the reconnect on the new page load doesn't always recover the event that triggered the reload. The tag can execute successfully and send its hit before the connection drops — Tag Assistant's live panel just never gets to show it.

If Tag Assistant shows nothing, how do I know whether the tag actually fired?

Pull the raw Tag Assistant JSON export (not the live panel) and check the tag's execute status and resolved parameter values for the message tied to the form submission event. A tag can show execute_succeeded with fully resolved, correct values in the export even when the live panel showed nothing. Cross-check against GA4 DebugView, filtered to your tag's actual configured event name, as the final source of truth.

Should I turn off Wait for Tags if Tag Assistant isn't showing the tag firing?

Not automatically. First confirm via a JSON export and GA4 DebugView whether the tag is genuinely not firing or just not visible in the live panel. If the export and DebugView both confirm the hit never arrives, then test with Wait for Tags off to isolate whether it's the specific cause before deciding to leave it off.

GTM Form Tag Not Showing in Tag Assistant? It May Still Be Firing (2026)

A GTM form submission tag with Wait for Tags enabled that shows nothing in Tag Assistant’s live Tags panel isn’t necessarily broken — it can execute successfully, send a correct hit to GA4, and still never appear in that panel. The cause is a full-page reload breaking Tag Assistant’s live connection at the exact moment the tag fires. Before assuming the tag failed, check the raw JSON export and GA4 DebugView, which both read from the underlying event stream rather than Tag Assistant’s live UI connection.

What You’re Seeing

Form Submits, Tag Assistant’s Live Panel Shows Nothing
Tag Assistant Disconnects and Reconnects Right at Submission

The Fix

Check the Raw JSON Export, Not the Live Panel
Confirm in GA4 DebugView by the Tag’s Real Event Name

Form Submits, Tag Assistant’s Live Panel Shows Nothing

What’s Happening: A native HTML form (full-page GET or POST submit, no JavaScript handling it) with a GTM Form Submission trigger and Wait for Tags enabled submits normally, the page reloads — and Tag Assistant’s Tags panel shows nothing fired for that event. No error, no partial result, just silence where a fired tag should show up.

This looks identical to a trigger that genuinely never matched. The difference only shows up once you stop trusting the live panel and go to the raw data.

The Diagnostic: Export the Tag Assistant debug session as JSON (not a screenshot of the live panel) and find the message corresponding to the form submit event. Check the tag’s execute field — if it reads execute_succeeded with correctly resolved parameter values, the tag ran. The live panel’s silence doesn’t match the export’s own record of what happened.

Tag Assistant Disconnects and Reconnects Right at Submission

What’s Happening: Watching Tag Assistant’s live panel during the actual submit, you can see it visibly drop connection and reconnect right as the page navigates. This is expected behavior for any full-page-reload form, Wait for Tags or not — Tag Assistant’s live debug session lives inside the page’s own JavaScript context, and a full navigation destroys that context entirely. It has to reconnect from scratch on the new page.

GA4’s own hit, by contrast, is typically sent via sendBeacon or an equivalent mechanism specifically designed to survive page unload — the browser guarantees delivery even as the page is being torn down. That’s why GA4 can receive a hit that Tag Assistant’s live panel never got to display.

The Diagnostic: If you see the disconnect/reconnect pattern happen right at the moment of submission, treat the live panel as unreliable for that specific event going forward — don’t conclude the tag failed from the panel alone.

Fix 1: Check the Raw JSON Export, Not the Live Panel

Step 1 — Export the debug session as JSON from Tag Assistant’s interface rather than relying on the visual panel.

Step 2 — Find the message matching your form submission event (gtm.formSubmit in the event list).

Step 3 — Check the tag’s execute status within that message. execute_succeeded with resolved parameter values means the tag ran, regardless of what the live panel showed.

Step 4 — Check the resolved values, not just the templated `` references, to confirm the actual data sent was correct.

Fix 2: Confirm in GA4 DebugView by the Tag’s Real Event Name

Step 1 — Open GA4 DebugView and submit the form again.

Step 2 — Search for your tag’s exact configured event name — not GA4’s own auto-collected form_submit event, which can fire independently via Enhanced Measurement and is easy to mistake for your custom tag.

Step 3 — Confirm the event’s parameters match what you configured. This is the actual ground truth — a hit either arrived at GA4’s servers correctly or it didn’t, independent of anything Tag Assistant’s live panel did or didn’t display.

If both the JSON export and DebugView confirm the tag is firing correctly, the “nothing in Tag Assistant” symptom is a debugging-tool limitation on full-page-reload forms, not a configuration problem to keep chasing.

Can’t tell whether your form tags are actually firing in production, or just not showing up where you’re looking? We trace the full trigger-to-hit chain — Tag Assistant exports, GA4 DebugView, and the network payload itself — and tell you exactly what’s really happening. Get a diagnostic.