Back to Blog
AnalyticsJune 11, 2026
Consent Mode v2 Setup, CMP, GA4, Google Ads, and a Practical Checklist
Direct answer
Consent Mode v2 works when your CMP, tag manager, GA4, and Google Ads all pass the same consent state consistently. Most failures come from partial implementations where one tool updates and the others do not.
What Consent Mode actually changes
It changes how tags behave before and after consent. That affects:
- cookie storage
- attribution completeness
- modeled conversions
- audience eligibility
Minimum setup components
- a CMP that supports granular purposes
- tag manager logic that reads consent signals
- GA4 and Google Ads tags listening to those signals
- QA on both consented and denied states
A practical checklist
| Area | What to verify |
|---|---|
| banner | clear language and equal choice |
| consent states | denied by default where required |
| tags | respond correctly to granted and denied |
| reporting | modeled conversions understood and documented |
| server side | consent string passed downstream where needed |
Common implementation mistakes
- firing remarketing before consent
- assuming one CMP script configures every downstream tool
- not testing locale variations
- not documenting what “granted” changes in reports
Why this matters for GEO and AI visibility
If your measurement becomes inconsistent, you cannot tell which content works. That breaks the feedback loop you need to improve pages for both Google and AI systems.
If you need AdCharta to review your consent setup and analytics impact, contact us.
Ready to Grow Your Ad Performance?
Get a free audit of your current advertising setup and discover untapped growth opportunities.
hello@adcharta.com