Guide 19 · Debugging · GA4 + Tag Manager
The event arrives but its parameters are missing: read the payload, then the tag
An event with no parameters is a tag that sends a name and nothing else. Read the payload in the network tab, then the parameter list in the tag, and the missing row will show itself.
After the steps below, the event carries every parameter the report needs, the payload shows each value, and DebugView lists the same parameters.
Download the check: the debugging check (JSON) (MD5 93d7253554cde0affde6c99dcbfe4823, 445 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
- The event in DebugView. Click it and read the parameter list it arrived with — that list is the evidence.
- The tag that sends it. The GA4 Event tag in Tag Manager, open on its parameter list.
- The data layer values the tag reads. The variables the parameters point to, and what they hold when the event fires.
- The parameter list the event should carry. Written down from the tag's design, not from memory.
The trace
The worked check: the figures below were recomputed before publication, and the note under the table shows the working.
| Check | Figure |
|---|---|
| Parameters the event should carry | 6 |
| Parameters present in DebugView | 4 |
| Parameters missing | 2 |
| Missing parameters that were empty variables | 2 |
| Parameters present after the fix | 6 |
The event should carry 6 parameters and DebugView showed 4, so 6 minus 4 is 2 missing. Both missing parameters pointed at data layer variables that held nothing when the event fired — 2 of 2 — so the fix was the variables, not the tag. After the fix, 6 of 6 parameters were present.
- Read the parameters in DebugView. Open DebugView, find the event, and click it. The parameter list shows what GA4 received. Count it against the list the event should carry. In the worked check, 4 of 6 were present. Write down which ones are missing, by name — the names are the diagnosis.
- Read the parameter list in the tag. Open the GA4 Event tag and read its event parameters, one row at a time. A parameter that is not in the tag at all was never configured; a parameter that is in the tag but absent from DebugView is configured and failing.
- Check what each variable holds when the event fires. For each missing parameter, open the variable it points to — usually a data layer variable — and check its value at the moment the event fires. In Preview, the Variables tab shows each variable's value for the selected event. A variable that shows undefined at that moment is the break.
- Check the timing, not just the value. A variable that holds the right value a second after the event fires is still empty when the tag reads it. If the data layer push happens after the tag fires, the parameter is missing even though the data exists on the page. Move the push earlier, or move the trigger later.
- Send a fresh event and count the parameters again. After the fix, do the action once and read the parameter list in DebugView again. The count should be 6 of 6. If a parameter is still missing, its variable is still empty at fire time — read the Variables tab for that event again.
Dead ends
DEAD END — ADDING THE PARAMETER TO THE REPORT. A parameter that never arrives cannot be added to a report, registered as a dimension, or fixed in the report builder. The report reads what GA4 received. If DebugView shows 4 parameters, the report will show 4, and no report change adds the other 2.
DEAD END — THE VARIABLE HOLDS THE VALUE LATER. Checking the data layer after the page has finished loading shows the value present, and the tester concludes the variable is fine. The tag reads the variable when it fires, not when the page finishes. Read the value for the event, in Preview, at fire time.
DEAD END — A NAME THAT IS ALMOST RIGHT. A parameter named item_price in the tag and itemPrice in the data layer never meets its variable. Parameter and variable names are case-sensitive. Copy the name from the data layer push, not from the tag's memory of it.
End state
The event carrying all 6 parameters, each one read in DebugView and matched to a variable that holds a value at fire time. A missing parameter is now a named row in a tag, not a mystery in a report — and the report can finally be built on it.
Sources
- Analytics Help — Monitor events in DebugView — Clicking an event in DebugView to see its associated parameters, and the Seconds stream showing events from the last 60 seconds
- Tag Manager Help — Preview and debug containers — The debug interface showing what data each tag passes, including the variables for each 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 parameter counts, recomputed — 6 expected, 4 present, so 2 missing, both from empty variables, and 6 of 6 present after the fix. 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.