what it is and how to integrate it into your site?
Required for EU/UK traffic since March 2024. 5 consent signals, anonymous modeling, and GA4 + Google Ads integration. cerez.io automatic activation with; no manual coding needed.
Regulations and standards covered with GCM v2
The badges above are supported standards. Customer-related examples are clearly marked as example on the page.
Google Consent Mode v2, what does it do?
Google cookies are not loaded before the user gives consent; once they do, the correct signals are updated automatically. Without consent, Google ML models step in to estimate conversions.
As soon as the page loads, all signals go out as "denied".
Under the ePrivacy Directive, no Google cookie should be loaded before the banner is shown. By default, GCM v2 denies all signals and waits for the banner response via the wait_for_update parameter. When the user makes a choice, the update signal carries the correct values.
- GA4 and Google Ads cookies are not loaded before the banner appears
- The update signal is sent within milliseconds after consent
- cerez.io The SDK manages this flow automatically
Data from users who do not consent is estimated, not lost.
A key advantage of GCM v2: conversions from users who do not consent are included in reports as "Modeled Conversions" by Google ML models. This reduces the ad data gap and helps Smart Bidding and Target ROAS strategies run more reliably.
- The ad data gap is closed with Modeled Conversions
- Smart Bidding, Target ROAS, and Customer Match keep working
- GDPR and KVKK compliant; no personal data is processed, only statistical estimation
Each signal controls a different Google product .
GCM v2 (November 2023) added two new signals to v1: ad_user_data and ad_personalization. Without these two signals, enhanced conversion tracking and dynamic remarketing do not work.
ad_storage
from v1
Ad measurement cookies. Required for Google Ads conversion tracking and basic remarketing campaigns. When denied, your Google Ads campaigns fly blind.
ad_user_data
Sending user data to Google. Required for enhanced conversion tracking (Enhanced Conversions) and Customer Match. When denied, email/phone matching does not work.
ad_personalization
Personalized advertising. Required for dynamic remarketing, RLSA (Remarketing Lists for Search Ads), and audience targeting. When denied, all of these targeting methods stay off.
analytics_storage
from v1
GA4 and other analytics cookies. When denied, GA4 session, page view, and conversion data are not collected; reports look incomplete.
functionality_storage
from v1
Cookies for site functionality: language preference, session information, cart contents. They usually stay "granted" as essential because these cookies are required for the site to work.
Without GCM v2, Google Ads campaigns fly blind.
Required for EU/UK traffic since March 2024. Sites without integration see a warning message in Google Ads, loss of conversion data, and a drop in ad performance.
Without GCM v2
Google Ads warning and performance loss.
- The "Consent banner required" warning appears across all EU/UK campaigns
- Conversion data is missing; Smart Bidding strategies break down
- Dynamic Remarketing, Customer Match, and RLSA do not work
- Personalized ads cannot be shown to EU/UK users
"If you see a warning in your Google Ads account, GCM v2 integration is probably missing."
GCM v2 + cerez.io with
The warning clears and ad data is unified.
- The Google Ads warning clears within 24-48 hours
- The ad gap is closed with Modeled Conversions
- Smart Bidding and Target ROAS run reliably again
- KVKK and GDPR compliant; consent logs are stored with timestamps
To be clear: GCM v2 solves the ad data gap, not the personal data question. A consent banner is also required for KVKK/GDPR compliance.
GCM v2 by hand you do not need to code .
Just enter your GA4 Measurement ID or GTM Container ID. cerez.io The SDK manages the entire flow: sending default signals, obtaining consent, and triggering the update signal.
Google Consent Mode v2 · all signals
cerez.io Managed by the SDK
No manual coding neededcerez.io manages GCM v2 signals automatically; for KVKK and GDPR compliance you also need to display a valid consent banner. GCM v2 alone is not a legal compliance document.
Default denied and update flow.
cerez.io The SDK manages this code automatically. It is shared for reference for those who want to use it manually. All signals are updated dynamically based on the actual consent choice.
- wait_for_update parameterSets how long Google waits until the banner opens (milliseconds).
- Granular consentUsers can make a separate choice for each category; the update signal is sent accordingly.
- cerez.io zero code withJust enter your GA4 ID or GTM ID; the SDK manages the entire flow automatically.
// 1. SAYFA YÜKLENDİĞİNDE - Default denied
gtag('consent', 'default', {
ad_storage: 'denied',
ad_user_data: 'denied', // YENİ v2
ad_personalization: 'denied', // YENİ v2
analytics_storage: 'denied',
functionality_storage: 'granted',
wait_for_update: 500
});
// 2. KULLANICI KABUL ETTİĞİNDE - Update
gtag('consent', 'update', {
ad_storage: 'granted',
ad_user_data: 'granted',
ad_personalization: 'granted',
analytics_storage: 'granted'
});GCM v2 and IAB TCF v2.3 conceptual mapping table.
They are separate systems. IAB TCF v2.3 certification cerez.io is targeted for Q3 2026 at. The table below shows only a conceptual mapping; automatic mapping is not available yet.
| GCM v2 Signal | IAB TCF Purpose (Conceptual) | Description | cerez.io Status |
|---|---|---|---|
ad_storage |
Purpose 1 (consent) | Advertising cookie storage | GCM v2 active |
ad_user_data |
Purpose 7 (conceptual) | Sending user data to Google | GCM v2 active |
ad_personalization |
Purpose 3+4 (conceptual) | Personalized advertising | GCM v2 active |
analytics_storage |
Purpose 8 (conceptual) | Analytics cookies | GCM v2 active |
functionality_storage |
Technical requirement | Session, language, cart | GCM v2 active |
| IAB TCF v2.3 automatic mapping cerez.io is targeted for Q3 2026 at. The purpose mappings above serve as a conceptual reference. | |||
Your questions about GCM v2
What is Google Consent Mode v2?
What is the difference between GCM v2 and v1?
ad_user_data (sending user data for enhanced conversions and Customer Match) and ad_personalization (dynamic remarketing, RLSA, audience targeting). v1 had only ad_storage, analytics_storage, and functionality_storage. v2 is far more granular on the advertising side and strengthens GDPR compliance.Is GCM v2 required for Turkey?
Does Google Ads work without GCM v2?
What does default "denied" mean?
wait_for_update parameter; when the user accepts, a "granted" update signal is sent. cerez.io The SDK manages this flow automatically.How is GCM v2 related to IAB TCF v2.3?
How do I test GCM v2?
dataLayer object in the browser console: the "consent" event and its status should be visible.cerez.io How does GCM v2 integration work?
ad_storage, ad_user_data, ad_personalization, analytics_storage). Just enter your GA4 Measurement ID or GTM Container ID; no manual coding is needed. It is included in all tiers, starting from the free plan.Resolve your Google Ads warning today.
GCM v2 activation for GA4 + Google Ads + Tag Manager. 5 steps, 15 minutes, start for free. No credit card required.