Consent Mode v2 Tags Not Firing After Accept: What to Check
A practical walkthrough for the frustrating case where the banner works, the user clicks accept, and measurement still does not behave.
Audience: GTM specialists, developers, legal operations, and marketing teams.
Common problem
Everything looks fine on the surface: the banner loads, the accept button works, but GA4 or ad tags still do not behave the way the team expects.
Why it matters
This is where marketing, analytics, development, and legal teams start talking past each other. One team sees a banner; another sees missing signals; nobody is sure which part failed.
How Measure Copilot helps
Consent Mode checks look for the four consent signals, CMP clues, default/update evidence, and tags that may be firing before consent is established.
Evidence to upload
- Website URL scan with consent and tag signals.
- GTM JSON export showing tag consent settings, triggers, and exceptions.
- GTM Preview or Tag Assistant evidence for accepted and denied consent paths.
Productivity angle: The report gives each team a lane: analyst for measurement evidence, developer for implementation timing, legal/privacy for policy review, and platform owner for CMP settings.
Key takeaways
- A visible banner is not the same thing as a working consent sequence.
- The key moments are default state, user choice, consent update, and what each tag does after that update.
- Measure Copilot keeps the line clear between technical consent risk and legal compliance review.
Accepted consent is only one moment in the flow
The click is only the most visible part. The full story starts before the banner appears and continues after the user makes a choice.
If the first page view already passed, or the tag was blocked in the wrong way, accepting consent might not replay the measurement moment you expected.
Check blocking in more than one place
Consent behavior can be shaped by GTM triggers, tag consent settings, CMP autoblocking, custom scripts, and older workarounds that nobody has touched in a year.
A good audit does not say “compliant” because a banner exists. It says what was seen, what was not seen, and what needs runtime proof.
Legal and technical ownership are different
Measure Copilot can surface technical consent risks, but it does not provide legal advice or certify regulatory compliance.
Legal teams should review policy and regional requirements, while analysts and developers verify the tag behavior.
How to use Measure Copilot for this audit
Run a URL audit first, then upload the relevant evidence files. The report separates confirmed findings from high-risk signals and missing-data gaps, so you can decide what to fix now and what needs more proof.
Run a trust auditFAQ
Should Google tags be completely blocked until consent?
Google's Consent Mode guidance explains that Google tags can adjust behavior based on consent state. Blocking behavior depends on implementation, CMP, region, and tag type, so teams should review official guidance and legal requirements.
Can Measure Copilot confirm region-based consent behavior?
Only with region-specific evidence. Without that evidence, the report should mark regional behavior as Needs More Data.