Google Consent Mode v2, fully supported
Consentify sets all four Google Consent Mode v2 signals by default and updates them the moment a visitor makes a choice. No extra GTM setup, no custom variables, no data loss.
Google Consent Mode v2, fully supported
Consentify sets all four Google Consent Mode v2 signals by default and updates them the moment a visitor makes a choice. No extra GTM setup, no custom variables, no data loss.
What is Google Consent Mode v2?
Google Consent Mode v2 (required since March 2024 for all sites using Google Ads or GA4 in the EU) is a framework that lets Google products adapt their behaviour based on the user's consent state. When analytics consent is denied, GA4 uses modelling to fill gaps. When ad consent is denied, Google Ads stops personalising. Consentify passes all four required signals (analytics_storage, ad_storage, ad_user_data, ad_personalization) automatically.
The four Consent Mode v2 signals
analytics_storageControls GA4 measurement cookies
ad_storageControls Google Ads cookies
ad_user_dataControls sending user data to Google for ads
ad_personalizationControls remarketing and personalised ads
How Consentify implements Consent Mode v2
Default denied on page load
Consentify sets all four signals to 'denied' as soon as the script loads, before the banner appears and before any Google tag Consentify loads. If you use GTM, Consentify loads your container too, so the defaults are always in place before it starts.
Instant update on consent
When a visitor declines, Consentify calls gtag('consent', 'update', ...) straight away. When they accept, the page reloads once and the update is sent before anything else runs, with the correct granted or denied value for each signal.
All four signals covered
analytics_storage, ad_storage, ad_user_data, and ad_personalization are all set correctly, not just the two basic signals. This covers the full Consent Mode v2 specification.
Works with and without GTM
Add your GTM container ID in Consentify, and Consentify loads the container once a visitor has agreed, and pushes a consentify_consent event to the dataLayer, so tags from other vendors can wait for consent too.
Frequently asked questions
Do I need to configure anything in GTM to use Consent Mode v2?
For Google tags, no. Add your GTM container ID in Consentify, and the Google Analytics and Google Ads tags in it follow Consent Mode on their own. Tags from other vendors (Meta, TikTok, LinkedIn, Hotjar) do not read Consent Mode, so in GTM give them a trigger on the consentify_consent event.
What happens to Google Analytics data when consent is denied?
When analytics_storage is denied, GA4 uses Google's modelling (cookieless pings) to estimate traffic, so you still get aggregated insights, just not individual-level tracking. When analytics_storage is granted, full GA4 tracking resumes.
Is Consent Mode v2 required by Google?
Yes, since March 2024 for EEA/UK traffic. Sites using Google Ads conversion tracking or GA4 remarketing that do not implement Consent Mode v2 lose access to those features for users who don't consent. Consentify handles this automatically.
Does Consentify support Google's 'Basic' and 'Advanced' Consent Mode?
Consentify implements Advanced Consent Mode. Signals are set on every page load before tags fire, and updated on consent. This gives Google the most data for modelling while fully respecting user choices.
Check your own site against this
The scan lists the scripts that run before consent, so you know what you actually need to block.
- Results in about 10 seconds
- No account needed
- Shareable report link
Add Consent Mode v2 to your site in 5 minutes
Free forever for one domain. Paste one script tag.
- 1 domain
- 5,000 pageviews/mo
- All integrations
- GDPR, CCPA and ePrivacy