Guide
Consent mode blocking analytics
A banner change put every tag behind a consent state that never resolves. How to tell a blocked tag from a broken one, then confirm the reading.
Last reviewed September 2026.
The banner changed. The dashboards went quiet.
A theme update, a new cookie plugin, or a CMP default that shipped as “denied until chosen” will put every tag behind a state that never becomes granted. The page still loads. Orders still arrive. Nothing errors.
1. Leave the banner alone on the first load
Use a fresh profile. If you automatically accept cookies when you test, you will never see what a new visitor sees. Many “it works on my machine” reports are an accepted banner.
2. Read the state, not the widget
Look at the consent object the CMP writes — often on dataLayer, sometimes on a vendor callback. You want a value that is granted or denied. A missing object, or one that stays pending, means every tag that waits will wait forever.
3. Grant once and watch collect
Accept analytics. If /g/collect or the Meta collect request appears immediately, the tag is fine and the banner was the gate. If it still does not, you have a silent tag on top of a consent problem. Fix one at a time.
4. Unobservable is not broken
Tagnovo will not emit a broken finding on a page where the store’s own control signal did not fire. A banner that blocks everything, including that control, is reported as unobservable.The control that stops a false alarm.
If you need a second confirmed reading after a CMP change,watch the store rather than relying on one manual check.
Confirm it with a scan
Four page types, a real browser, no account. A scan will not fix the tag. It will tell you whether it is firing now.