Privacy-Safe Tracking · Consent Mode v2
We implement Consent Mode v2 across GA4 and Google Ads with region-based defaults, all four consent signals and a CMP that updates them correctly, then prove it works in Tag Assistant and in the network requests.
What it is
Consent Mode is Google's way of passing a visitor's consent choices to its tags. Your consent management platform records the choice; Consent Mode translates it into signals that GA4, Google Ads and other Google tags adjust to. Version 2 added two signals about advertising use of data: ad_user_data and ad_personalization.
For visitors from the EU and UK, Google expects these signals before it uses their data for ad measurement, remarketing and personalization. A U.S. store with any European traffic needs it working, and a U.S.-only store can use the same mechanism to honor opt-outs and Global Privacy Control.
The signals
| Signal | What it controls | Typical EU and UK default | Typical U.S. setup |
|---|---|---|---|
| analytics_storage | Analytics cookies, such as GA4 client IDs | Denied until the visitor accepts | Granted, unless your counsel decides otherwise |
| ad_storage | Advertising cookies, such as Google Ads click identifiers | Denied until the visitor accepts | Granted, switched to denied on opt-out or GPC |
| ad_user_data | Whether user data may be sent to Google for advertising | Denied until the visitor accepts | Granted, switched to denied on opt-out or GPC |
| ad_personalization | Whether data may be used for remarketing and personalized ads | Denied until the visitor accepts | Granted, switched to denied on opt-out or GPC |
These are common starting points, not recommendations. The right defaults for your store are a decision for you and your counsel; we implement whatever you approve.
Basic or advanced
Google tags don't load until the visitor grants consent. If they decline, nothing is sent to Google. It's the simplest model to explain and audit.
Google tags load with denied defaults. Without consent they set no cookies and send limited, cookieless pings. When the property meets Google's eligibility requirements, GA4 and Google Ads use these to model the conversions they can't observe.
How we implement it
Where your traffic comes from, which regions get opt-in defaults and which get opt-out, and how Global Privacy Control is treated.
The CMP sets region-specific defaults on GTM's Consent Initialization trigger, with a short wait for the banner to update them.
Google tags use built-in consent checks. Meta, TikTok and other non-Google tags get additional consent checks in Google Tag Manager so they follow the same choice.
On Shopify, app pixels and custom pixels follow Shopify's customer privacy settings, so the CMP must pass the choice to Shopify as well as to Google tags.
Tag Assistant's consent view for each state, plus the consent parameters on Google's network requests, under accept, reject and GPC.
Consent rates by region and whether GA4 modeling is active, reviewed after banner or tag changes.
Common mistakes
The default command runs after GA4 or Google Ads has already fired, so the first page view ignores consent entirely.
ad_user_data and ad_personalization are never set, so Google treats EU and UK traffic as lacking consent for ad features.
The banner records the choice but doesn't send the update, so tags stay denied after a visitor accepts.
Consent Mode only governs Google tags. Meta and other pixels keep firing unless they're blocked separately.
Related services
Consent Mode depends on a correctly configured banner, covered under CMP Setup. To check what your store actually does today, start with a Tracking Privacy Review. To recover signal from consented visitors, add server-side tracking and enhanced conversions. Lower observed conversions change reported ROAS, so recheck targets with the ROAS calculator. All part of Privacy-Safe Tracking.
FAQ
Version 2 added two signals, ad_user_data and ad_personalization, to the existing ad_storage and analytics_storage. They tell Google whether user data may be sent for advertising and whether it may be used for personalized ads and remarketing. Without them, Google can't use EU and UK traffic for those features.
Google's requirement applies to visitors from the EU and UK, so it matters for any U.S. store that gets European traffic. For U.S. visitors, Consent Mode is not required by Google, but it's a practical way to switch off advertising signals when someone opts out or sends Global Privacy Control.
Basic mode sends nothing to Google until consent is granted. Advanced mode sends limited cookieless pings when consent is denied, which lets Google model missing conversions. Advanced usually gives more complete reporting, but it's a data-sharing decision your counsel should approve. We can implement either and switch later.
Open Tag Assistant, load your store as a new visitor and check the consent state before and after each choice. Then inspect Google's network requests for the consent parameters. Both should change when the visitor accepts or rejects. We document these tests for each region and state.
No. Consent Mode only adjusts Google tags. Other pixels must be blocked or allowed by your CMP or by additional consent checks in Google Tag Manager. This is one of the most common gaps we find: Google tags respect consent while every other pixel keeps firing.
Start with the free audit to see how your consent setup looks from the outside, or book a call to review your banner and tags with us.