Home / Blog / Consent Mode V2 Broke Shopify Conversion Tracking
Shopify · Consent Mode V2 · Google Ads
Consent Mode V2 Broke Shopify Conversion Tracking: What to Check
If Google Ads purchases dropped, GA4 purchases disappeared, or Shopify checkout events stopped showing after Consent Mode V2 changes, do not assume the pixel is broken. Consent Mode V2 can make a working Shopify setup look broken when consent signals fire in the wrong order, the CMP does not pass all four Google signals, GTM overrides consent, or server-side tracking does not receive the same consent state.
ad_storage, analytics_storage, ad_user_data, or ad_personalization are missing, delayed, overridden, or not updated after cookie acceptance.Key takeaways
- Consent Mode V2 is not a cookie banner. It is a signal layer.
- V2 added
ad_user_dataandad_personalization. - A Shopify banner can look correct while sending incomplete or late signals.
- Server-side tracking does not bypass consent.
- Validate with Tag Assistant, GA4 DebugView, Google Ads diagnostics, and Elevar checks.
What changed in Consent Mode V2
Google says Consent Mode lets websites control how Google tags behave based on consent choices, and V2 added two new parameters. Google Consent Mode overview Google Consent Mode setup
| Consent signal | What it controls | Common Shopify failure |
|---|---|---|
| ad_storage | Google Ads cookies and ad identifiers | Stays denied after accept or loads too late |
| analytics_storage | Analytics cookies and identifiers | GA4 blocked or sessions missing |
| ad_user_data | Sending user data to Google for ads | Missing in old V1 setups |
| ad_personalization | Personalized ads and remarketing | Remarketing/audience signals limited |
Why Shopify stores are fragile
Shopify tracking can be split across Google & YouTube app, Customer Events, theme code, GTM, Elevar, a CMP app, and checkout sandboxed pixels. Shopify’s Customer Privacy API docs say consent can be collected asynchronously and integrations should listen for consent collection events. Shopify Customer Privacy API
Common symptoms
| Symptom | Likely cause | First check |
|---|---|---|
| GA4 purchases missing | analytics_storage denied, late, or not updated | Tag Assistant + DebugView |
| Google Ads purchases dropped | ad_storage or ad_user_data missing/denied | Google Ads diagnostics |
| Remarketing audiences shrink | ad_personalization missing/denied | Consent signals and audience diagnostics |
| Enhanced conversions warning | ad_user_data missing or data blocked | Enhanced conversion diagnostics |
| Tags still blocked after accept | GTM override/default issue | Tag consent settings |
| Consent tab empty | Consent Mode missing or Google tag blocked | Tag Assistant |
Elevar-specific checks
Elevar says consent setup makes GTM tags consent-aware as well as server-side activities configured inside Elevar destinations, and that consent can block data until granted. Elevar Consent Overview
- Consent Mode is enabled in the Shopify Source/data layer.
- The CMP is supported or mapped correctly.
- Cookiebot/Consentmo/Pandectes/other CMP template is updated for V2.
- All four Google signals are present.
- Server-side destinations have destination-specific consent rules.
- Accepted, denied, and no-choice states are tested through checkout.
Most common setup mistakes
1. Missing V2 signals
Google’s verification guide says to check the earliest Consent event and confirm ad_storage, ad_personalization, ad_user_data, and analytics_storage. Verify consent mode
2. Consent update fires too late
Google warns that if a page loads denied and then reloads granted after consent changes, Google tags may lose key data points. Call the update command whenever consent changes.
3. GTM overrides consent defaults
Shopify Community cases show GTM override settings can keep Google tracking blocked even after users accept cookies. Shopify Community consent issue
4. CMP does not integrate with Customer Privacy API
Google recommends using a CMP that integrates with Shopify Customer Privacy API. Google Shopify consent setup
5. Server-side tracking does not receive consent state
Server-side tracking needs consent mapping too. Littledata says its Shopify Consent Mode V2 integration works through Shopify Customer Privacy API. Littledata Consent Mode V2
Basic vs advanced consent mode
| Implementation | Behavior | What can go wrong |
|---|---|---|
| Basic consent mode | Tags blocked until consent granted | No denied pings, fewer modeling signals, no data before accept |
| Advanced consent mode | Tags load with denied defaults and update when consent changes | Wrong defaults, missing update, late CMP, identifiers lost before update |
How to test on Shopify
- Open Tag Assistant.
- Visit the storefront in a fresh session.
- Before clicking the banner, check the earliest Consent event.
- Confirm all four signals exist.
- Confirm default state is intended for that region.
- Accept cookies and confirm consent update fires.
- Repeat with reject/deny.
- Repeat through checkout and purchase.
- Check GA4 DebugView and Google Ads diagnostics.
- Check Elevar server-side destinations and consent rules.
Diagnostic table
| Issue | Likely cause | Where to check | Fix direction |
|---|---|---|---|
| Consent tab empty | Consent Mode missing or tag blocked | Tag Assistant | Unblock tag and implement consent commands |
| Only two signals visible | V1 setup not upgraded | Earliest Consent event | Add ad_user_data and ad_personalization |
| Signals stay denied after accept | Update missing or CMP not integrated | Consent timeline | Fire consent update after choice |
| Purchase missing after accept | Tag sequencing/race issue | GTM preview, DebugView | Initialize consent before purchase |
| Google Ads drops conversions | ad_storage/ad_user_data denied or missing | Google Ads diagnostics | Fix Ads consent signals |
| Remarketing issue | ad_personalization missing | Tag Assistant + audiences | Pass personalization consent |
| Elevar server events lack identifiers | Consent not passed server-side | Elevar consent rules | Map consent to destinations |
| Tracking blocked despite accept | GTM override defaults | Tag consent settings | Remove incorrect overrides |
What not to do
- Do not install multiple CMPs at once.
- Do not paste random Consent Mode snippets into theme.liquid without auditing Customer Events, Google & YouTube, GTM, and Elevar.
- Do not assume the banner UI proves Consent Mode works.
- Do not test only the homepage. Checkout and purchase are where money is lost.
TrackingAudit validation checklist
- CMP identified and confirmed compatible or mapped.
- All four Consent Mode V2 signals present.
- Default consent state appears before Google tags fire.
- Consent update fires after accept/reject.
- Tag Assistant Consent tab is populated.
- GA4 fires according to analytics_storage.
- Google Ads fires according to ad_storage and ad_user_data.
- GTM tag-level overrides reviewed.
- Elevar Shopify Source consent mode enabled if used.
- Elevar server-side destinations listen to consent correctly.
- Checkout and purchase tested in accepted and denied states.
Conversions dropped after Consent Mode V2?
TrackingAudit can inspect Shopify Customer Privacy, CMP configuration, GTM consent order, Elevar consent mode, GA4, Google Ads, and server-side destinations.
Get your free audit →Frequently asked questions
Can Consent Mode V2 break Shopify conversion tracking?
Yes. It can reduce or break tracking when consent signals are missing, late, overridden, or not passed into checkout/server-side tracking.
What are the four Consent Mode V2 signals?
ad_storage, analytics_storage, ad_user_data, and ad_personalization.
Why did conversions drop after adding a cookie banner?
The banner may block tags, fail to send updates, miss V2 signals, or load after the purchase event.
Does server-side tracking bypass consent?
No. Server-side tracking must still respect consent and receive the correct consent state.
How do I test Consent Mode V2?
Use Tag Assistant’s Consent tab, confirm all four signals, test accept/reject, then test checkout in GA4, Google Ads, and Elevar.
Sources
- Google Developers: Set up consent mode on websites
- Google Developers: Consent mode overview
- Google Tag Manager Help: Verify consent mode implementation
- Google Tag Manager Help: Updates to consent mode for EEA
- Google Ads Help: About consent mode
- Google Ads Help: Tag Diagnostics and consent issues
- Google Analytics Help: Troubleshoot consent mode
- Google Analytics Help: Set up Shopify to obtain user consent
- Shopify Help: Customer privacy settings
- Shopify Help: Create GTM custom pixel
- Shopify Dev: Customer Privacy API
- Elevar: Consent Overview
- Elevar: Consent Mode v2 March 2024 updates
- Elevar: Cookiebot Consent Mode setup
- Elevar: Updating Cookiebot for Consent Mode V2
- Elevar: Consentmo Consent Mode setup
- Littledata: Google Consent Mode v2 with Shopify
- Littledata: Check Google Consent Mode V2 is working
- Analyzify: Consent-compliant setup
- Stape: Consent mode in server GTM
- Shopify Community: Cookie consent and Google Analytics
- Shopify Community: Cookie consent blocking Google Ads tracking
- Shopify Community: Google Ads conversions dropping after consent changes
- Reddit: Consent Mode V2 Shopify conversions tracking issue