Guide 10 · Debugging · GA4 + Tag Manager
The Measurement ID does not match the stream: copy it, do not type it
A tag with the wrong Measurement ID fires cleanly and reports cleanly — into someone else's property. Compare the ID in the tag with the ID in the stream, character by character.
After the steps below, the ID in the tag and the ID in the web stream are identical, and a test event appears in the right property's Realtime report.
Download the check: the debugging check (JSON) (MD5 db93958180398b80b8f58666dba8cb84, 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
- The tag that sends the event. The Google tag, or the GA4 Event tag for the event you are chasing.
- Access to the GA4 property. Admin, then Data Streams, then the web stream, where the Measurement ID is shown.
- A test event you can trigger. One action that should send one event, so you can watch where it lands.
- Realtime open on the property. The Realtime report, to see whether your test event arrives in this property or not.
The trace
The worked check: the figures below were recomputed before publication, and the note under the table shows the working.
| Check | Figure |
|---|---|
| Characters in the Measurement ID | 11 |
| Characters that matched between tag and stream | 10 |
| Characters that differed | 1 |
| Test events that landed in the right property | 0 |
| Test events that landed in the other property | 4 |
The ID has 11 characters, G- plus 9 more, and 10 of them matched between the tag and the stream — 11 minus 10 is 1 character different, a single mistyped letter. Four test events were sent and 0 landed in the right property while 4 landed in the other property, so 4 of 4 went to the wrong place because of one character.
- Copy the ID from the stream. In Analytics, go to Admin, then Data Streams, then the web stream. Copy the Measurement ID from the stream details. Do not type it from memory and do not copy it from a chat message or an old document.
- Read the ID in the tag. Open the Google tag in Tag Manager, or the GA4 Event tag for the event. Read the Tag ID or the Measurement ID field exactly as saved. If the tag uses a variable for the ID, open the variable and read its value.
- Compare them character by character. Put the two IDs side by side. They must be identical — G-, then the same letters and digits in the same order. One different character sends every event to a different property, and nothing in Tag Assistant will flag it, because the tag itself is working.
- Send one test event and watch Realtime. Trigger the event once and look at the Realtime report on the right property. If the event appears there within minutes, the IDs match. If Realtime stays empty, open the other property you have access to and look there — the event will usually be sitting in it.
- Fix the tag, then test again. Paste the copied ID into the tag, save, and test in Preview first. Then publish the version and repeat the test. The Realtime report on the right property should now show the event.
Dead ends
DEAD END — TYPING THE ID FROM MEMORY. G- IDs are 10 or 11 characters of look-alike letters and digits. Typing one from memory is how a single wrong character gets in. Copy it from the stream every time, even when you are sure you know it.
DEAD END — THE TAG FIRES, SO THE ID MUST BE RIGHT. A tag fires when its trigger matches, whatever ID it carries. Tag Assistant shows Tags Fired for a tag sending to the wrong property, because firing and addressing are two different things. Fired proves the trigger; only the ID proves the destination.
DEAD END — CHECKING REALTIME ON THE WRONG PROPERTY. If the ID points elsewhere, Realtime on your property stays empty however many test events you send, and each empty check feels like proof the tag is broken. Check the property the ID actually names before you rebuild the tag.
End state
The ID copied from the stream, compared character by character with the ID in the tag, and a test event seen in the right property's Realtime report. From here, a missing event is not an addressing problem — the mail is going to the right house.
Sources
- Tag Manager Help — Preview and debug containers — Preview mode showing which tags fired, which does not by itself prove the tag sends to the right property
- Analytics Help — Confirm that you are collecting data — The Realtime report as the same-day check that an event arrived in the property
Checked 11 November 2026. The click paths above are the ones in Google's help pages, opened 11 November 2026. What was run: the ID comparison, recomputed — 11 characters, 10 matching and 1 differing, with 4 of 4 test events landing in the other property and 0 in the right one. 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.