GA4 Ultimate Stack
Orphaned, rug-pulled or unaccounted: reading parity findings
Each parity finding means something specific. Learn what each one tells you, what it doesn't, and where to look first.
Six findings, six meanings
A parity mismatch isn't automatically a bug. The checker separates real breaks from events that are simply built or sent differently:
| Finding | What it means | Default |
|---|---|---|
| Orphaned tracking | GTM fires it, GA4 has never recorded it | On |
| Rug-pulled key event | Still a key event, not recorded in the lookback, and nothing produces it | On |
| Unaccounted key event | GA4 records it, but no tag in this container or GA4 rule explains it | On |
| Portfolio consistency | Set differently across brands | On |
| GA4-derived | Built by a GA4 create or modify rule whose source event is alive | Off |
| Not a key event | Fires and is recorded, just not a conversion | Off |
A two-column list of the six parity findings with short meanings.
Orphaned tracking
GTM sends the event, but GA4 has never recorded it. It is invisible everywhere. Common causes: the tag sends to the wrong Measurement ID, consent blocks it, a trigger never fires in practice, or something filters it on the way. Start in GTM preview mode on the journey, then check the Measurement ID and consent.
A GTM tag sends checkout_started, something in between blocks it, and GA4 has never recorded it.
Rug-pulled key events
The event is still a key event in GA4, but GA4 hasn't recorded it in the lookback window and no GTM tag or GA4 rule produces it. Reports quietly show zero conversions. This is the finding to act on fastest. For low-volume events, rerun with the 30-day lookback before concluding it has stopped.
A daily bar chart of purchase dropping to zero for seven days, labelled rug-pulled.
Unaccounted key events
GA4 is recording the event, but nothing in this container and no GA4 rule explains it. It isn't broken: it comes from somewhere else. Usual sources: the Measurement Protocol, a platform's own gtag.js, a sibling GTM container, an app stream, server-side GTM, or a tag whose event name is a variable. Find the source before you change anything, because removing the wrong one stops real data.
Five possible outside sources pointing at an event GA4 records without a matching GTM tag.
GA4-derived and not-a-key-event
A GA4-derived key event has no tag of its own because a GA4 rule builds it from an event that is still firing. That's healthy. The checker confirms the source event is alive but doesn't evaluate the rule's parameter conditions. Not a key event means an event fires and is recorded but isn't marked as a conversion, which is expected for most events. Turn both on when you are auditing what should count.
A short checklist explaining the not-a-key-event finding.
From finding to fix
- Confirm the bond is verified and points at the right property.
- Reproduce the finding in preview mode or with a test journey.
- Fix it in the right place: the GTM tag, the GA4 key event, or the outside source.
- Run parity again with the same lookback.
Four steps from a parity finding to a verified fix.
ODDVX for Windows
Every property, one screen.
Start free on one GA4 brand per run. Premium adds every brand in one run, batch writes, exports and scheduled checks.