Consent activates measurement

If nothing fires after "Accept", the consent wiring is likely broken, you lose data despite opt-in.

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.

The fix

Check the CMP triggers and tag sequencing: tags must actually fire after the consent update.

Matching template

Consent Mode Audit Checklist

Seven layers, each with a check, a failure signal and an owner. Covers this finding and the six around it.

Get the checklist →

Check it yourself first

The Tracking Check tests this point along with all the others, in seconds.

Start the Tracking Check →

Asked often

What does a failing "Consent activates measurement" check 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 a failing "Consent activates measurement" check?

Check the CMP triggers and tag sequencing: tags must actually fire after the consent update.

The fix, delivered

Wired up in days, not sprints.

Findings from the Tracking Check go into a ranked sequence with effort estimates in the Audit Sprint, every module with an acceptance criterion.

To the service Request an Audit Sprint