Consent Mode v2 Readiness Checker
Check your Google Consent Mode v2 implementation status and get a prioritized fix list.
Google's Consent Mode v2 requires sites serving EU visitors to pass four consent signals to Google tags: ad_storage, analytics_storage, ad_user_data, and ad_personalization. Without these signals configured correctly, Google Ads loses access to remarketing audiences and GA4 can no longer model conversions for users who decline cookies.
This checker walks you through every requirement: tag installation, consent defaults, consent updates, advanced features like URL passthrough and redaction, and CMP integration. Check the items that match your current setup and the tool generates a prioritized remediation list showing exactly what to fix first, complete with code snippets and implementation notes.
Built for developers and marketing teams running Google Ads or GA4 on sites with EU traffic. No data leaves your browser; the entire assessment runs client-side.
Check all that apply to your current setup:
Basic Setup
Consent Mode Implementation
Advanced Features
Testing & Verification
Frequently Asked Questions
- What is Google Consent Mode v2?
- Consent Mode v2 is Google's framework for adjusting how Google tags behave based on user consent choices. It requires two new signals (ad_user_data and ad_personalization) alongside the original analytics_storage and ad_storage signals. Sites running Google Ads or GA4 in the EU must implement it to maintain measurement and remarketing capabilities.
- Do I need Consent Mode if I only use GA4 (no Google Ads)?
- Yes. GA4 uses the analytics_storage signal from Consent Mode to decide whether to set cookies. Without Consent Mode, GA4 falls back to cookieless pings with limited data. Implementing Consent Mode lets GA4 model conversions for users who decline cookies, recovering some of the data you would otherwise lose.
- What happens if my CMP loads after gtag?
- If your CMP loads after the Google tag, the consent default command never fires before data collection begins. This means Google tags briefly run without consent signals, which can lead to non-compliant data collection. The fix is to load your CMP synchronously before gtag, or use the consent initialization callback.
- How do I test that Consent Mode is working?
- Open Chrome DevTools, go to the Network tab, and filter for collect requests to google-analytics.com. Check the gcs parameter in the request URL: it encodes the consent state for each signal. You can also use the Tag Assistant Chrome extension to see consent state changes in real time.
Related Resources
Consent Mode v2 Setup Playbook
Step-by-step implementation guide with GTM templates and test cases.
PlaybookCookie Consent Banner Setup
How to implement a compliant cookie banner that works with Consent Mode.
DownloadConsent Mode v2 Checklist (PDF)
Printable implementation checklist for your team.