Check explainer
Consent activates measurement
If nothing fires after "Accept", the consent wiring is likely broken, you lose data despite opt-in.
- note
- ok
What we check
Checks whether analytics measurement actually fires after "Accept".
Why it matters
If nothing fires after "Accept", the consent wiring is likely broken, you lose data despite opt-in.
Common causes
- The tags hang on triggers that never fire after opt-in. The consent update arrives, but no event releases the tags.
- The CMP blocks scripts via a
type="text/plain"rewrite, and after a relaunch the unblocking no longer matches the changed script paths. - Tracking deliberately runs server-side and the web trigger was removed, then the finding is expected and not an error.
- Tags only fire on the production domain, but a staging or preview URL was scanned.
How to fix it
Check the CMP triggers and tag sequencing: tags must actually fire after the consent update.
What does a failing Consent activates measurement finding mean?
If nothing fires after "Accept", the consent wiring is likely broken, you lose data despite opt-in. Check the CMP triggers and tag sequencing: tags must actually fire after the consent update.
How do you fix Consent activates measurement?
Check the CMP triggers and tag sequencing: tags must actually fire after the consent update.