Google Consent Mode CMP

Activate Google Consent Mode with UniConsent

Google Consent Mode is a feature that allows web and app developers to adjust the behavior of Google tags and app SDKs based on the consent choices made by users. UniConsent CMP integrates with Google Consent Mode to tailor how Google tags behave on your website or app, depending on whether users have granted or denied consent.

When targeting European users with Google Ads or Google Analytics, you risk losing marketing data when users decline consent banners. With UniConsent and Google Consent Mode, you can recover conversion data through modeling and close the gap in your advertising and analytics reporting. This integration helps fill data gaps when users choose not to give consent.

Since March 2024, Google requires Consent Mode for using audience personalization and measurement features when targeting users in the European Economic Area, the United Kingdom, and Switzerland.

Consent Mode v2: Basic vs Advanced

Google Consent Mode v2 offers two implementation approaches:

Basic Consent Mode blocks all Google tags from firing until the user grants consent. No data is collected before the user interacts with the consent banner. This is the simpler approach but means you lose all measurement data from users who decline consent.

Advanced Consent Mode (User + Consent) sets consent defaults to denied before any tag fires, then sends cookieless pings to Google when consent is denied. These pings feed Google's conversion modeling, which recovers a significant portion of the lost conversion data. Advanced Consent Mode is the recommended approach for most sites because it maintains measurement coverage while respecting user consent.

UniConsent supports both modes. You can configure your preferred mode in the UniConsent dashboard or follow the Basic vs Advanced Consent Mode setup guide.

Consent Mode and Google Tag Gateway

Google Tag Gateway (GTG) serves Google tags from your first-party domain instead of from Google's servers. This improves tag delivery rates but changes the script load order, which can result in "late" consent signals where tags fire before the CMP has set consent defaults.

UniConsent's Advanced Consent Mode is the recommended mechanism for GTG-enabled tags because it sets consent defaults synchronously before any tag can execute, regardless of where the tag is loaded from. If you use GTG, especially via one-click CDN injection (e.g. Cloudflare), see our Google Tag Gateway tutorial for setup instructions.

Consent Mode and Server-Side GTM

Server-side Google Tag Manager routes tag requests through a server-side container rather than firing them directly from the browser. This gives you full control over what data leaves your environment and lets you apply consent checks server-side before forwarding events to Google.

UniConsent works with server-side GTM by passing consent state to the client-side GTM container, which then forwards it to the server-side container. Events are only processed and forwarded when the appropriate consent has been granted.

Consent Mode for Google Analytics 4

Google Analytics 4 relies on Consent Mode to collect data compliantly under GDPR and CCPA. When Consent Mode is active and a user denies analytics_storage, GA4 sends cookieless pings instead of setting cookies. These pings provide basic measurement data (page views, events) without identifying the user, and Google uses them for conversion modeling.

Without Consent Mode, GA4 either fires normally without consent (a compliance risk) or is blocked entirely (losing all measurement for non-consented users). UniConsent's integration ensures GA4 respects user consent while maintaining as much measurement as possible through modeling.

If Google Analytics Tag Diagnostics flags missing consent signals, see our consent signals for Google Analytics guide.

Consent Mode for Google Ads

Google Ads uses Consent Mode to adjust conversion tracking and remarketing behavior based on consent. When ad_storage or ad_user_data is denied, Google Ads sends cookieless pings that feed conversion modeling. When ad_personalization is denied, remarketing audiences are not built for that user.

Without Consent Mode, Google disables personalised advertising and conversion measurement for non-consented users in the EEA, UK, and Switzerland. Implementing Consent Mode through UniConsent recovers conversion data for these users through modeling and maintains your ability to optimize ad campaigns.

Conversion Modeling

When users deny consent, Google's consent-aware tags send cookieless pings instead of setting cookies. Google uses these pings along with machine learning models to estimate the conversions that would have been observed if consent had been granted. This is called conversion modeling.

Conversion modeling helps close the gap between observed conversions and actual conversions. The modeled data appears in your Google Ads and Google Analytics reports alongside observed data, giving you a more complete picture of campaign performance.

Advanced Consent Mode is required for conversion modeling to work. Basic Consent Mode blocks all tags when consent is denied and does not send cookieless pings, so no data is available for modeling.

EEA, UK, and Switzerland Scope

Google's EU User Consent Policy applies to end users located in the European Economic Area (EEA), the United Kingdom (UK), and Switzerland. If your website or app serves users in these regions, you must implement Consent Mode and obtain user consent before using Google's advertising and measurement features.

UniConsent automatically detects the user's region and applies the appropriate consent defaults. For EEA, UK, and Switzerland, all consent types default to denied. For other regions, defaults follow local regulatory requirements. You can configure region-specific behavior in the UniConsent dashboard.