Google Consent Mode v2 is the mechanism that lets Google Ads and Google Analytics respect a visitor’s cookie choice while still sending Google a minimal, cookieless signal that something happened. Since March 2024, advertisers who serve ads to people in the European Economic Area (EEA), the UK and Switzerland must pass two additional consent signals, ad_user_data and ad_personalization, or they lose access to audience features and the measurement of those users in Google Ads. If you run ads in Germany, the Netherlands, France, Spain or Italy and your banner is not wired to Consent Mode v2, you are almost certainly underreporting conversions and bidding on incomplete data.
The short answer to “do I need it?” is yes if any part of your traffic comes from Europe, even if your business is based in the US. The short answer to “which version?” is advanced mode wherever your legal team is comfortable with it, because it is the only version that recovers modeled conversions from users who decline. The rest of this guide covers what each mode does, how to implement it with a consent management platform (CMP) and Google Tag Manager, and how to verify that Google is actually receiving the signals.
This is a technical topic with legal edges. We are a paid media agency, not a law firm, so treat the compliance points below as a starting checklist to confirm with your own advisor.
What Consent Mode v2 actually does
Consent Mode is a set of parameters your website sends to Google tags that describe what the visitor agreed to. Version 1 had two: analytics_storage and ad_storage. Version 2 adds two more that map directly to the Digital Markets Act obligations Google took on in 2024:
- ad_user_data: whether user data may be sent to Google for advertising purposes.
- ad_personalization: whether that data may be used for personalized advertising, which covers remarketing lists, Customer Match and similar audiences.
When a visitor declines, Google tags behave differently depending on which mode you chose. Google’s official documentation on Consent Mode in Google Ads describes both, and the developer guide on consent has the exact parameter names and default states.
Basic mode vs advanced mode
This is the decision that matters most, and it is the one most agencies gloss over.
| Aspect | Basic Consent Mode | Advanced Consent Mode |
|---|---|---|
| Tags before consent | Blocked entirely until the user accepts | Load immediately, but send cookieless pings only |
| Data from users who decline | Nothing; Google only sees that consent was denied | Anonymous, cookieless pings with no identifiers |
| Conversion modeling | General modeling based on consent-rate observation only | Observation-based modeling using the cookieless pings; recovers a share of lost conversions |
| Audience building for EEA users | Only consenting users | Only consenting users (same as basic) |
| Legal comfort | Highest; nothing fires without consent | Requires your DPO to be comfortable with cookieless pings |
In our experience most US-based advertisers with EU traffic default to basic mode because it is simpler to explain. The cost is real: with typical European consent rates somewhere between 50% and 80% depending on banner design and market, basic mode means a large slice of your conversions simply disappears from Google Ads, and Smart Bidding optimizes toward the people who click “accept”, not toward everyone who buys. Advanced mode lets Google model the missing portion. Google documents eligibility thresholds for modeling (a minimum volume of ad clicks per country and domain group over a trailing window), so very small accounts may not see modeled conversions even with advanced mode, but the setup is still correct and starts working as volume grows.
How to set up Consent Mode v2 step by step
- Pick a Google-certified CMP. Cookiebot, OneTrust, Usercentrics, CookieYes, Didomi and Complianz all support v2 natively. A certified CMP sets the four consent parameters for you; a home-made banner means you write the
gtag('consent', ...)calls yourself and are responsible for keeping them correct. - Set default consent states before any Google tag loads. The
consent defaultcommand must fire first on every page. For EEA, UK and Swiss visitors defaults should bedeniedfor all four parameters; many CMPs let you set region-specific defaults so US visitors keepgrantedunless you have a reason to change that. - Update consent after the user chooses. The CMP fires
consent updatewith the user’s selection. In Google Tag Manager, use the CMP’s template or the built-in consent settings on each tag and check the “Consent Overview” view to see which tags require which signals. - Choose basic or advanced. In GTM, advanced mode is the default behavior of Google tags once consent defaults are set. Basic mode means adding consent-initialization triggers so the tags do not fire at all until consent is granted.
- Verify in Google Ads. Go to Goals, then Conversions, then Diagnostics (or the Consent Mode section under Data Manager in newer accounts). Google reports whether consent signals are being received and whether they are “active” for EEA traffic. Also check Tag Assistant: each hit should show the consent state in the request details.
- Verify in GA4. Under Admin, then Data Streams, the stream details show the consent settings status; GA4 Reports will show “(modeled)” data once thresholds are met.
- Re-test after any site change. New theme, new checkout, new CMP version: each one can silently break the default command order. Put a quarterly check on the calendar.
Common Consent Mode v2 mistakes that cost conversions
Google tags fire before the consent default
The single most frequent failure. If gtag.js or GTM loads before consent default, the first pageview hits Google with full cookies regardless of what the visitor later chooses. Google Ads will show consent signals as “missing” or “inconsistent” and you may also be exposed legally. Fix: place the default command in the <head> above the GTM snippet, or use your CMP’s “load before GTM” option.
Only two parameters are set
Older banners still set ad_storage and analytics_storage only. Without ad_user_data and ad_personalization, Google Ads cannot use EEA users for remarketing or Customer Match at all, and the Google Ads diagnostics page will flag it.
Server-side tagging without forwarding consent
If you moved to server-side GTM, the consent state must travel with the event to the server container and the server tags must respect it. Many migrations break this without anyone noticing because conversions still appear to be counted.
Treating every visitor as EEA (or none)
Applying “denied” defaults worldwide throws away perfectly usable US and Canadian data. Applying “granted” defaults worldwide violates the whole point. Use region-specific defaults based on the region parameter.
Conversion tracking that was already broken
Consent Mode cannot model what was never tracked. If your purchase tag double-fires, has no value, or sits on a thank-you page that some payment flows skip, fix that first. Our walkthrough on setting up Google Ads conversion tracking with GA4 covers the plumbing, and if campaigns show clicks but no conversions, start with why Google Ads is not converting before touching consent settings.
What changes in your Google Ads reporting
Once advanced mode is live and modeling kicks in, you will typically see conversion counts rise for EEA campaigns, often modestly rather than dramatically, and conversion values that are modeled rather than observed. Smart Bidding uses these modeled conversions, which usually makes tCPA and tROAS bidding steadier in European markets. If you compare Google Ads to your Shopify or WooCommerce back end, expect the gap to narrow but not close: attribution windows and cross-device logic still differ.
For US advertisers, the practical implication is that one site, one CMP and one GTM container can serve all markets if region defaults are handled correctly. For European advertisers, the implication is that an un-audited setup may be feeding Smart Bidding a biased sample. A Google Ads audit is the fastest way to find out whether consent signals are being received and whether your conversion actions are counting what you think they count, and ongoing Google Ads management keeps the setup verified after every site release.
FAQ
Is Consent Mode v2 mandatory?
If you want to use Google Ads measurement and audience features for users in the EEA, UK or Switzerland, Google requires the v2 signals. It is not a legal requirement in itself; your legal obligation comes from GDPR and the ePrivacy rules, and Consent Mode is Google’s way of letting you honor them while keeping some data.
Does Consent Mode v2 replace a cookie banner?
No. It is the bridge between your banner and Google’s tags. You still need a compliant CMP that collects consent; Consent Mode just tells Google what the visitor chose.
Do US-only advertisers need it?
If you have no EEA, UK or Swiss traffic and do not plan to, the impact is minimal. Most “US-only” stores still get some European visitors and some US states now have their own consent laws, so implementing it correctly with region defaults is cheap insurance.
Which mode should I choose, basic or advanced?
Advanced recovers more data through modeling and is what we recommend when your privacy counsel accepts cookieless pings. Basic is the conservative choice and is fine for small accounts that would not meet modeling thresholds anyway.
How can I tell if it is working?
Google Ads shows consent signal status under conversion diagnostics; Tag Assistant shows the consent state on each hit; GA4 shows a consent settings status on each data stream. All three should agree.
Does Consent Mode v2 affect Performance Max and Shopping?
Yes. Both rely on conversion data and audience signals, so missing consent signals degrade them the same way they degrade Search. If you are choosing between the two, our comparison of Google Shopping vs Performance Max explains which depends more on audience data.
Need help with your campaigns?
If you are not sure whether your consent setup is leaking conversions, we can check it as part of a Google Ads audit and fix the tag order, parameters and conversion actions in one pass. For a quick first look, request a free mini audit or book a 30-minute call and we will walk through your account together.