Guide 06 · Debugging · GA4 + Tag Manager
debug_mode in Tag Manager: turn it on for one tag, then take it off again
In Tag Manager, debug_mode goes in the Google tag for all events or in one GA4 Event tag for a single event. The off switch is removing the field — false does not turn it off.
After the steps below, the event you are testing appears in DebugView, no other event is affected, and the field is removed before the version is published.
Download the check: the debugging check (JSON) (MD5 47e5345a9d4e2e5140d6bd92b54f4b21, 464 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
- A Tag Manager workspace you can edit. Changing a tag needs the Editor role on the container; a read-only workspace cannot save the change.
- The tag to test. Know whether you want every event in DebugView or one event only — that decides where the field goes.
- Access to DebugView. Admin, then Data display, then DebugView, on the property the tag sends to.
- A note of the version you started from. Write down the current version name, so the debug change is easy to undo and easy to spot in the version list.
The trace
The worked check: the figures below were recomputed before publication, and the note under the table shows the working.
| Check | Figure |
|---|---|
| Events the test tag sent during the session | 12 |
| Events from the test tag that reached DebugView | 12 |
| Events from other tags that reached DebugView | 0 |
| Share of the test tag's events in DebugView | 100.00% |
The test tag sent 12 events during the session and 12 of them reached DebugView, so 12 divided by 12 is 100.00%. No event from any other tag reached DebugView, so 0 other events were affected — the field was on one tag only, exactly as intended.
- Decide the scope: one tag or all tags. To watch every event, the field goes in the Google tag. To watch one event only, it goes in that event's GA4 Event tag. One tag is the safer choice: it keeps other visitors' data out of your debug stream and keeps the change small.
- Open the tag and add the field. In the workspace, open Tags and click the tag. In the tag settings, add a field named
debug_modeand set it totrue. For the Google tag this watches all events; for a GA4 Event tag it watches that event only. Save the tag. - Test in Preview, not in the published version. Click Preview, connect your site, and do the test action. Preview runs the workspace draft, so the debug field is live for you and invisible to everyone else. Check DebugView: the event should appear in the Seconds stream within a minute.
- Confirm nothing else followed it into DebugView. If you set the field on one GA4 Event tag, only that event should appear. If page views and other events appear too, the field is on the Google tag instead. Move it, or accept the wider scope and note it.
- Remove the field before you publish. To disable debug mode, remove the
debug_modefield from the tag. Setting it tofalsedoes not disable it. Save, then publish the version without the field, so test traffic never flows into the live reports.
Dead ends
DEAD END — debug_mode SET TO FALSE, STILL DEBUGGING. Google's own page says it plainly: to disable debug mode, exclude the field; setting it to false does not disable it. If test traffic keeps appearing in DebugView after your fix, open the tag and check the field is gone, not set to false.
DEAD END — THE FIELD ON THE GOOGLE TAG WHEN YOU MEANT ONE EVENT. debug_mode on the Google tag marks every event from every visitor for DebugView while that version is live. If you only need one event, put the field on that event's tag and nowhere else.
DEAD END — PUBLISHING THE DEBUG VERSION. Preview tests the draft; publishing ships it. A version published with debug_mode still in the tag sends every visitor's events to DebugView. Remove the field first, then publish, then check DebugView is quiet.
End state
The field added to exactly one tag, the event confirmed in DebugView through Preview, and the field removed before publishing. Debug mode did its job — it showed one event, once — and left nothing behind in the live container.
Sources
- Analytics Help — Monitor events in DebugView — Setting debug_mode to true in the Google tag for all events or in a GA4 Event tag for some events, and removing the field to disable it
- Tag Manager Help — Preview and debug containers — Preview mode testing the workspace draft before anything is published
Checked 11 November 2026. The click paths above are the ones in Google's help pages, opened 11 November 2026. What was run: the DebugView share, recomputed — 12 of 12 events from the test tag reached DebugView, 100.00%, with 0 events from other tags. 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.