Aimerce Blog

Consent Mode v2 on Shopify: What Actually Changes for Your Conversion Data

2 October 2026

Consent Mode v2 on Shopify: What Actually Changes for Your Conversion Data

First-Party Data 101

Quick Answer: Consent Mode v2 is Google's framework for passing each visitor's consent choices to Google Ads and GA4. On Shopify, your cookie banner writes those choices to Shopify's Customer Privacy API, and that state has to reach your Google tags as four signals: ad_storage, analytics_storage, ad_user_data, and ad_personalization. It has been required for traffic from the EEA, UK, and Switzerland since March 2024 if you use Google remarketing or conversion measurement. Basic mode blocks Google tags until a shopper consents. Advanced mode loads them in a restricted state and sends cookieless pings, which lets Google model the conversions it can't observe. It governs Google only, so Meta, TikTok, and Klaviyo need their own consent handling.

Key Takeaways

Consent Mode v2 is a campaign performance decision dressed up as a compliance task. The mode you pick decides how many conversions Google Ads gets to bid on for EEA and UK shoppers.
Version 2 added two signals to the original pair: ad_user_data and ad_personalization. Missing either one is a common reason a "compliant" store still loses remarketing and measurement features.
On Shopify, consent lives in the Customer Privacy API. Your banner app has to write to it and your Google setup has to read from it. When those two disagree, nothing warns you.
Advanced mode enables advertiser-specific conversion modeling once you clear Google's traffic threshold. Basic mode falls back to a general model.
It doesn't touch Meta CAPI, TikTok Events API, or Klaviyo. Server-side tracking doesn't exempt you from consent either. It should respect the same consent state as everything else.

Every few weeks a brand tells me their Google Ads conversions dropped for European traffic and asks whether the algorithm broke. Usually nothing broke. Their cookie banner is doing its job, Google isn't hearing about it properly, and the conversions that should have been modeled are simply gone.

Most guides treat Consent Mode v2 as a legal checkbox. I'd rather treat it as what it actually is for a DTC brand: a setting that decides how much conversion data Google's bidding gets to learn from. The legal part matters. So does the part where your ROAS changes.

It's a set of signals your site sends to Google on every page load, saying what this particular visitor agreed to. Google's tags then adjust what they collect.

The original Consent Mode had two signals, analytics_storage and ad_storage. Version 2 added ad_user_data, which covers whether user data can be sent to Google for advertising, and ad_personalization, which covers whether it can be used for remarketing. Google made v2 mandatory for EEA, UK, and Swiss traffic in March 2024 for anyone using remarketing or conversion measurement, following the EU's Digital Markets Act.

One thing it isn't: a consent banner. Consent Mode doesn't ask anyone anything. It only relays the answer your banner collected. Setting every signal to granted by default and calling it done is one of the most common failures out there, and it's a compliance problem, not a clever workaround.

Three pieces have to agree with each other.

The banner. Shopify has its own, and the App Store has dozens of consent apps (CMPs). Whatever you use has to write the shopper's choice to Shopify's Customer Privacy API by calling setTrackingConsent.

The Customer Privacy API. This is Shopify's source of truth for consent on the storefront. Apps and web pixels read from it, and Shopify admin is where you decide which regions require consent at all.

Your Google tags. Whether Google runs through the Google & YouTube app, a GTM container, or a custom pixel, something has to translate Shopify's consent categories into Google's four signals.

That translation step is where things quietly break. Shopify's categories and Google's signals don't map one to one. Developers on Shopify's own community forum have documented setups where the native Google integration plus Shopify's banner didn't pass v2 signals into GTM without custom mapping, and cases where a pixel received a default consent state of granted when it shouldn't have. None of this throws an error. Your store looks fine. Your Google Ads data just gets thinner.

Basic vs. Advanced: which one changes your numbers?

This is the decision that actually matters for performance.

Basic mode keeps Google tags blocked until a shopper interacts with the banner. If they decline, Google gets nothing. Conversion modeling in Google Ads still exists, but it runs on a general model rather than one trained on your account.

Advanced mode loads Google tags right away in a restricted state. When a shopper declines, no ad or analytics cookies are set, but the tags send cookieless pings carrying non-identifying information. Google uses those pings to build an advertiser-specific model of the conversions it couldn't see, and GA4 can use them for behavioral modeling.

There's a catch. Advertiser-specific modeling only switches on once your account meets Google's minimum traffic threshold. Below it, you're compliant but the modeling benefit doesn't apply yet. Google Ads shows this status per conversion action, so check it before assuming modeling is working.

Which should you pick? Part of that is a legal call, and I'd run it past whoever owns privacy for your brand, because some legal teams aren't comfortable with any pre-consent pings at all. If your counsel is fine with Advanced, though, it's the version that gives Google's bidding the most to work with.

What happens	No Consent Mode	Basic	Advanced
Google tags before the shopper answers the banner	Uncontrolled, depends entirely on your banner setup	Blocked	Load in a restricted state
When the shopper declines	Google gets no consent signal at all	Nothing is sent	Cookieless pings, no cookies set
Google Ads conversion modeling	Not available	General model	Advertiser-specific model, once you clear Google's traffic threshold
GA4 behavioral modeling	No	No	Yes
EEA and UK remarketing and measurement	At risk	Supported	Supported
Best for	Nobody selling into the EEA or UK	Brands whose legal team wants zero pre-consent data sent to Google	Brands that rely on Google Ads bidding and have meaningful EU or UK traffic

This is where most of the confusion lives, so I'll be blunt. Consent Mode v2 is a Google specification. It does nothing for Meta, TikTok, Pinterest, or Klaviyo.

If a shopper declines marketing cookies, your Meta Pixel and Conversions API setup need their own logic to respect that. Same for TikTok's Events API. A store can have perfect Consent Mode v2 and still send Meta events it shouldn't, or block events it's allowed to send.

Server-side tracking isn't a consent loophole either. Moving events from the browser to a server changes how reliably they arrive. It doesn't change whether you're allowed to send them. A well-built server-side tracking setup on Shopify reads the same consent state as everything else and acts on it.

This is also why consent and conversion discrepancies are linked. If EU and UK shoppers are a meaningful share of your sales, part of the gap between Shopify orders and what ad platforms report is consent, not broken ecommerce conversion tracking. Knowing which is which keeps you from "fixing" something that's working as designed.

How do you check your setup in about 15 minutes?

Confirm your region settings. In Shopify admin, open your customer privacy settings and check which regions require consent. If the EEA and UK aren't covered, start there.
Visit as an EU shopper. Set a VPN to an EEA country, open your store in a private window, and confirm the banner appears before anything else fires.
Watch the consent state in Tag Assistant. With Google Tag Assistant connected, check the consent view before you click anything. All four signals should start as denied. Decline, and they should stay denied. If any show as granted before you've answered the banner, your default is wrong.
Accept and repeat. Reload, accept cookies, and confirm the signals flip to granted.
Check Google Ads diagnostics. Open your conversion actions in Google Ads and look at the consent mode status for each one. It tells you whether Consent Mode is detected and whether modeling is active or you're still below the threshold.
Test the other platforms too. Run the same decline test and confirm your Meta and TikTok events behave the way your consent policy says they should.

What should you expect in your reports after switching?

Give it time before judging. Modeled conversions show up in Google Ads alongside observed ones, and the model needs data to build up. Comparing the first week after a change to the week before tells you almost nothing.

Expect Google Ads and Shopify to diverge in new ways, too. Shopify counts real orders. Google Ads now includes conversions it estimates happened among shoppers who declined. Neither number is wrong. They answer different questions, which is the same lesson as every other platform-versus-Shopify comparison.

Common mistakes to avoid

Defaulting signals to granted. It makes your dashboards look healthier and your compliance much worse.
Sending only the two original signals. Without ad_user_data and ad_personalization, your setup is incomplete for EEA and UK traffic.
Using a banner app that doesn't write to the Customer Privacy API. The banner looks right, but nothing downstream knows what the shopper chose.
Assuming Consent Mode covers Meta and TikTok. It doesn't. Those need separate consent logic.
Treating server-side tracking as a way around consent. It improves delivery, not permission.
Judging Advanced mode in week one. Modeling needs volume and time.

FAQ

Do I need Consent Mode v2 if I don't sell in Europe? Google's requirement applies to traffic from the EEA, UK, and Switzerland. If you get meaningful traffic from those regions and use Google remarketing or conversion measurement, you need it. Privacy rules elsewhere keep shifting too, so setting it up properly once beats patching it later.

Does Consent Mode v2 work with Shopify's own cookie banner? It can, as long as the consent choice reaches your Google tags as v2 signals. Whether that happens automatically depends on how Google is installed on your store, so test it in Tag Assistant rather than assuming.

What's the difference between Consent Mode v1 and v2? Version 1 used two signals, ad_storage and analytics_storage. Version 2 added ad_user_data and ad_personalization, which control whether user data can be sent to Google for ads and used for remarketing.

Should I use Basic or Advanced Consent Mode on Shopify? Advanced gives Google Ads more to model from, since it sends cookieless pings when shoppers decline. Basic sends nothing until consent. The right choice depends on your legal team's comfort with pre-consent pings and how much you rely on Google Ads bidding.

Does Consent Mode v2 affect my Meta ads? No. It's a Google specification. Meta Pixel and the Meta Conversions API need their own consent handling on your Shopify store.

Does server-side tracking let me skip consent? No. Server-side tracking makes events arrive more reliably, but the same consent rules apply to them. A good setup reads the shopper's consent state and respects it.

Why did my Google Ads conversions drop after adding a cookie banner? Usually because shoppers who decline are no longer tracked and you're either on Basic mode or below the modeling threshold. Check the consent status in Google Ads diagnostics before changing bids or budgets.