What is Google Consent Mode?
Google Consent Mode adjusts how Google tags (GA4, Google Ads) behave based on the visitor’s consent choices. When consent is denied it sends cookieless “pings” that let Google model conversions without storing identifiers.
Why Google Consent Mode matters
Consent Mode v2 is effectively required to keep Google Ads audiences and conversion modelling working in the EU. Its presence signals a team keeping up with Google’s consent requirements — but it is frequently mis-wired to the CMP, so the signals never actually reach Google.
Sites using Google Consent Mode
A sample of domains in the TagStack index where Google Consent Mode was detected.
What's usually deployed alongside Google Consent Mode
Share of indexed containers running Google Consent Mode that also run each tool. Based on a sample of the index, so treat these as approximate.
Is your Google Consent Mode set up correctly?
- Default consent state is set before any Google tag fires.
- The CMP updates Consent Mode when the visitor makes a choice.
- Both analytics_storage and ad_storage signals are handled, not just one.
- Consent Mode v2 parameters (ad_user_data, ad_personalization) are present.
See Google Consent Mode on any website
Enter a URL to reveal its full tracking stack — every tag, pixel and consent tool — in seconds. No login or code access required.
Common Google Consent Mode alternatives
Google Consent Mode FAQ
TagStack has detected Google Consent Mode in 56,361 Google Tag Manager containers across its index of 3,278,587 scanned domains. That reflects sites deploying Google Consent Mode through GTM, so sites that install it directly in their source code are not counted.