Consent Mode v2 vs Legacy Consent Mode: What's the Difference?
You might have heard that Google requires Consent Mode v2, or you're wondering if your existing Consent Mode setup is still valid. The difference between Consent Mode v2 and legacy Consent Mode isn't just a version number - it's a fundamental change in how consent signals are communicated to Google, and it directly affects whether Google Ads can model conversions for users who reject cookies.
Legacy Consent Mode (the original version) had limitations that prevented proper conversion modeling. Consent Mode v2 addresses these limitations and is now required for modern Google Ads setups. If you're still using legacy Consent Mode, you're likely losing conversion data and breaking Google Ads optimization. This is one of several ways Google Ads conversions break.
This guide explains the key differences, why v2 matters, and how to check which version you're using.
Check Which Consent Mode Version You're Using
Run a free diagnostic scan to verify if you're using Consent Mode v2 or legacy Consent Mode, and identify any configuration issues.
Run Free Scan →The scan checks Consent Mode version, configuration, and whether consent updates fire correctly.
What Is Legacy Consent Mode?
Legacy Consent Mode (also called Consent Mode v1 or the original Consent Mode) was Google's first attempt at managing consent for tracking. It was introduced to help sites comply with GDPR and other privacy regulations while still allowing some level of tracking.
How Legacy Consent Mode Worked
Legacy Consent Mode used a simpler approach:
- It set default consent states (usually 'denied')
- It allowed consent updates when users accepted
- It sent basic consent signals to Google
However, it had significant limitations that prevented proper conversion modeling and attribution.
Limitations of Legacy Consent Mode
- Limited conversion modeling - Google couldn't effectively model conversions for users who rejected cookies
- Incomplete consent signals - Consent signals weren't comprehensive enough for proper attribution
- No region-specific handling - Limited support for different privacy regulations
- Weaker integration - Less effective integration with Google Ads and other Google services
What Is Consent Mode v2?
Consent Mode v2 is Google's updated framework for managing consent. It was introduced to address the limitations of legacy Consent Mode and provide better conversion modeling, especially for Google Ads.
Key Features of Consent Mode v2
- Enhanced conversion modeling - Google can model conversions more accurately for users who reject cookies
- Comprehensive consent signals - More detailed consent information sent to Google
- Better Google Ads integration - Improved attribution and conversion tracking for Google Ads
- Region-specific support - Better handling of different privacy regulations (GDPR, CCPA, etc.)
- Required for modern setups - Google strongly recommends v2 for all new implementations
Why Consent Mode v2 Matters
Consent Mode v2 is required for proper conversion modeling. Without it:
- Google can't model conversions for users who reject cookies
- You lose conversion data for a significant portion of traffic
- Google Ads optimization degrades because algorithms receive incomplete data
- Conversion attribution may fail, causing Google Ads to show 0 conversions but GA4 to show events
Key Differences: Legacy vs v2
Here are the main differences between legacy Consent Mode and Consent Mode v2:
| Feature | Legacy Consent Mode | Consent Mode v2 |
|---|---|---|
| Conversion Modeling | Limited or ineffective | Enhanced and accurate |
| Consent Signals | Basic signals | Comprehensive signals |
| Google Ads Integration | Weak integration | Strong integration |
| Region Support | Limited | Comprehensive |
| Required for Modern Setups | No | Yes (strongly recommended) |
| Default State Handling | Basic | Enhanced with wait_for_update |
Technical Differences in Code
The code differences between legacy and v2 are subtle but important:
Legacy Consent Mode Code
// Legacy Consent Mode (simpler, less effective)
gtag('consent', 'default', {
'ad_storage': 'denied',
'analytics_storage': 'denied'
});Legacy mode didn't include wait_for_update and had less comprehensive consent signal handling.
Consent Mode v2 Code
// Consent Mode v2 (enhanced, recommended)
gtag('consent', 'default', {
'ad_storage': 'denied',
'analytics_storage': 'denied',
'wait_for_update': 500
});The key difference is the wait_for_update parameter, which tells Google to wait for consent updates before processing data. This enables better conversion modeling.
However, the real difference isn't just the code - it's how Google processes the consent signals. v2 sends more comprehensive signals that enable better modeling and attribution.
What Breaks If You're Using Legacy Consent Mode
If you're still using legacy Consent Mode, several things break:
1. Conversion Modeling Fails
Google can't effectively model conversions for users who reject cookies. If 30% of users reject cookies, you lose 30% of conversion data - and Google Ads optimizes on incomplete information.
2. Google Ads Attribution Breaks
Without proper consent signals, Google Ads may suppress conversion attribution. This is why Google Ads shows 0 conversions but GA4 shows events - the tracking code exists, but consent configuration prevents proper attribution.
3. Campaign Optimization Degrades
Google's machine learning algorithms need conversion data to optimize bids, targeting, and ad delivery. Without proper conversion modeling, you're feeding incomplete data, which reduces campaign performance over time.
4. Retargeting Audiences Don't Build
Google Ads remarketing lists require proper consent signals. Without Consent Mode v2, audiences stay empty or incomplete, breaking remarketing campaigns.
How to Check Which Version You're Using
To determine if you're using legacy Consent Mode or Consent Mode v2:
Method 1: Check Your Code
Look for the Consent Mode initialization code. If it includes wait_for_update, you're likely using v2. However, this alone isn't definitive - you need to verify that consent signals are being sent correctly.
Method 2: Check Network Requests
In DevTools Network tab, look for Google requests and check the consent parameters (gcs, gcd). v2 sends more comprehensive signals than legacy mode.
Method 3: Run a Diagnostic Scan
The easiest way is to run an automated diagnostic scan that checks Consent Mode version, configuration, and whether it's working correctly. See how to check Google Consent Mode v2 for manual steps, or run our scan for automated verification.
Should You Migrate from Legacy to v2?
Yes, absolutely. If you're using legacy Consent Mode, you should migrate to Consent Mode v2. Here's why:
- Better conversion modeling - You'll recover conversion data for users who reject cookies
- Improved Google Ads performance - Better attribution and optimization
- Future-proofing - v2 is the standard going forward; legacy mode may lose support
- Compliance - v2 provides better compliance with privacy regulations
- Required for modern setups - Google strongly recommends v2 for all new implementations
The migration is usually straightforward - you just need to update your Consent Mode initialization code to include wait_for_update and ensure consent updates fire correctly. However, you should test thoroughly to make sure everything works after migration.
Common Mistakes When Migrating
When migrating from legacy to v2, people often make these mistakes:
Mistake 1: Only Updating the Code
Adding wait_for_update to your code doesn't guarantee v2 is working. You need to verify that consent signals are being sent correctly and that consent updates fire when users accept.
Mistake 2: Not Testing After Migration
After updating to v2, you must test that conversions still fire correctly and that consent updates work. Don't assume it works just because the code changed.
Mistake 3: Forgetting Consent Updates
v2 requires that consent updates fire when users accept. If you only update the initialization code but don't ensure consent updates work, v2 won't function correctly.
See common Google Consent Mode v2 mistakes for a complete list of configuration errors to avoid.
How Consent Mode v2 Affects Google Ads
Consent Mode v2 has a direct impact on Google Ads performance:
Conversion Attribution
With v2, Google Ads can properly attribute conversions even when users reject cookies, because Google can model conversions based on consent signals. Without v2, conversions for users who reject cookies are lost.
Campaign Optimization
Google's algorithms need conversion data to optimize. With v2, they receive more complete data (including modeled conversions), leading to better optimization. Without v2, optimization degrades because data is incomplete.
Retargeting
Remarketing lists require proper consent signals. With v2, audiences build correctly. Without v2, audiences stay empty or incomplete.
For a deeper dive into how consent affects Google Ads, see does Consent Mode affect Google Ads optimization.
Next Steps: Verify Your Setup
Don't guess whether you're using legacy or v2. Run a diagnostic scan to verify:
- Which Consent Mode version you're using
- If Consent Mode is configured correctly
- If consent updates fire when users accept
- If conversion tracking works with your Consent Mode setup
Check Your Consent Mode Version
Get an automated report that identifies whether you're using legacy or v2, checks configuration, and identifies any issues preventing proper conversion modeling.
Run Free Scan →See a sample report: View sample report →
Related guides:
Part of the Google Ads conversion tracking series:
← Back to: Why Google Ads Conversions Break