Consent Mode v2 is one of those things store owners either ignore until their remarketing audiences dry up, or over-implement until GA4 goes dark. Here’s the plain-English version: what it is, why it’s required, and how to set it up on Shopify without breaking your analytics.
Why it’s required
Since March 2024 (widely reported as March 6, 2024), Google requires advertisers to collect consent from EEA end users — and, as most implementations apply it, UK users — and pass those consent signals to Google. Without them, Google won’t use that traffic’s data for ads personalization or remarketing. Data may still flow, but your remarketing lists, audiences and conversion modeling quietly degrade.
This isn’t optional if you run Google Ads to EU/UK shoppers. It’s the price of keeping personalization and remarketing working.
The four signals
Consent Mode v2 kept the original two parameters and added two new ones:
| Signal | Controls | Added |
|---|---|---|
ad_storage | Advertising cookies/identifiers | v1 |
analytics_storage | Analytics cookies (GA4) | v1 |
ad_user_data | Sending user data to Google for advertising | v2 |
ad_personalization | Personalized advertising / remarketing | v2 |
The two v2 additions are what “v2” means — miss them and you’re not compliant with the current requirement.
Basic vs Advanced — pick deliberately
- Basic: Google tags don’t load until the shopper interacts with the banner. Nothing is sent before consent — not even a consent-state ping. Simpler, but Google has nothing to model with for people who ignore the banner.
- Advanced: tags load on every page with consent defaulted to denied, sending cookieless pings (consent state + limited, non-identifying signals). On consent, full measurement follows. This gives Google the denied-state data it uses for conversion modeling — usually the better choice for advertisers.
Most CMPs default to Advanced. Choose consciously; it changes how much recovered/modeled data you get.
Setting it up on Shopify — two paths
Path 1 — Native (simplest).
- Settings → Customer privacy → Cookie banner → Set up banner. Configure the regions where it shows (at least the EEA/UK).
- Per Google’s own Shopify guidance, once the banner is enabled, Consent Mode is enabled automatically — and if you use the Google & YouTube channel app for GA4/Ads, it reads Shopify’s consent signals with no manual
gtagwiring.
That’s genuinely it for many stores: Shopify’s Customer Privacy API is the consent layer, and the Google app consumes it.
Path 2 — CMP (more control / IAB TCF). If you need granular categories, IAB TCF, or multi-platform signals, use a CMP that integrates with Shopify’s Customer Privacy API — Cookiebot, Usercentrics, Pandectes, Consentmo, CookieYes. The CMP writes consent to Shopify’s API and relays it to Google tags (and GTM, if you enter your container ID). Follow the CMP’s Shopify integration doc; most enable Advanced mode by default.
Either way, if you deploy tags through GTM, make sure your tags are gated by consent checks, not hard-removed (see the trap below).
The trap: over-blocking that kills all GA4 events
The most common — and most damaging — misconfiguration is hard-blocking tags until the banner is clicked on top of Consent Mode. Google is explicit: if you prevent Google tags from loading until a user interacts with your banner, Google can’t verify consent and you lose data. The result: shoppers who never touch the banner generate no pings and no signals at all — GA4 effectively goes silent for a chunk of traffic.
Correct behavior: let Consent Mode adjust tag behavior based on consent state instead of stripping the tags out. In Advanced mode, tags still fire, send denied-state cookieless pings, and unlock full data only after consent. If your GA4 is mysteriously empty in the EU/UK, this double-gating is the first thing to check — details in Consent Mode blocking all GA4 events.
Verify it works
- Load the store from an EEA/UK context (or with a VPN) — the banner should appear.
- Before consent: in the tag debugger, confirm consent defaults are
deniedand (Advanced) cookieless pings still fire. - After accepting: confirm
ad_user_data,ad_personalization,ad_storage,analytics_storageflip tograntedand full events flow into GA4 DebugView. - After rejecting: confirm events are adjusted, not the whole tag disappearing.
Not sure if your consent setup is compliant — or silently dropping conversions? The free Tracking-Health Mini-Audit checks Consent Mode alongside your GA4 and Meta setup in ~10 minutes.
FAQ
Is Consent Mode v2 required on Shopify? For EEA (and UK) traffic, yes — since March 2024 Google needs the v2 signals to use data for ads personalization and remarketing.
What are the four signals?
ad_storage, analytics_storage, plus the v2 additions ad_user_data and ad_personalization.
How do I enable it? Set up the banner under Settings → Customer privacy; with the Google & YouTube app, Consent Mode enables automatically. Or use a CMP that integrates with Shopify’s Customer Privacy API.
Basic vs Advanced? Basic blocks tags until interaction; Advanced loads them denied-by-default and sends cookieless pings, giving Google more to model with.
Related
- Consent Mode blocking all your GA4 events
- Does Consent Mode v2 hurt conversions?
- GA4 DebugView isn’t showing events