Understanding Google Consent Mode v2: A Complete Guide for Website Owners
Learn what Google Consent Mode v2 is, why it's required for EU compliance, how to implement it, and how it affects your Google Analytics and Ads tracking.
Since March 2024, Google requires websites that use Google Analytics and Google Ads and serve users in the EEA to implement Consent Mode v2 — or risk losing measurement and remarketing capabilities. If you haven't implemented it yet and you have European visitors, your data is already being affected.
TL;DR:
- Consent Mode v2 tells Google's tags whether a user consented, so tags adjust behavior instead of firing blindly.
- Two new signals were added in v2:
ad_user_dataandad_personalization, on top of the existingad_storageandanalytics_storage. - Set all signals to
deniedby default, thenupdatetograntedonly after the user accepts — and make sure defaults load before any Google tag. - Choose basic or advanced mode depending on whether you need any pre-consent signal at all.
What is Google Consent Mode v2?
Consent Mode v2 is Google's framework for respecting user privacy choices while still collecting meaningful analytics data. It communicates user consent choices to Google's tags, which then adjust their behavior accordingly.
What Changed in v2
Consent Mode v2 adds two new consent signals:
| Signal | Purpose | Default |
|--------|---------|---------|
| ad_storage | Enable/disable ad storage | denied |
| analytics_storage | Enable/disable analytics | denied |
| ad_user_data (NEW) | Consent for user data to ads | denied |
| ad_personalization (NEW) | Consent for personalized ads | denied |
Why It Matters
Without Consent Mode v2:
- Google Ads conversion tracking may stop working
- GA4 measurement becomes limited
- Remarketing audiences shrink significantly
- EU traffic data is lost
How to Implement Consent Mode v2
Step 1: Add Consent Default Script
Place this BEFORE any Google tags in your <head>:
<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag('consent', 'default', {
'ad_storage': 'denied',
'analytics_storage': 'denied',
'ad_user_data': 'denied',
'ad_personalization': 'denied',
});
</script>
Step 2: Add Cookie Consent Banner
Implement a cookie consent banner that:
- Shows on first visit
- Allows users to accept/reject categories
- Updates consent signals based on choice
Step 3: Update Consent on User Choice
When user accepts cookies:
gtag('consent', 'update', {
'ad_storage': 'granted',
'analytics_storage': 'granted',
'ad_user_data': 'granted',
'ad_personalization': 'granted'
});
Step 4: Implement via GTM (Recommended)
Use Google Tag Manager's Consent Overview to set consent requirements per tag.
Basic vs Advanced Consent Mode
Google offers two implementation modes, and picking the wrong one causes either data loss or compliance risk:
| Aspect | Basic mode | Advanced mode | |--------|-----------|---------------| | When tags load | Only after consent granted | Load immediately, adjust behavior by consent | | Pre-consent data | None at all | Anonymous "cookieless pings" sent | | Behavioral modeling | Not available | Available (fills gaps with ML) | | Best for | Strict interpretations, simpler setups | Maximizing measurement while compliant |
Advanced mode sends cookieless, anonymized pings before consent, which Google uses to model the behavior of users who decline — recovering much of the lost data. Basic mode blocks tags entirely until consent, which is simpler and more conservative but loses all pre-consent signal. Most businesses that rely on ad measurement choose advanced mode; privacy-strict organizations may prefer basic. Confirm the right choice with your legal counsel, not just your marketer.
You Still Need a CMP
Consent Mode is not a cookie banner. It's the signaling layer. You still need a Consent Management Platform (CMP) to show the banner and capture the choice. For Google Ads remarketing in the EEA, Google requires a CMP that is Google-certified and integrates the IAB TCF or uses the consent API directly. A visually pretty banner that doesn't actually pass signals to gtag('consent', 'update', ...) is worse than useless — it looks compliant while collecting data illegally.
Behavioral Modeling
Consent Mode v2 enables behavioral modeling in GA4 — Google uses machine learning to fill gaps in data from users who don't consent.
Requirements for modeling:
- Consent Mode implemented correctly
- At least 1,000 page views per day
- At least 7 days of data
- GA4 connected to Google signals
Implementation Checklist
Use this checklist before publishing Consent Mode v2 on a production website:
- Consent default is set before Google Analytics, Google Ads, or GTM tags load.
ad_storage,analytics_storage,ad_user_data, andad_personalizationare included.- Cookie banner has clear accept, reject, and settings options.
- User choice is stored and respected on the next visit.
- Consent update fires when the user changes preference.
- GA4 DebugView confirms events are still sent with the correct consent state.
- Google Tag Manager Consent Overview shows consent requirements per tag.
- Privacy Policy explains cookies, analytics, ads, and third-party services.
For websites that plan to use Google AdSense, the privacy page should also mention advertising cookies and third-party ad partners. This improves transparency and reduces policy risk.
Common Mistakes
The most common implementation mistake is loading Google tags before consent defaults are set. If tags fire first, data can be collected before the user has a chance to choose. Another common mistake is showing a cookie banner visually but not actually updating the Google consent signals.
Other mistakes:
- Only implementing old Consent Mode fields and missing the v2 fields.
- Using a cookie banner that has no reject option.
- Forgetting to update the Privacy Policy.
- Not testing EU/EEA behavior.
- Tracking ad conversions without checking consent requirements.
How to Test Your Implementation
Never assume it works — verify it. Three practical checks:
- Google Tag Assistant / GTM Preview. Load your site, and before accepting cookies, confirm consent state shows all
denied. Accept, and confirm theupdatefires togranted. - Browser DevTools → Network tab. Filter for
collect(GA4) orgoogle-analytics. Pre-consent, requests should either not fire (basic) or fire withgcs=G100-style denied parameters (advanced). Post-consent,gcsshould reflect granted. - GA4 DebugView. Confirm events still arrive with the correct consent state, and that modeled conversions appear in Ads after a few days of traffic.
Test specifically with an EEA context (use a VPN or GTM region override) because that's where the rules bite. A setup that looks fine from Indonesia may behave differently for a German visitor.
Region-Specific Configuration
You don't have to treat every visitor the same. Using GTM or your CMP, you can set defaults per region:
- EEA + UK: all signals
deniedby default; require explicit opt-in. - Other regions (e.g. Indonesia): many sites set defaults to
granted, subject to local law such as Indonesia's UU PDP.
This maximizes data where legally permitted while staying strict where required. Configure region defaults with gtag('consent', 'default', { region: ['ES','DE',...], ... }) or your CMP's geo rules.
Why This Matters for SEO and Ads
Consent Mode does not directly improve ranking, but it protects measurement quality. Without reliable analytics, you cannot know which SEO pages, tools, articles, or service pages generate leads. For service websites, this affects budget decisions for SEO, Google Ads, and content marketing.
If you need a clean analytics setup, see Complete Guide to Google Tag Manager, Google Analytics untuk Bisnis Bali, and Jasa SEO Maintenance Bali.
FAQ
Is Consent Mode v2 required?
Yes if you use Google Analytics or Google Ads and have visitors from the EU/EEA. Google has made it mandatory for continued measurement.
Does it affect non-EU traffic?
Consent signals apply globally, but the legal requirement is primarily for EU/EEA visitors. Many sites set default to "granted" for non-EU visitors.
Can I use a free cookie banner?
Yes. Options include:
- Cookiebot (free tier available)
- Osano (free tier)
- Custom implementation
What if I don't implement it?
Your Google Ads conversions may stop tracking, and GA4 data for EU visitors will be significantly reduced. Remarketing audiences built from EEA traffic will also shrink or stop refreshing.
Does Consent Mode v2 apply to my Bali business with mostly local traffic?
The legal trigger is serving users in the EEA/UK. If your villa, hotel, or agency gets European visitors — very common in Bali tourism — then yes, it applies to that traffic. For purely domestic Indonesian audiences, Consent Mode v2 isn't legally required by Google's EEA rule, but Indonesia's UU PDP still governs how you handle personal data. Implementing it correctly is the safe default for any tourism-facing site.
Basic or advanced mode — which should I pick?
If your priority is recovering measurement data and you're comfortable sending anonymized cookieless pings before consent, choose advanced. If you or your legal team prefer that no signal at all leaves the browser before consent, choose basic. Advanced is the more common choice for businesses that spend on Google Ads because behavioral modeling meaningfully restores conversion data.
Do I need a paid CMP?
Not necessarily. Free tiers (Cookiebot, Osano) work for small sites, and a custom banner is fine if it correctly calls gtag('consent', 'update', ...). For EEA Google Ads remarketing, the key requirement is that your CMP is Google-certified — check that before choosing, regardless of price.
Related Articles:
Implement Consent Mode v2 correctly with help from Jayax.dev.
