- If you run Google Ads or GA4 and get visitors from the European Economic Area, Google's EU user consent policy expects you to pass their consent choices to Google, and Consent Mode v2 is how most stores do it.
- Consent Mode v2 has four core signals: ad_storage, analytics_storage, ad_user_data and ad_personalization. Basic mode blocks Google tags until consent; advanced mode sends cookieless pings so Google can model what it can't observe.
- Set region-specific defaults (denied for EEA, UK and Switzerland visitors), connect your consent banner to update them, and test the full path before trusting your reports.
Does Consent Mode v2 apply to a U.S. store?
It applies to your traffic, not your headquarters. An Ohio store that ships to Germany or the UK and runs Google tags has visitors whose consent choices matter. Two things are in play:
- The law. The EU’s GDPR and ePrivacy rules, and the UK’s equivalents, generally require consent before setting non-essential cookies or similar storage on a visitor’s device. GDPR can apply to businesses outside the EU that offer goods to people in the EU. Whether and how it applies to you depends on your situation, so confirm your obligations with counsel.
- Google’s policy. Google’s EU user consent policy covers end users in the EEA, the UK and Switzerland. Advertisers who measure with Google tags or use audience and personalization features for EEA traffic must pass consent choices to Google, for example through consent mode. Google’s guidance says verified consent signals are expected for EEA traffic. For UK and Swiss traffic it currently does not expect a verified signal, but the policy still covers those users, and consent law applies there too.
Skip it and the cost shows up in measurement: without valid consent signals for EEA users, features such as remarketing audiences, personalized ads and conversion modeling are limited for that traffic.
U.S. visitors are a different case. Several U.S. state privacy laws center on the right to opt out of the “sale” or “sharing” of personal data, and some expect you to honor Global Privacy Control signals. That’s an opt-out model, so your defaults and banner logic should differ by region. Confirm the details with counsel.
What are the four Consent Mode v2 signals?
Your consent management platform (CMP) collects the visitor’s choice; consent mode passes it to Google tags as signals, each “granted” or “denied.”
| Signal | Added in | What it controls | What happens when denied |
|---|---|---|---|
| ad_storage | v1 | Cookies and storage used for advertising, such as ad click identifiers | Ad cookies aren’t read or written |
| analytics_storage | v1 | Cookies and storage used for analytics, such as GA4’s client ID | GA4 doesn’t set or read its cookies |
| ad_user_data | v2 | Whether user data can be sent to Google for advertising purposes | User data isn’t sent for ads, which affects features like enhanced conversions |
| ad_personalization | v2 | Whether data can be used for personalized ads, including remarketing | The visitor isn’t added to remarketing audiences |
Version 1 only covered storage. Version 2 separates “may we store cookies?” from “may we send your data to Google for ads?” and “may we personalize ads with it?” Two optional settings are worth knowing:
- ads_data_redaction: when ad_storage is denied, redacts ad click identifiers in the requests that are still sent.
- url_passthrough: passes ad click information through URL parameters across pages when cookies can’t be used, which can help measurement when consent is denied.
What is the difference between basic and advanced consent mode?
This is the main decision you’ll make.
Basic mode: Google tags are blocked entirely until the visitor accepts. If they decline, nothing is sent to Google. Simple and conservative, but Google sees no data at all from people who decline.
Advanced mode: Google tags load with denied defaults before the visitor chooses. When consent is denied, tags send cookieless pings: no cookies are set or read, but Google receives limited signals that a page view or conversion happened. Google uses these to model conversions and behavior for unconsented users, which feeds reporting and Smart Bidding.
| Basic | Advanced | |
|---|---|---|
| Tags load before choice | No | Yes, with denied defaults |
| Data sent when visitor declines | None | Cookieless pings, no cookies |
| Conversion modeling | More limited | Uses the cookieless pings |
| Setup complexity | Lower | Higher, and the default must fire before any Google tag |
| Legal review | Simpler to explain | Ask counsel whether cookieless pings fit your consent approach |
Advanced mode usually recovers more measurement. Whether sending cookieless pings without consent suits your case is a legal question, not a technical one, so decide with counsel and document it.
How much measurement can you lose? An illustrative example
Take a store with 10,000 monthly sessions from the EEA and UK, 2 percent of which convert, giving 200 real orders. All numbers here are illustrative.
| Scenario | Consent rate | Orders observed directly | Orders Google can model | What Ads and GA4 see |
|---|---|---|---|---|
| No consent mode, tags blocked for decliners | 60% | About 120 | None | About 120, a 40% gap |
| Basic mode | 60% | About 120 | Limited | Close to 120, with limited modeling |
| Advanced mode | 60% | About 120 | Part of the remaining 80 | Closer to 200, if modeling is available for your account |
The point isn’t the exact numbers. Smart Bidding learns from the conversions it sees; if it sees 120 orders when there were 200, it undervalues the campaigns behind them. If your GA4 numbers already disagree with Shopify, our article on the GA4 vs Shopify revenue discrepancy covers the other common causes.
How do you implement Consent Mode v2?
The sequence is the same whether you use gtag.js directly or Google Tag Manager.
1. Set defaults before any Google tag fires
Consent mode needs a default state on every page load, before tags run. Set it by region so EEA, UK and Swiss visitors start with everything denied, while other regions follow your policy for them. A gtag example:
gtag('consent', 'default', {
'ad_storage': 'denied',
'analytics_storage': 'denied',
'ad_user_data': 'denied',
'ad_personalization': 'denied',
'region': ['AT','BE','DE','FR','IE','IT','NL','ES','GB','CH'],
'wait_for_update': 500
});
The region list is shortened here; yours should cover every EEA country plus the UK and Switzerland. The wait_for_update value (in milliseconds) gives the CMP a moment to load and send a stored choice before tags fire.
2. Update consent when the visitor chooses
When the visitor accepts or changes their choice, the CMP sends an update command with the new values. Most CMPs certified under Google’s CMP Partner Program handle this automatically, including the two v2 signals. Check that the banner’s categories map correctly: “marketing” consent typically controls ad_storage, ad_user_data and ad_personalization; “analytics” controls analytics_storage.
For returning visitors, the CMP should read the stored choice and send the update immediately on load.
3. Cover every tag, not only Google’s
Consent mode only adjusts Google tags. Meta, TikTok, Pinterest and other pixels need to be blocked or released by your CMP directly, according to the same choices. Server-side setups also need consent: if you send Meta purchase events through the Conversions API, pass the consent state along and respect it on the server.
How does this work on Shopify, WooCommerce and Magento?
Shopify. Shopify has a built-in customer privacy setting and a Customer Privacy API that apps and pixels can read. Pick a CMP that integrates with that API and supports Google consent mode, so one choice reaches Shopify, your apps and your Google tags. If you run both Shopify’s Google & YouTube app and a GTM container, check that both read the same consent state. Test custom pixels in Shopify’s customer events separately, since they run in their own sandbox.
WooCommerce and Magento / Adobe Commerce. Usually a CMP plugin or extension plus GTM. Check that page caching doesn’t serve one visitor’s banner state to another, that the default fires before any analytics or ads plugin loads its tags, and retest after upgrades.
On any platform, server-side tagging helps you control what leaves your site, but it doesn’t remove the need for consent. Our guide to server-side tagging for Shopify covers when it’s worth adding.
How do you test Consent Mode v2?
Don’t trust a banner because it looks right. Test the full path:
- [ ] Using a VPN or browser location set to an EEA country, load the site in a private window and confirm all four signals start as denied before any interaction.
- [ ] In Google Tag Assistant, check that the default consent command appears before the first Google tag fires.
- [ ] Decline everything. In advanced mode, confirm requests are sent without cookies; in basic mode, confirm no Google requests are sent.
- [ ] Accept everything. Confirm an update command sets all four signals to granted, and that GA4 and Google Ads cookies now appear.
- [ ] Accept analytics only. Confirm analytics_storage is granted and the three ad signals stay denied.
- [ ] Reload and change pages. Confirm the stored choice applies immediately, and that U.S. visits follow your U.S. settings.
- [ ] Check that non-Google pixels (Meta, TikTok and others) are blocked when marketing consent is denied.
- [ ] Review consent status in the Google Ads and GA4 interfaces, where Google surfaces whether consent signals are being received.
- [ ] Document your chosen mode, region list and banner categories, and have counsel review them.
After launch, track consent rate by region, Google-reported conversions against store orders from the same regions, and EEA remarketing audience sizes each month. A sudden change in any of them usually means a signal stopped arriving.
FAQ
What is the difference between Consent Mode v1 and v2?
Version 1 had two signals, ad_storage and analytics_storage, which control cookies. Version 2 adds ad_user_data and ad_personalization, which control whether user data can be sent to Google for advertising and whether it can be used for personalized ads and remarketing.
Is advanced consent mode legal under GDPR?
That depends on your circumstances and how your consent approach is designed. Advanced mode sends cookieless pings even when a visitor declines, and some legal teams are more comfortable with that than others. It’s a question for your counsel, not your developer.
Do I need Consent Mode v2 if I only sell in the U.S.?
If you have no meaningful EEA, UK or Swiss traffic, Google’s EU consent requirements are less relevant, though U.S. state privacy laws have their own opt-out rules. If you ship internationally or run campaigns that reach Europe, set it up with region-specific defaults.