Google Consent Mode v2 Check — Is It Actually Working?
You're here because Google said you need Consent Mode v2, or you're wondering if yours is configured correctly. You might have installed Google Tag Manager, added a consent banner, and assumed everything is working. But most sites that think they have Consent Mode v2 actually don't—or it's misconfigured in ways that break conversion tracking.
The problem: Consent Mode v2 isn't something you install. It's something you configure. Having Google Tag Manager doesn't mean you have Consent Mode. Having a cookie banner doesn't mean Consent Mode is working. And without proper configuration, Google can't model conversions when users don't consent—meaning you lose conversion data entirely.
The uncertainty is real: Your setup looks fine, but is it actually doing what Google needs? Here's how to check.
Check Your Consent Mode v2 Setup Now
Run a free scan to verify if Consent Mode v2 is properly configured on your site.
Run Free Scan →What Consent Mode v2 Is (In 3 Sentences)
Consent Mode v2 is Google's way of telling its tracking systems (Google Ads, Google Analytics) what consent state users have granted, allowing Google to model conversion data even when consent isn't given.
When properly configured, it sends consent signals to Google before any tracking scripts run, so Google knows whether to track fully, track with modeling, or not track at all.
Without Consent Mode v2, Google can't model conversions for users who reject cookies—meaning you lose conversion data for a significant portion of your traffic.
That's it. Consent Mode v2 is essentially a communication protocol between your site and Google's tracking systems. It doesn't replace your consent banner—it works alongside it to tell Google what's allowed.
Why Google Cares (And Why You Should Too)
Google introduced Consent Mode v2 because of a simple problem: When users reject cookies, tracking stops entirely. Without tracking, Google can't measure conversions. Without conversion data, Google Ads can't optimize campaigns effectively.
Consent Mode v2 solves this by allowing Google to:
- Model conversions when users don't grant consent, using aggregated data and machine learning to estimate conversion rates
- Maintain campaign optimization even with partial consent, so your ad spend isn't wasted on campaigns that can't measure results
- Improve audience building by using modeled data to populate retargeting lists and lookalike audiences
- Comply with privacy regulations while still getting useful measurement data
For you, this means: If you don't have Consent Mode v2 configured correctly, you're losing conversion data. Every user who rejects cookies becomes invisible to Google Ads optimization. That could be 30%, 50%, or even more of your traffic—completely unmeasured.
The kicker? Google requires Consent Mode v2 for certain features and may penalize campaigns that don't have it properly configured. Without it, you're not just missing data—you're potentially limiting your campaign performance.
Why Most Sites Think They Have It But Don't
This is the most common misconception: "I have Google Tag Manager, so I must have Consent Mode v2." Or: "I have a cookie banner, so Consent Mode is working."
Reality check: Having Google Tag Manager doesn't give you Consent Mode. Having a cookie banner doesn't configure Consent Mode. Consent Mode v2 requires specific code that declares consent states to Google—and most sites are missing it.
Misconception #1: "I Use Google Tag Manager, So I'm Covered"
Google Tag Manager is just a container for your tags. It doesn't automatically configure Consent Mode v2. You still need to add the Consent Mode code that declares default consent states (denied) and updates them when users consent. Without this code, GTM tags run, but Google doesn't know the consent state—so modeling doesn't work.
Misconception #2: "My Cookie Banner Means Consent Mode Is Working"
Cookie banners collect consent from users. Consent Mode v2 communicates that consent to Google. These are two separate things. Your banner can work perfectly, but if it doesn't trigger Consent Mode updates, Google never knows what consent state users have—so it can't model conversions.
Misconception #3: "I Added the Code, So It's Working"
Even if you added Consent Mode code, it might be in the wrong place, configured incorrectly, or not updating when users consent. The code needs to run before any Google tags load, declare default states as "denied," and update when users accept or reject. Most implementations miss at least one of these steps.
Misconception #4: "It Worked Before, So It Still Works"
Consent Mode v2 is a recent requirement. Older implementations of Consent Mode (v1) don't meet current requirements. If you set this up months ago, it might be using the old version or missing new parameters that Google now requires.
The only way to know for sure if Consent Mode v2 is working is to test it. You need to check if:
- Consent Mode code runs before any Google tags load
- Default consent state is set to "denied"
- Consent state updates when users accept or reject cookies
- Google receives the consent signals correctly
This is exactly what our scan checks—not just whether the code exists, but whether it's configured correctly and actually communicating with Google.
How to Check If Consent Mode v2 Is Configured
You could manually inspect your code, check browser network requests, and test consent flows—or you can run a 10-second diagnostic scan that does all of this automatically.
Our scan specifically checks for:
- Consent Mode v2 detection: Is the code present and configured?
- Default state: Is consent defaulting to "denied" as required?
- Consent updates: Does the consent state change when users accept or reject?
- Timing: Does Consent Mode run before tracking scripts load?
- Integration: Are consent updates properly connected to your banner?
💡 No technical knowledge needed. Just paste your URL and get instant results.
Check Consent Mode v2 →What Happens If Consent Mode v2 Isn't Working
If Consent Mode v2 isn't configured correctly, here's what breaks:
Lost Conversion Data
Google can't model conversions for users who reject cookies, so you lose measurement data for a significant portion of your traffic.
Poor Campaign Optimization
Without complete conversion data, Google Ads can't optimize bid strategies effectively, leading to wasted ad spend.
Incomplete Audiences
Retargeting and lookalike audiences won't populate correctly because conversion signals are missing.
Compliance Gaps
Without proper Consent Mode configuration, you might be tracking users who rejected cookies, creating compliance issues.
The bottom line: Without Consent Mode v2 working correctly, you're operating with incomplete data and potentially wasting ad spend. The fix is usually straightforward once you know what's missing.
Common Consent Mode v2 Configuration Mistakes
Even when sites try to implement Consent Mode v2, they often make these mistakes:
Code Runs After Tags Load
Consent Mode code must run before any Google tags (GA4, Google Ads) load. If tags load first, they don't receive the consent signals and run in a default state—which breaks measurement.
Default State Not Set to "Denied"
Consent Mode v2 requires default consent states to be "denied" until users explicitly grant consent. If defaults aren't set, Google assumes consent is granted, which violates privacy requirements.
Consent Updates Don't Trigger
When users accept or reject cookies, your consent banner needs to call Consent Mode update functions. If this connection is missing, consent states never update, and Google can't model conversions correctly.
Using Consent Mode v1 Instead of v2
Older Consent Mode implementations don't meet current requirements. You need the v2 parameters and structure. Many sites think they're compliant but are using outdated code.
Next Steps: Verify Your Setup
Don't guess whether Consent Mode v2 is working. Run a diagnostic scan to get a definitive answer. The scan checks all the critical configuration points and tells you exactly what's missing or misconfigured.
Check Your Consent Mode v2 Configuration
Run a free scan to verify if Consent Mode v2 is properly set up on your site. Get instant results with specific fixes if anything is misconfigured.
Run Free Scan →Related resources: