GOOGLE INTEGRATION
Google Consent Mode V2: your visitors decide, Google's tags follow.
Google Consent Mode V2 passes each visitor's cookie choice to Google tags such as Google Analytics 4 and Google Ads. ConsentBit sends those signals straight from your consent banner, so Google's tags adjust to what the visitor allowed.
Google-certified CMP · IAB Europe registered CMP (ID 502) · Works on Webflow, Framer, WordPress and any website builder
Visitor accepts Analytics only
consent updateEvery banner choice is sent to Google as a consent update.
ad_storage, analytics_storage, ad_user_data and ad_personalization, set from one click.
Google's rule for European traffic, not a law.
Consent Mode is Google's own requirement. If you use Google Ads or Google Analytics with visitors in the EEA, Google requires consent signals to keep measurement, ad personalization and remarketing working. Google's EU user consent policy also covers the UK and Switzerland. Version 2 added two new signals for advertising.
Required signals
4 signals
ad_storage, analytics_storage, ad_user_data and ad_personalization.
Required since
March 2024 (EEA)
Since 15 June 2026
Consent Mode is the single control for Google Ads cookies and IDs collected through Google Analytics.
Five things Google expects from your consent setup
Each requirement in plain terms, next to how ConsentBit covers it.
How a choice reaches Google, step by step
Consent Mode works in two moments: a default when the page loads, and an update when the visitor chooses.
The page loads
ConsentBit sets the default. For visitors who see the GDPR banner, every signal starts as denied.
The visitor chooses
Accept all, Reject all, or open the preferences panel to pick categories.
ConsentBit sends the update
Each banner category switches its Google signals to granted or denied.
Google's tags adjust
Google Analytics and Google Ads change what they store and use, based on the signals they receive.
One banner choice. The right Google signals.
Visitors choose between four familiar categories. ConsentBit translates each one into the signals Google's tags understand.
Google requires the first four signals (ad_storage, analytics_storage, ad_user_data, ad_personalization). The other three are optional.
Basic or Advanced: what Google gets before a visitor chooses
Google offers two ways to set up Consent Mode. The difference is what happens before the visitor clicks anything.
ConsentBit supports both. Advanced is the default: Google tags load with consent set to denied and can send cookieless pings, which lets Google use its more detailed, advertiser-specific conversion modeling. In Basic mode, Google tags stay blocked until the visitor agrees.
Defaults depend on the visitor
Visitors who see the GDPR banner start with every signal denied. US visitors start with signals granted, and they switch to denied if the visitor opts out.
Works with IAB TCF too
If you use ConsentBit's IAB TCF banner, the visitor's TCF choice is passed on to Consent Mode as well, so Google's tags follow the same decision.
Visitors who see the GDPR banner start with every signal denied until they choose.
Try ConsentBit with your Google tags, free.
Set up ConsentBit for Google in 4 steps
Four steps, from a new account to a setup you can verify yourself.
Create your account
Add your site in the ConsentBit dashboard and copy your Script ID.
Install ConsentBit first
Add the ConsentBit script as the first script in your <head>, above your Google tags. Or add the ConsentBit CMP template in Google Tag Manager, on the Consent Initialization trigger.
Choose Basic or Advanced Consent Mode
Advanced is the default: Google tags load with consent set to denied. In Basic mode, Google tags don’t load at all until the visitor agrees.
Apply the banner template and check your setup
Apply the Google Consent Mode banner template, then open your site with ?consentbit_debug=1 to confirm the consent default loads before your Google tags.
Since June 2026, your consent signal decides what Google Ads gets
On 15 June 2026, Google made Consent Mode the single control for the Google Ads cookies and IDs collected through the Google Analytics tag. That makes an accurate consent signal more important than before.
If the consent signal is wrong, the data Google Ads receives is wrong too. ConsentBit sends it from the visitor's actual choice.
FAQ
Consent Mode V2 questions, answered
Short answers to what website owners ask most.
It's a Google requirement, not a law. If you use Google Ads or Google Analytics with visitors in the EEA, Google requires consent signals to keep measurement, ad personalization and remarketing features working for those visitors. Google's EU user consent policy also covers the UK and Switzerland.
Google won't receive the consent signals it needs for visitors in the EEA. That puts Google's measurement, ad personalization and remarketing features at risk for those visitors, so your remarketing audiences and conversion reports in Google Ads can become less complete.
Version 2 added two signals: ad_user_data, which controls whether user data can be sent to Google for advertising, and ad_personalization, which controls personalized advertising such as remarketing. The original signals, ad_storage and analytics_storage, are still used.
No. Consent Mode doesn't ask visitors anything. It takes the choice a visitor makes in your consent banner and passes it to Google's tags. You still need a banner, such as ConsentBit, to collect that choice.
Google's requirement covers visitors in the EEA, and its policy also covers the UK and Switzerland. ConsentBit still sends signals for US visitors: they start as granted and switch to denied if the visitor opts out through the banner.
(Link "Read our CCPA guide" once the CCPA page is live)
Google Tag Assistant shows the default and updated consent states as your page loads and as a visitor makes a choice. Google Analytics 4 also has a consent settings view that shows whether consent signals for measurement and ad personalization are active.
ConsentBit also has a debug mode: add ?consentbit_debug=1 to your page address to see whether the consent default loaded before your Google tags.
No. Consent Mode passes a visitor's choice to Google's own tags. IAB TCF is an industry framework that shares consent with ad-tech vendors, and Google requires a certified CMP using TCF for publishers who show ads through AdSense, Ad Manager or AdMob in Europe. ConsentBit supports both and passes the TCF choice on to Consent Mode.
(Link: "IAB TCF" → https://www.consentbit.com/iab-tcf)
Yes. ConsentBit has a free plan, and every paid plan comes with a 14-day free trial. See pricing for what each plan includes.
(Link: "See pricing")
Is Google Consent Mode V2 mandatory?
It's a Google requirement, not a law. If you use Google Ads or Google Analytics with visitors in the EEA, Google requires consent signals to keep measurement, ad personalization and remarketing features working for those visitors. Google's EU user consent policy also covers the UK and Switzerland.
What happens if I don't use Consent Mode V2?
Google won't receive the consent signals it needs for visitors in the EEA. That puts Google's measurement, ad personalization and remarketing features at risk for those visitors, so your remarketing audiences and conversion reports in Google Ads can become less complete.
What's the difference between Consent Mode V1 and V2?
Version 2 added two signals: ad_user_data, which controls whether user data can be sent to Google for advertising, and ad_personalization, which controls personalized advertising such as remarketing. The original signals, ad_storage and analytics_storage, are still used.
Does Consent Mode V2 replace a cookie banner?
No. Consent Mode doesn't ask visitors anything. It takes the choice a visitor makes in your consent banner and passes it to Google's tags. You still need a banner, such as ConsentBit, to collect that choice.
Do I need Consent Mode V2 for US visitors?
Google's requirement covers visitors in the EEA, and its policy also covers the UK and Switzerland. ConsentBit still sends signals for US visitors: they start as granted and switch to denied if the visitor opts out through the banner.
(Link "Read our CCPA guide" once the CCPA page is live)
How do I check that Consent Mode V2 is working?
Google Tag Assistant shows the default and updated consent states as your page loads and as a visitor makes a choice. Google Analytics 4 also has a consent settings view that shows whether consent signals for measurement and ad personalization are active.
ConsentBit also has a debug mode: add ?consentbit_debug=1 to your page address to see whether the consent default loaded before your Google tags.
Is Consent Mode V2 the same as IAB TCF?
No. Consent Mode passes a visitor's choice to Google's own tags. IAB TCF is an industry framework that shares consent with ad-tech vendors, and Google requires a certified CMP using TCF for publishers who show ads through AdSense, Ad Manager or AdMob in Europe. ConsentBit supports both and passes the TCF choice on to Consent Mode.
(Link: "IAB TCF" → https://www.consentbit.com/iab-tcf)
Is there a free trial?
Yes. ConsentBit has a free plan, and every paid plan comes with a 14-day free trial. See pricing for what each plan includes.
(Link: "See pricing")
Related reading
Connect your consent banner to Google's tags
ConsentBit sets the default before Google's tags run, sends an update the moment a visitor chooses, and keeps a record of every choice.
This page is a general overview of Google Consent Mode, not legal advice. Consent Mode is Google's requirement for its own products. It doesn't replace your obligations under privacy laws such as GDPR.