Google Consent Mode v2, explained simply: it is a way for your consent banner to tell Google's tags what each visitor agreed to, so that Google Analytics, Google Ads and Floodlight tags behave accordingly. Version 2 added two signals, ad_user_data and ad_personalization, on top of the original ad_storage and analytics_storage. Google has required these signals since March 2024 for advertisers who want to keep using measurement, remarketing and personalisation features on European traffic. Consent Mode doesn't collect consent itself and doesn't make your site compliant; your consent management platform does the asking, and Consent Mode passes on the answer.
The bigger decision is between basic and advanced mode, because advanced mode sends some data to Google before a visitor has agreed. Here is how each works and what it means legally.
General information, not legal advice.
The Consent Mode signals
According to Google's developer documentation, the consent types are:
| Signal | Controls | Effect when denied |
|---|---|---|
| ad_storage | Advertising cookies and device identifiers | No new ad cookies written, existing ones not read; IP addresses truncated at collection |
| analytics_storage | Analytics cookies such as visit duration | First-party analytics cookies not read or written |
| ad_user_data | Sending user data to Google for advertising | Personal data collection for ads disabled, including user_id and enhanced conversions |
| ad_personalization | Personalised advertising | Remarketing and personalised ads disabled |
| functionality_storage, personalization_storage, security_storage | Site functions, personalisation and security storage | Used by your own tags as needed |
ad_user_data and ad_personalization in practice
The two v2 signals separate storing cookies from what Google may do with data. A visitor might allow ad measurement cookies but not personalised ads, or neither. Your CMP should map each banner purpose to the right signals. If a visitor rejects advertising, all three ad signals should be denied.
Consent Mode basic vs advanced
| Basic | Advanced | |
|---|---|---|
| When Google tags load | Only after the visitor interacts with the banner and consents | On page load, with consent defaulting to denied |
| Data before consent | None | "Cookieless pings" with consent state and limited technical data |
| If the visitor rejects | Tags never fire | Pings continue without cookies |
| Conversion modelling | General model | Advertiser-specific model, typically more detailed |
| Privacy risk | Lowest | Higher; requires a legal judgement |
Google describes cookieless pings as including browser-supplied headers (timestamp, user agent, referrer) and aggregate, non-identifying data such as whether an ad-click identifier appeared in the URL, the consent state and a random number generated per page load. The pings are network requests, so Google also receives the visitor's IP address in transit.
Consent Mode, GDPR and ePrivacy
Basic mode is straightforward: nothing goes to Google until there's consent, which fits the EU prior-consent rule cleanly.
Advanced mode is the debated one. Google's position is that denied-state pings use no cookies and contain no identifiers. Critics point out that the ePrivacy rules are not only about cookies: the EDPB's Guidelines 2/2023 say tracking pixels and URL-based tracking that cause a device to send information can fall within Article 5(3). On that reading, sending pings to an advertising provider before consent may itself need consent. The GDPR also applies to the IP address and any click identifier involved.
Our practical view for European publishers:
- EU traffic: basic mode is the lower-risk default. Use advanced mode only after a documented assessment, and set ads_data_redaction to true so ad-click identifiers are redacted when ad_storage is denied.
- UK traffic: the new PECR statistical exemption doesn't cover advertising, so the same caution applies to ad pings. Analytics can sometimes be treated differently under the exemption, as covered in our guide on whether Google Analytics is GDPR compliant.
- Adult sites: be more conservative. Pings tied to URLs on adult pages can reveal sensitive interests even without cookies.
Consent Mode is not a banner. It only relays choices. You still need a banner that meets the EU cookie banner requirements, including Reject all on the first layer.
Consent Mode implementation, step by step
- Choose a CMP that supports Consent Mode v2. If you run Google publisher products in the EEA, UK or Switzerland, it must also be Google-certified. See how to choose a consent management platform.
- Decide basic or advanced per region, and record why.
- Set defaults before any Google tag. The default consent command must run before tags load. For EEA and UK visitors, default all four main signals to denied.
- Map banner purposes to signals. Analytics purpose to analytics_storage; advertising purposes to ad_storage, ad_user_data and ad_personalization.
- Send updates on choice. When the visitor accepts or rejects, the CMP sends a consent update. Check that it fires on every page, not just the first.
- Configure tags in Google Tag Manager to respect built-in consent checks, and add consent requirements to any non-Google tags too (Consent Mode doesn't control them).
- Verify. Use Tag Assistant or your browser's network panel. With everything rejected, you should see no ad or analytics cookies, and in basic mode no Google requests at all.
A hypothetical example
An affiliate comparison site running Google Ads for its own acquisition sets basic mode for EU visitors and advanced mode with redaction for the rest of the world. Its EU conversion reporting relies on Google's general model plus its own affiliate network data, which it treats as the source of truth for revenue anyway. It accepts the smaller modelled numbers in exchange for lower legal risk.
Common problems
- Defaults set too late: tags load before the default command and set cookies.
- Granted by default in Europe: some templates default to granted outside a specific country list. Check your region rules.
- Non-Google tags ignored: affiliate pixels and other ad networks still need blocking by the CMP.
- Server-side containers: moving tags to a server doesn't remove the need to respect consent. See server-side tagging for affiliate sites.
What happens if you don't implement it
If you block Google tags with your CMP but send no Consent Mode signals, you stay on the safe side legally, but Google treats European traffic as lacking the consent information it needs. In practice that means:
- Remarketing audiences stop growing from European visitors.
- Conversion measurement for European traffic becomes patchier, and modelling isn't available to fill gaps.
- Features such as enhanced conversions and personalised ads can't use European user data.
For an affiliate publisher that doesn't buy Google Ads, the impact is small: GA4 reporting is the main thing affected. For anyone buying Google traffic to promote offers, implementing Consent Mode properly, even in basic mode, is worth the effort.
Frequently asked questions
Is Google Consent Mode v2 mandatory?
Not by law. Google requires it for advertisers who want to keep using measurement, remarketing and personalisation features for European users. The legal requirement is valid consent, which your banner must collect.
Does advanced Consent Mode comply with GDPR?
It depends on your assessment. Google says denied-state pings are cookieless and non-identifying, but sending data to an ad provider before consent may fall within ePrivacy rules on some readings. Basic mode avoids the question.
Does Consent Mode affect non-Google tags?
No. It only adjusts Google's own tags. Your CMP must block other networks' scripts and pixels until consent.
Next steps
Check your current defaults and region rules in Tag Assistant today. Then decide basic or advanced per region and document it. For tools that support Consent Mode, browse our software and services directory, and see the rest of our GDPR and cookies guides.