Google Consent Mode v2, set up in one afternoon
Google Ads and Google Analytics need a consent signal from your cookie banner. Without it, conversions stop being attributed and audiences stop filling in the EEA, the UK and Switzerland. Google calls that signal Consent Mode v2.
One Privacy sends it for you. Install the script or the Google Tag Manager template, publish the banner, and the default and update commands, the CMP developer ID, and the four consent types Google requires are all in place. No gtag code to write.
What Consent Mode does
Before the visitor chooses, One Privacy tells Google tags that storage is denied. When the visitor accepts, it sends an update with the categories they agreed to. Google tags read those signals and adjust what they collect, so measurement keeps working where consent is given and stays off where it is not.
One Privacy sends ad_storage, analytics_storage, ad_user_data and ad_personalization, plus the functionality, personalization and security types, mapped from the banner categories.
Three steps to a working setup
Every step happens in the One Privacy dashboard or in Google Tag Manager. Nothing needs a developer.
- Create an account and add your website. The scanner finds your cookies and sorts them into categories.
- Install One Privacy: paste the script as the first tag in your page head, or add the One Privacy CMP template from the Google Tag Manager gallery on the Consent Initialization trigger.
- Publish the banner. The GDPR (EU) type is preselected and already carries the wording Google asks for. Map your regions with geo rules and you are done.
A banner that meets Google’s requirements
Google asks that a Consent Mode banner explains that data is collected for personalised advertising, links to how Google uses that data, and gives visitors a clear way to accept. The GDPR (EU) banner type does all three out of the box, and every word of it can be changed from the dashboard.
Regions without a banner still measure
Show the banner only where you need consent. For every other region, set a No banner geo rule or a granted row in the Tag Manager template, and Google tags start in the granted state for those visitors. Nothing is lost outside the consent regions.
Check it on your own site
Open your site, open the browser console and run onePrivacy.debug(). The report shows whether the consent default reached your Google tags before they fired, what the update contained, and whether any tag is served through Google tag gateway. If something is late, the report links to the fix.
Support starts with One Privacy
If Google Ads or Analytics report missing consent signals, contact One Privacy support first, not Google. Consent Mode and Google tag issues have their own address, google-support@oneprivacy.io. We look at the report from your site and fix the setup with you, and we work with Google when a problem is on their side.
When you write to us about Consent Mode, add cmp-support-helper@google.com in CC. Google uses that address to improve Consent Mode support across all consent platforms, and it lets Google support step in when needed.
For systemic problems, such as signals missing across many sites, email google-support@oneprivacy.io with a subject line that starts with Escalation. The founder handles escalations and replies the same business day.
Frequently asked questions
Do I have to write any gtag code?
No. The One Privacy script sends the default command before your tags load and the update command after the visitor chooses. With the Tag Manager template, the template sets the defaults inside GTM.
Does One Privacy send the Google CMP developer ID?
Yes. The developer ID is set by the script and by the Tag Manager template, as early as possible on the page, and it is not editable.
Can I run basic consent mode, with tags blocked until consent?
Yes. Gate each Google tag on the one-privacy-consent-updated event in Tag Manager. If you want no Consent Mode commands at all, one option on the page or one checkbox in the template turns them off.
Where do I go when consent signals are missing?
Start with One Privacy support, not Google. Email google-support@oneprivacy.io with the onePrivacy.debug() report from your site and put cmp-support-helper@google.com in CC. We respond within the times listed on the support page.
Scan your site before you decide anything
Run a free scan and compare the cookie list to what your current tool reports. No account, no card.