Consent mode v2 and AdSense: two consent signals, one site
Key takeaways
- Google consent mode is a tag-level API for the Google tag, Google Analytics, Google Ads, Floodlight and Conversion Linker; AdSense is not in Google's list of tags with built-in consent checks.
- For EEA, UK and Swiss traffic, AdSense reads the IAB TCF string from a certified CMP, not consent mode signals.
- The "v2" version added two consent types, ad_user_data and ad_personalization, to the original ad_storage and analytics_storage.
- Google's tags can derive consent mode from a TCF string when you set TCData.enableAdvertiserConsentMode to true in the CMP or window['gtag_enable_tcf_support'] to true on the page.
- Google's European regulations message can also send consent mode signals for EEA, UK and Swiss users, but you must set defaults for everyone else.

Consent mode v2 is Google’s API for telling its measurement and advertiser tags (Google Analytics, Google Ads, Floodlight) what a user agreed to. AdSense does not rely on it: for EEA, UK and Swiss visitors, AdSense reads the IAB TCF string from a Google-certified CMP. On a site that runs both AdSense and Analytics, you need both signals, and they must say the same thing.
This guide is based on Google’s developer documentation and AdSense help as of November 2026. It describes how the tools behave, not what the law requires, and is not legal advice.
What is consent mode, and what changed in v2?
Google’s consent mode overview describes it as a way to “control how Google tags and SDKs behave based on users’ consent choices”. It defines seven consent types:
| Consent type | What it controls |
|---|---|
ad_storage |
Advertising cookies or device identifiers |
ad_user_data |
Sending user data to Google for online advertising |
ad_personalization |
Personalized advertising (remarketing) |
analytics_storage |
Analytics cookies |
functionality_storage |
Storage for site features such as language |
personalization_storage |
Storage for content personalization |
security_storage |
Storage for security and fraud prevention |
“Consent mode v2” is the common name for the version that added ad_user_data and ad_personalization. Google’s TCF integration guide notes that its TCF mapping was updated in November 2023 to cover these two types. The EU user consent policy help page says advertisers with EEA traffic who use Google tags “need to pass through end-user consent choices to Google (e.g. via consent mode or TCF)”.
Why doesn’t AdSense use consent mode?
The overview lists the products whose tags contain built-in consent checks: the Google tag, Google Analytics, Google Ads, Floodlight and Conversion Linker. AdSense is not on the list.
On the publisher side, Google’s TCF integration article for AdSense says that if you run an IAB-registered TCF CMP, “AdSense automatically consumes the TC string from the CMP”. For EEA, UK and Swiss traffic, Google also requires that CMP to be Google-certified for personalized ads.
| Signal | Who reads it | What AdSense does with it |
|---|---|---|
| TC string from a certified CMP | AdSense, Ad Manager, AdMob, many ad partners | Chooses personalized, non-personalized or limited ads |
Consent mode states (gtag('consent', ...)) |
Google Analytics, Google Ads, Floodlight, Conversion Linker | Nothing documented for AdSense |
| NPA or privacy treatment flag in ad code | AdSense | Downgrades the request; see limited and non-personalized ads |
So a banner that only speaks consent mode leaves AdSense without a TCF signal in Europe. Google reports such requests as error 10.1 and attempts limited ads.
How do I keep both signals in sync?
There are three common setups:
| Setup | TCF string for AdSense | Consent mode for Analytics and Ads | Effort |
|---|---|---|---|
| Google’s European regulations message with Consent Mode enabled | Yes | Yes, for EEA, UK and Swiss users | Low |
| Certified commercial CMP with consent mode integration | Yes | Yes, via the CMP’s own integration | Medium |
| TCF CMP plus Google’s TCF-to-consent-mode mapping | Yes | Derived from the TC string | Medium |
Option 1: Google’s own message
Google’s European regulations message has a Consent Mode setting. When it is on, Google’s CMP “interprets” users’ choices for ad storage, ad personalization, ad user data and analytics storage. Google notes three limits: it applies to web and apps but not AMP; it only updates consent for users who see the European message, so you must set defaults for other regions; and enabling it while another CMP also sends consent mode signals could cause conflicts. Setup is covered in the Privacy & messaging guide.
Option 2: Google’s TCF mapping
Google tags can read the TC string themselves. The TCF guide says to enable it either by having your CMP set TCData.enableAdvertiserConsentMode to true, or by adding window['gtag_enable_tcf_support'] = true before the Google tag. The mapping it describes:
| TCF Purpose denied | Consent mode effect |
|---|---|
| Purpose 1 (store and/or access information on a device) | ad_storage and ad_user_data denied |
| Purpose 3 or 4 (personalized ads profile, selection) | ad_personalization denied |
| Purpose 7 (measure ad performance) | ad_user_data denied, Google signals disabled in Analytics (web) |
| Purpose 9 or 10 | Google signals disabled |
If the CMP does not respond within 500 milliseconds, or reports an “error”, “stub” or “loading” status, the tag proceeds with default consent settings. The mapping does not set analytics_storage: Google’s guide says that to control Google Analytics cookies you integrate with consent mode directly.
Option 3: your own code
If your CMP gives you callbacks, set defaults and updates yourself. Google’s setup guide shows the pattern:
<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag('consent', 'default', {
'ad_storage': 'denied',
'ad_user_data': 'denied',
'ad_personalization': 'denied',
'analytics_storage': 'denied',
'wait_for_update': 500
});
</script>
Run it before the Google tag, then call gtag('consent', 'update', {...}) when the user decides. The guide recommends scoping defaults to the regions where banners are required, using the region parameter with ISO 3166-2 codes.
Scoping defaults by region
The setup guide explains that you can “set defaults for specific regions, and then set a different default for all other regions”. A default command without a region parameter applies to every visitor not covered by a region-specific one, and when a region and a subregion both have defaults, “the one with a more specific region will take effect”. Google’s example sets analytics_storage to denied for Spain (ES) and Alaska (US-AK) only, then ad_storage to denied for everyone.
For an AdSense site with European traffic, that usually means denied defaults for EEA countries, the UK (GB) and Switzerland (CH), and a separate default for the rest of the world that matches your legal position there.
What happens in each region without consent?
| Region | What AdSense needs | Consent mode for Google Analytics | Without consent |
|---|---|---|---|
| EEA, UK, Switzerland | TC string from a certified CMP | Denied defaults, update on choice | AdSense: non-personalized or limited ads; Analytics: no cookies, cookieless pings in advanced mode |
| US states with privacy laws | Opt-out signals, restricted data processing | Defaults usually granted, per your legal analysis | AdSense: restricted data processing after opt-out |
| Other regions | No consent signal required by Google | Defaults set by you | AdSense serves normally |
The US row is covered in more detail in the US state privacy laws guide.
Two optional settings
The setup guide lists two advanced features that matter when consent is denied:
ads_data_redaction. Withgtag('set', 'ads_data_redaction', true)andad_storagedenied, “ad click identifiers sent in network requests by Google Ads and Floodlight tags will be redacted”. It has no effect whenad_storageis granted.url_passthrough. Withgtag('set', 'url_passthrough', true), parameters such asgclid,dclid,gclsrcand_glmay be appended to internal links so click information survives without cookies.
Neither setting affects AdSense ad serving. They concern advertiser tags that may also run on your site, such as Google Ads conversion tracking for your own campaigns.
Basic or advanced consent mode?
| Basic | Advanced | |
|---|---|---|
| Google tags before consent | Not loaded | Loaded, defaults denied |
| Data sent if user refuses | Nothing, not even the consent state | Consent state and cookieless pings |
| Modeling in Google Ads | General model | Advertiser-specific model |
Advanced mode sends cookieless pings before consent. Whether that is acceptable where you operate is a legal question; some publishers choose basic mode to keep the banner the single gate.
Common mistakes
- Using a consent-mode-only banner in Europe. It satisfies Analytics, not AdSense.
- Two CMPs sending consent mode. Google warns this “could result in conflicts”.
- Defaults only for Europe. Google’s message updates consent only for EEA, UK and Swiss users; other regions need explicit defaults.
- Placing the default command after the Google tag. The first hits go out with no consent state.
- Expecting consent mode to block AdSense cookies. It has no documented effect on AdSense; control AdSense through the TC string and the open-source banner limits apply if your banner is not a TCF CMP.
Frequently asked questions
Do I need consent mode v2 to show AdSense ads in Europe?
Not for AdSense itself. For EEA, UK and Swiss traffic, AdSense consumes the TCF string from a Google-certified CMP. Consent mode matters if the same site also runs Google Analytics, Google Ads conversion tags or other Google tags, which do read consent mode states. Most sites with AdSense and Analytics end up needing both signals to agree.
Can a cookie banner that only supports consent mode serve personalized AdSense ads in the EEA?
No. Google requires a Google-certified CMP integrated with the IAB TCF for personalized ads to EEA, UK and Swiss users. A banner that only calls gtag('consent', 'update', ...) produces no TC string, so AdSense treats those requests as having no TCF signal and attempts limited ads.
What is the difference between basic and advanced consent mode?
In basic mode, Google tags do not load until the user interacts with the banner, and nothing is sent to Google if the user refuses. In advanced mode, tags load with denied defaults and send cookieless pings, which Google uses for advertiser-specific modeling. Advanced mode sends more data before consent, so check whether that fits your legal position.
What does wait_for_update do?
It tells Google tags to wait a number of milliseconds for the CMP to update consent before sending data. Google's setup guide uses 500 milliseconds in its example. It helps when the CMP loads asynchronously after the Google tag and would otherwise miss the first hit.
Sources
- Consent mode overview · Google for Developers
- Set up consent mode on websites · Google for Developers
- Implement the Transparency & Consent Framework · Google for Developers
- Publisher integration with the IAB Europe TCF · Google AdSense Help
- About European regulations messages · Google AdSense Help
- Help with the EU user consent policy · Google
Related guides
- IAB TCF v2.3 for publishers: what Google requires, what changed from v2.2, and v2.4
TCF v2.3 is mandatory for TC strings created since March 1, 2026. What changed from v2.2, Google's dates, the purposes AdSense needs, and the v2.4 update.
- AdSense Privacy & messaging: building the European regulations (GDPR) message
Build the GDPR consent message in AdSense Privacy & messaging: every setting, the two- vs three-button layout, testing, troubleshooting and what it cannot do.
- Google's certified CMP requirement: what AdSense publishers need for EEA, UK and Swiss traffic
Since 2024 AdSense needs a Google-certified TCF CMP for personalized ads in the EEA, UK and Switzerland. Dates, what happens without one, how to check yours.
- Open-source cookie banners with AdSense: what they can and cannot do
Klaro, CookieConsent and tarteaucitron.js are solid free banners, but none writes a TCF string or is Google-certified. What that means for AdSense in Europe.
- Personalized, non-personalized and limited ads: the three AdSense serving modes compared
How AdSense picks personalized, non-personalized or limited ads from consent signals, what each mode still collects, the ad code switches and the setting to check.