Consent Mode v2: Practical Setup Guide (Don't Lose Data)
Basic vs Advanced Consent Mode, GTM configuration, CMP integration, behavioral modeling. Common mistakes and how to avoid them.
Consent Mode v2: What Are We Actually Talking About?
Consent Mode is a Google protocol that adapts tag behavior based on user consent. Version 2, mandatory since March 2024 for Google Ads advertisers in the EEA, adds two new signals: ad_user_data and ad_personalization. Without these signals, your remarketing audiences and Google Ads conversions progressively lose precision.
In practical terms, Consent Mode informs Google tags of the consent state. When a user refuses cookies, instead of sending nothing at all, Google receives anonymized pings that feed its machine learning models to fill the gaps in your data.
Basic vs Advanced: What Is the Difference?
This is the most misunderstood distinction. In Basic mode, Google tags simply do not fire until the user has accepted. It is binary: consent or silence. You stay compliant, but you lose all data on visitors who refuse.
In Advanced mode, tags always fire, but send cookieless pings when consent is denied. These pings contain no personal data — no cookie, no identifier. They do, however, allow Google to estimate, through modeling, the likely behavior of non-consenting users based on patterns observed among those who accepted.
Advanced mode offers the best compromise between compliance and data quality. The CNIL (French data protection authority) has not, to date, raised a formal objection to its use, provided that your CMP is properly configured and that cookieless pings do not constitute personal data processing in your context.
GTM Configuration: Key Steps
Setup involves your CMP (Axeptio, Didomi, Cookiebot, OneTrust) and Google Tag Manager. Your CMP must push consent signals into the data layer in the format expected by GTM. The four parameters to manage are: analytics_storage, ad_storage, ad_user_data, and ad_personalization.
In GTM, verify that your default consent settings are configured in the container settings (Consent Overview section). Each tag must have its consent requirements set. GA4 tags require analytics_storage, while Google Ads tags require all four parameters.
Systematically test with GTM preview mode and GA4 real-time reports. Verify that events come through when you accept, and that only anonymized pings are sent when you refuse.
Common Mistakes
The most common error: configuring Consent Mode in GTM but forgetting to update the CMP. Both must communicate. If your CMP does not push the correct signals, GTM cannot adapt tag behavior.
Second trap: not testing the refusal path. Many sites verify that tracking works after acceptance but never check what happens when the user refuses or ignores the banner. Yet this scenario determines whether Consent Mode is actually working.
Third error: confusing Consent Mode with tag blocking. Consent Mode does not replace blocking. Your CMP must still prevent non-essential tags from firing before consent (or, in Advanced mode, ensure they do not set cookies).
Impact on Your Data and Campaigns
With a properly configured Advanced Consent Mode, Google claims to recover up to 65% of conversions normally lost through modeling. This number varies depending on your consent rate and traffic volume. The more traffic your site has, the more accurate the model becomes.
If you are not sure your Consent Mode is correctly implemented, a tracking audit can quickly verify it and identify the corrections needed.