Introduction
A Google Consent Mode v2 checker should answer a practical question: on a real first visit, do your Google tags respect visitor consent — and do the right Consent Mode v2 parameters appear before and after Accept, Reject, or preference changes?
Tag Assistant alone is not enough. Preview sessions, logged-in browsers, and prior consent cookies can hide production failures. This guide explains what to test, what signals matter, and how technical diagnostics complement manual verification. Read Consent Mode v2 vs Google Certified CMP first if you are unsure whether you need Consent Mode diagnostics or a certified CMP.
GDPRChecker supports Consent Mode v2 diagnostics. It is not currently a Google Certified CMP or IAB TCF CMP. Automated checks are technical checks only and are not legal advice.
- What is Google CMP
- Google Certified CMP
- What is IAB TCF
- Google CMP and Consent Mode
- Google CMP Requirements
- Google CMP Setup Guide (clarified)
- How to Validate Google CMP
- Google CMP vs Cookiebot
- Consent Mode v2 vs Google Certified CMP
- Do I need a CMP if I don't run Google Ads?
- Google Consent Mode v2 checker guide
What a Consent Mode v2 checker should do
A useful checker inspects production behavior from a clean context — similar to a first-time EU visitor with no prior consent cookies. It should not rely only on configuration screenshots or GTM preview mode.
- Detect whether Google tags are present (GA4, GTM, Google Ads, Floodlight).
- Detect whether Consent Mode default and update signals exist.
- Verify key v2 parameters: analytics_storage, ad_storage, ad_user_data, ad_personalization.
- Flag pre-consent requests to Google measurement domains.
- Flag non-Google marketing and analytics trackers that run before consent.
- Confirm protection on key URLs, not only the homepage.
| Check | What good looks like | Common failure |
|---|---|---|
| Consent Mode detected | gtag consent default/update or equivalent GTM signals present | Google tags load with no consent API usage |
| Default denied before tags | analytics_storage and ad_storage denied on first paint | Tags fire and set cookies before banner interaction |
| v2 parameters present | ad_user_data and ad_personalization included with v2 setups | Only legacy analytics_storage and ad_storage mapped |
| Update on Accept | Relevant parameters move to granted after opt-in | UI accepts but data layer never updates |
| Update on Reject | Parameters stay denied; no new ad/analytics cookies | Reject closes banner but tags keep running |
| Tag order | Consent defaults before GTM/gtag snippet | GTM container executes before consent initialization |
| Non-Google trackers | Meta, LinkedIn, Hotjar blocked until consent where required | Third-party pixels fire on first load |
| Page coverage | Important templates and landing pages protected | Consent works on homepage only |
Consent Mode v2 parameters to verify
Consent Mode v2 extends the original model with ad_user_data and ad_personalization. A checker should confirm all four core advertising and analytics parameters are set in defaults and updated consistently when users change choices.
- analytics_storage — GA4 measurement cookies and behavioral association
- ad_storage — Google Ads audience and conversion cookies
- ad_user_data — whether site data may be used for advertising purposes
- ad_personalization — whether data may be used for personalized ads
- functionality_storage — optional, when you map functional cookies through Consent Mode
- personalization_storage — optional, for experience personalization categories
- security_storage — often granted for security-related storage where applicable
Passing a Consent Mode v2 checker does not mean your site is GDPR compliant. It means the technical consent signal layer appears to behave as expected in automated tests.
Manual checks vs automated diagnostics
The strongest verification combines manual browser tests with automated scans. Manual testing catches category mapping nuances. Automated scans catch regressions after GTM publishes, plugin updates, or template changes.
- Open a fresh private window with no stored consent.
- Load the page and inspect network requests before interacting with the banner.
- Reject all and confirm Google and marketing requests do not write non-essential cookies.
- Accept analytics only and confirm ad parameters remain denied.
- Accept all and confirm parameters update together where intended.
- Navigate internal pages and confirm consent state persists.
- Run an independent scanner on the same URLs for a second opinion.
For step-by-step manual verification, see Verify Google Consent Mode.
Further reading
Browser DevTools complements automated Consent Mode checks. In a private window, open the Network tab before you interact with the cookie banner, then reload the page. Filter for common measurement endpoints — GA4 collect requests, GTM container loads, DoubleClick, and Meta Pixel — to see whether any non-essential requests start before consent.
Common failures a checker should catch
- GTM loads before Consent Initialization or default denied declaration.
- Consent update fires on Accept but not on Reject or preference changes.
- ad_user_data and ad_personalization missing from update calls.
- Banner appears only on homepage while campaign landing pages bypass it.
- Consent Mode configured in preview but not in published container.
- Third-party pixels unaffected by Consent Mode because they are not Google tags.
- Server-side tags ignore client consent state without explicit propagation.
Consent Mode governs Google tag behavior. It does not automatically control Meta Pixel, LinkedIn Insight Tag, Hotjar, Clarity, or other vendors. Those require separate blocking or category wiring.
Consent Mode checker vs Google Certified CMP
A Consent Mode v2 checker validates signal and tag behavior for Google measurement products. A Google Certified CMP is a different requirement for specific publisher advertising scenarios such as AdSense, Google Ad Manager, and AdMob in the EEA, UK, and Switzerland.
If you monetize with Google publisher ads, Consent Mode diagnostics alone may not be enough. You may need a Google Certified CMP with IAB TCF support where required.
See Do I need a CMP if I don't run Google Ads? for sites without paid Google advertising.
How GDPRChecker helps
GDPRChecker is designed for small teams that need repeatable technical checks on live sites. It complements GTM debugging by scanning from a clean context and flagging pre-consent trackers alongside Consent Mode signals.
- Detect Google Consent Mode v2 signals on scanned pages
- Check whether key Consent Mode v2 parameters appear in page signals
- Identify Google tags and common marketing pixels
- Flag possible pre-consent tracking requests
- Verify runtime script placement and page coverage where configured
- Provide actionable diagnostics for engineering and marketing teams
GDPRChecker provides automated technical checks. It does not provide legal advice, does not guarantee GDPR compliance, and is not currently a Google Certified CMP or IAB TCF CMP.
Run a Consent Mode v2 check
Test your production site for Consent Mode v2 signals, Google tag behavior, and pre-consent trackers in one scan.