How to Check If Google Consent Mode v2 Is Working

What Consent Mode v2 Is (In 3 Sentences)

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.

How to Verify in 30 Seconds

For a complete check - including timing, updates, and attribution - run the diagnostic scan above.

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.

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.

What a Correct Consent Mode v2 Setup Looks Like

A proper Consent Mode v2 setup includes a default consent declaration that runs before any Google tags load:

gtag('consent', 'default', {
  ad_storage: 'denied',
  analytics_storage: 'denied',
  ad_user_data: 'denied',
  ad_personalization: 'denied',
  wait_for_update: 500
});

If you don’t see this (or an equivalent GTM implementation) executing before Google tags load, Consent Mode v2 is not configured correctly.

What Parameters Does Consent Mode v2 Require?

Consent Mode v2 uses five parameters in the default consent declaration. Each controls a specific type of data or behavior:

• ad_storage — Controls whether advertising cookies (e.g., for remarketing) can be set. Must be "denied" by default until the user consents.
• analytics_storage — Controls whether analytics cookies (e.g., GA4) can be set. Must be "denied" by default until the user consents.
• ad_user_data — Controls whether user data can be shared with Google for advertising purposes (e.g., hashed emails). Required for Consent Mode v2.
• ad_personalization — Controls whether data can be used for personalized advertising. Required for Consent Mode v2.
• wait_for_update — Tells Google how long (in milliseconds) to wait for a consent update before assuming the default state is final. Typically 500ms.

All five must be set in your default consent for full Consent Mode v2 compliance. Missing ad_user_data or ad_personalization is a common mistake that leaves you on v1 instead of v2.

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? See our guide on the Consent Mode default state.
• 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?

This problem rarely exists alone - it typically occurs alongside other consent or timing issues covered in the comprehensive guide on Google Ads conversion failures.

What Happens If Consent Mode v2 Isn't Working

If Consent Mode v2 isn't configured correctly, here's what breaks:

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:

How to Check If Consent Mode v2 Is Enabled in Google Tag Manager

If you use Google Tag Manager, Consent Mode v2 is typically implemented via a tag or template. Here's how to verify it's set up correctly:

1. Go to GTM — Open your Google Tag Manager container and navigate to Tags.
2. Look for a Consent Initialization trigger — Consent Mode v2 should fire on "Consent Initialization – All Pages" (or equivalent). This ensures it runs before any other tags.
3. Check the tag order — The Consent Mode tag must fire before GA4, Google Ads, or any other Google tags. In GTM, use tag sequencing or firing order to enforce this.
4. Look for the default denied config — The tag should set ad_storage, analytics_storage, ad_user_data, and ad_personalization to "denied" by default. See our GTM Consent Mode template guide for implementation details.

If any of these are missing or misconfigured, Consent Mode v2 won't work correctly. Run our free scan to get an automated check of your live site.

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.