Your consent management platform (CMP) collects the visitor’s choice. Consent Mode passes it to Google tags such as GA4, Google Ads and Floodlight through four parameters: ad_storage, analytics_storage, ad_user_data (consent to send user data to Google for advertising) and ad_personalization (consent to personalized advertising). The last two were added in Consent Mode v2.
Google requires advertisers to pass consent signals for users in the European Economic Area to keep using ads measurement and personalization for that traffic. Google’s EU user consent policy also covers the UK and Switzerland.
There are two implementations. In basic mode, Google tags don’t load until the visitor consents, so Google receives nothing from visitors who decline. In advanced mode, tags load with consent denied by default and send cookieless pings when a visitor declines, which Google uses for conversion modeling in Google Ads and behavioral modeling in GA4.
Why it matters for eCommerce
For U.S. brands selling into Europe, missing Consent Mode v2 means EEA visitors drop out of remarketing audiences and conversion measurement. A correct setup keeps that traffic usable within what visitors allowed. Consent Mode can also carry opt-out choices for U.S. traffic, but legal requirements differ by state, so confirm with counsel.
How it works in practice
- Use a CMP that supports Consent Mode v2 and Shopify’s customer privacy API.
- Set the default consent state by region before any Google tag fires.
- Choose basic or advanced mode with your legal team.
- Use Tag Assistant to confirm all four parameters update after a visitor makes a choice.
Common mistakes
- Sending the consent update after tags have already fired.
- Setting only ad_storage and analytics_storage and missing the two v2 parameters.
- Assuming Consent Mode makes a site compliant. It only transmits the choice.