Google Consent Mode v2

Enable Google Consent Mode v2, wire GTM, and verify tag signals with CookieShift.

Integrations — Google Consent Mode v2 and related consent signals
Integrations — Google Consent Mode v2 and related consent signals

CookieShift sends Google Consent Mode v2 signals so Google tags respect marketing and analytics choices before cookies are set.

Overview

Consent Mode v2 tells Google Ads, Analytics, and Tag Manager how to behave based on your banner categories. CookieShift maps your consent categories to ad_storage, analytics_storage, ad_user_data, and ad_personalization.

Why it matters

Without Consent Mode, Google tags may fire in restricted regions before consent — risking regulatory exposure and inaccurate conversion modeling. v2 is required for EU/UK traffic and recommended globally.

Setup

  1. Open Consent Setup → Google Consent Mode v2 for your property.
  2. Enable Consent Mode and confirm default denied state matches your legal basis.
  3. Install CookieShift before GTM or gtag in <head> (see Installation).
  4. In GTM, use Consent Initialization tags or rely on CookieShift’s automatic gtag('consent', 'default', …) when configured.
  5. Publish the banner and run a test page load in Tag Assistant.

Examples

ScenarioExpected signal
User accepts analytics onlyanalytics_storage: granted, ads denied
User rejects allAll storages denied
US CCPA “Do Not Sell”Ads personalization denied per your mapping

Troubleshooting

  • Tags fire before banner — Move the CookieShift script above GTM; clear cache.
  • Consent not updating — Confirm property siteId matches the domain you are testing.
  • GTM preview shows denied forever — Accept categories in the banner and reload; check category mapping in Consent Setup.

Best practices