Google Consent Mode V2 for Shopify: The Complete Guide

Google Consent Mode V2 is mandatory since July 2025. Learn what it means for your Shopify store, how it works with server-side tracking, and how to stay compliant.

March 16, 2026

Latest

min read

Google Consent Mode V2 for Shopify: The Complete Guide

Since July 2025, Google Consent Mode V2 is no longer optional. Stores that failed to implement it lost remarketing audiences, saw conversion data disappear from their reports, and watched Smart Bidding performance degrade - sometimes within days.

For Shopify store owners running Google Ads, this is a structural change. Consent Mode V2 determines whether Google can use your conversion data for audience building, bidding optimization, and measurement. Get it wrong, and you are spending ad budget on campaigns that cannot learn. Get it right - especially in combination with server-side tracking - and you maintain full data coverage while respecting user privacy.

This guide covers what Consent Mode V2 is, what changed compared to V1, what happened to non-compliant stores, and how to implement it correctly on Shopify.

Google Consent Mode is a framework that adjusts how Google tags behave based on a visitor's consent choices. When a user accepts or declines cookies on your store, Consent Mode communicates those choices to Google's tags - which then modify their behavior accordingly.

Version 1 of Consent Mode introduced two signals: ad_storage and analytics_storage. These told Google whether it was allowed to set advertising cookies and analytics cookies, respectively.

Version 2 added two new signals: ad_user_data and ad_personalization. These signals are more granular - they specify whether a user's data can be sent to Google for advertising purposes and whether that data can be used to personalize ads.

The distinction matters. Under V1, Google could only know whether cookies were allowed. Under V2, Google also knows whether the user has consented to their data being used for ad targeting and remarketing. This aligns with the EU Digital Markets Act (DMA) requirements, which demand explicit consent for using personal data in advertising.

Google made Consent Mode V2 mandatory for all advertisers serving users in the European Economic Area (EEA) and the UK. The enforcement date was July 2025. Since then, any Google tag that does not pass the V2 signals operates in a restricted state - with significant consequences for your data and campaign performance.

For a broader understanding of how tracking works for Shopify stores, see: What is server-side tracking and how to install it for Shopify.

Understanding the four signals is essential for diagnosing tracking issues and configuring your consent setup correctly.

V1 Signals (Original)

ad_storage

Controls whether Google can read and write advertising cookies (such as the _gac cookie that stores Google Click IDs). When denied, Google cannot set or access advertising cookies, which means click-based attribution becomes limited.

analytics_storage

Controls whether Google can read and write analytics cookies (such as the _ga cookie used by GA4). When denied, Google Analytics cannot track sessions in the standard way.

V2 Signals (Added)

ad_user_data

Controls whether user data collected during a conversion event (email, phone number, address) can be sent to Google for advertising purposes. This is the signal that governs Enhanced Conversions. When denied, hashed customer data is not transmitted to Google - even if the conversion event itself is still recorded.

ad_personalization

Controls whether user data can be used for remarketing and personalization. When denied, Google cannot add the user to remarketing audiences or use their data for ad personalization signals.

How they work together

A visitor who accepts all cookies sends four "granted" signals. Google tags operate normally - cookies are set, conversion data with hashed identifiers is sent, and the user is added to remarketing audiences.

A visitor who declines sends four "denied" signals. Google tags still fire - but in a restricted mode. No cookies are set. No personal data is sent. Google receives pings (cookieless signals) that it uses for conversion modeling - estimating the likely number of conversions based on the behavior of consenting users.

This modeling capability is exactly why Consent Mode V2 exists. Rather than losing all data from non-consenting users, Google can model their likely behavior based on statistical patterns from consenting users. The more consenting users you have, the more accurate the modeling becomes.

What Happened to Non-Compliant Stores

The July 2025 enforcement was not a soft deadline. Stores that failed to implement Consent Mode V2 experienced tangible, measurable losses across three areas.

Remarketing audiences stopped growing

Without the ad_personalization signal, Google cannot determine whether users have consented to remarketing. Google's response: stop adding users to remarketing audiences entirely. For stores running retargeting campaigns - which for most Shopify brands represent a significant share of revenue - this meant audiences slowly shrank as existing members expired and no new members were added.

The downstream effect: retargeting campaigns saw reach decline, frequency increase on stale audiences, and cost per acquisition rise.

Conversion data became incomplete

Without the ad_user_data signal, Google cannot process hashed customer data for Enhanced Conversions. This removed the primary mechanism for recovering conversions that cookie-based tracking misses. For stores that had invested in setting up Enhanced Conversions, the benefit disappeared.

Google Ads reports showed fewer conversions - not because fewer people were buying, but because fewer conversions could be attributed. The gap between Shopify revenue and Google Ads reported revenue widened.

Smart Bidding performance degraded

Smart Bidding strategies (Target ROAS, Target CPA, Maximize Conversions) rely on conversion data to train their models. When conversion data becomes incomplete, bidding algorithms receive distorted input. They underbid on high-value audiences and overbid on low-value ones - because their training data no longer reflects reality.

The result: higher CPA, lower ROAS, and campaigns that appear to underperform even when the actual product and creative are strong. The problem is not the campaign - it is the data feeding the algorithm.

For stores spending significant budgets on Google Ads, non-compliance was not a regulatory inconvenience. It was a direct threat to ad performance.

A common misconception: server-side tracking bypasses consent requirements. It does not.

Server-side tracking changes where events are processed (your server instead of the visitor's browser), but it does not change whether consent applies. Google's Conversions API and Measurement Protocol both require consent signals. If a user has not consented, the same restrictions apply regardless of whether the data arrives via a browser tag or a server-side API call.

Here is how the interaction works in practice:

Visitor lands on your store - your consent banner fires and collects their choice
Consent signals are captured - your consent management platform (CMP) sets the four V2 signals
Events are collected server-side - TrackBee or your server-side solution captures PageView, AddToCart, Purchase, and other events
Consent signals are attached to each event - the server-side platform reads the visitor's consent state and includes the correct signals when sending data to Google
Google processes based on consent - for consenting users, full data is processed including hashed identifiers; for non-consenting users, only cookieless pings are processed for modeling

The key point: server-side tracking does not make consent mode irrelevant. But it does make consent mode more effective - because server-side tracking ensures that consenting users' data actually reaches Google, even when browser-side obstacles (ad blockers, script failures, iOS restrictions) would have prevented it.

To understand the broader advantages of server-side tracking with TrackBee's Conversion Booster for Google Ads, server-side delivery is what makes the consent framework work at full capacity.

The combination of server-side tracking and Consent Mode V2 creates a tracking architecture that is both privacy-compliant and data-complete. Here is why the two are better together.

When a user consents, your browser-side Google tag fires and sends data. But that tag can still fail - ad blockers remove it, script conflicts break it, slow page loads prevent it from executing. Consent was given, but Google never receives the data. You have permission to track, but no mechanism that works.

Server-side tracking alone has a compliance problem

Without consent signals, server-side tracking sends all data to Google indiscriminately. Google has no way to distinguish consenting from non-consenting users. This creates regulatory risk and means Google cannot properly model conversions from non-consenting visitors.

Server-side tracking ensures that every consenting user's data reaches Google - reliably, without browser dependencies. Consent Mode V2 ensures that non-consenting users are handled correctly - their data is not transmitted for advertising purposes, but Google can still model their likely conversions.

The net effect: you capture the maximum possible conversion data within the boundaries of user consent. Your Enhanced Conversions coverage improves because server-side delivery eliminates the browser-side failures that waste consented data. And your modeling accuracy improves because you have a larger pool of complete, consented conversion data for Google to extrapolate from.

TrackBee is built to respect consent signals without requiring manual configuration. Here is what happens under the hood.

When a visitor makes a consent choice on your store, TrackBee reads the consent state from your consent management platform. The four V2 signals (ad_storage, analytics_storage, ad_user_data, ad_personalization) are captured and attached to every subsequent event for that session.

There is no need to manually map consent categories to TrackBee events. The integration reads your CMP's output directly.

For visitors who consent: TrackBee sends the full, enriched event to Google - including hashed email, phone, name, address, Google Click IDs, and all session context. This maximizes Enhanced Conversion Coverage and gives Smart Bidding the richest possible training data.

For visitors who decline: TrackBee sends the conversion event without personal identifiers. No hashed email. No phone number. No address. The event includes only non-personal signals - transaction value, product category, timestamp - along with the denied consent signals. Google receives enough to power conversion modeling without receiving any personal data.

TrackBee's persistent Shopper Profiles handle mid-session consent changes gracefully. If a visitor initially declines consent but later accepts (for example, during checkout), TrackBee updates the consent state and adjusts what data is sent going forward. There is no need to reload pages or restart sessions.

TrackBee has been tested and validated with Shopify-compatible consent management platforms. The recommended options are Pandectes and Consentik - both support the full Consent Mode V2 signal set and integrate cleanly with Shopify's consent architecture.

Implementing Consent Mode V2 on Shopify requires two components: a consent management platform (CMP) that collects user choices and communicates them via the V2 signals, and a tracking setup that respects those signals.

Not every cookie banner supports Consent Mode V2. Many basic Shopify consent apps only handle cookie storage - they do not pass the ad_user_data and ad_personalization signals that V2 requires.

Recommended options:

Pandectes - Full Consent Mode V2 support, Google-certified CMP, automatic geo-detection for GDPR/CCPA compliance, Shopify app with straightforward setup
Consentik - Lightweight, Consent Mode V2 compatible, designed specifically for Shopify

Both options pass all four consent signals to Google tags and to server-side tracking integrations like TrackBee.

When setting up your CMP, ensure the following:

Default consent state is set to "denied" for EEA visitors (required by GDPR). This means Google tags start in restricted mode until explicit consent is given.
All four V2 signals are mapped to the appropriate consent categories in your banner. Most certified CMPs handle this automatically, but verify in testing.
The banner loads before any tracking tags fire. If tags fire before the consent banner initializes, you risk sending data before consent is determined - which is both a compliance issue and a data quality issue.

Step 3: Connect TrackBee

Once your consent banner is active, connect your store to TrackBee via the TrackBee dashboard. TrackBee automatically detects the consent signals from your CMP. No additional consent configuration is needed within TrackBee.

Step 4: Verify your setup

Visit your store in an incognito browser
Decline consent when the banner appears
Complete a test purchase
Check your TrackBee Accuracy page - the order should appear, tagged as a declined-consent conversion
In Google Ads, verify that the conversion shows as modeled (not directly attributed)

For full setup verification steps including the App Embed check, see: What is server-side tracking and how to install it for Shopify.

Impact on Google Ads Performance

Implementing Consent Mode V2 correctly - especially with server-side tracking - produces measurable improvements across several campaign metrics.

More complete conversion data

The most immediate impact is in your conversion reporting. With proper V2 implementation, Google receives clear consent signals for every user. Consenting users contribute full Enhanced Conversions data. Non-consenting users contribute modeled conversions. The result: your Google Ads conversion count more closely reflects your actual Shopify revenue.

Improved Smart Bidding accuracy

Smart Bidding algorithms train on your conversion data. When that data is more complete and more accurately attributed, bid predictions improve. Expect tighter alignment between your Target ROAS/CPA settings and actual performance - because the algorithm is working with better input.

TrackBee's Conversion Booster for Google Ads amplifies this effect by combining server-side delivery with data enrichment. The average result: a 17.1% increase in measured conversions, which directly improves Smart Bidding's training data.

Remarketing audiences that grow again

With the ad_personalization signal properly implemented, consenting users are added to your remarketing audiences again. Audience sizes stabilize and grow. Retargeting campaigns regain reach and efficiency.

Conversion modeling fills the gap

For stores with high consent decline rates (common in Germany, Austria, and the Netherlands), conversion modeling becomes critical. Google estimates the number of conversions from non-consenting users based on the behavior patterns of consenting users. The larger and more complete your consenting user data, the more accurate this modeling becomes.

This is where server-side tracking provides compounding value: it ensures that consenting users' data reaches Google reliably, which improves the statistical foundation for modeling non-consenting conversions. Better data from consenting users means better estimates for everyone.

Frequently Asked Questions

What is the difference between Consent Mode V1 and V2? V1 had two signals: ad_storage and analytics_storage, controlling whether Google could set advertising and analytics cookies. V2 added ad_user_data (whether user data can be sent to Google for advertising) and ad_personalization (whether data can be used for remarketing/personalization). V2 is required by the EU Digital Markets Act.

Is Consent Mode V2 required outside the EEA? Google's enforcement currently targets advertisers serving users in the EEA and UK. However, implementing V2 globally is recommended - it future-proofs your setup against expanding regulations and ensures consistent data handling across all markets.

Does Consent Mode V2 reduce my conversion data? Not compared to the alternative. Without V2, Google cannot process your data for audiences or Enhanced Conversions at all (for EEA users). With V2, consenting users contribute full data, and non-consenting users contribute modeled data. You end up with more usable conversion data, not less.

Can I use Consent Mode V2 with Google Analytics 4? Yes. GA4 respects the same consent signals. When analytics_storage is denied, GA4 sends cookieless pings instead of full session data. GA4 then uses behavioral modeling to estimate metrics for non-consenting users. TrackBee's server-side GA4 integration also respects these consent signals.

What happens if my consent banner does not support V2? Google treats the missing V2 signals as "denied" by default. This means even users who click "Accept All" on your banner may be treated as non-consenting for ad_user_data and ad_personalization - because those signals were never communicated. The fix: switch to a V2-compatible CMP like Pandectes or Consentik.

Does TrackBee work with any consent banner? TrackBee reads consent signals from any CMP that implements the Google Consent Mode V2 API correctly. Pandectes and Consentik are recommended because they have been validated for complete V2 signal support on Shopify. Other CMPs may work but should be tested to confirm all four signals are passed correctly.

Will implementing Consent Mode V2 break my current tracking? No. Consent Mode V2 is additive - it adds two new signals without changing how the original two work. Your existing tracking continues to function. The V2 signals provide Google with additional information about what it can do with the data it receives.

min read

In this article

Boost Your Revenue

Track Missing Conversion Data

Lorem Ipsum