Consent Mode v2 Setup
Consent mode v2, set up the way Google expects.
We wire your cookie banner into Google's consent signals correctly, so your ads and analytics keep working for visitors who say yes, and respect the ones who say no.
- Free to scope, quoted within one business day
- Built to work with the consent banner you already have
- Guaranteed for 30 days, like everything else we build
What we set up
The pieces of a working consent setup.
Consent signal wiring
We connect your cookie banner's yes and no choices to Google's four consent signals, ad storage, analytics storage, ad user data, and ad personalization.
Consent initialization trigger
We set a consent initialization trigger in Google Tag Manager so every tag knows the visitor's choice before it decides whether to fire.
Basic versus advanced mode decision
We help you choose between basic mode, which blocks tags until consent, and advanced mode, which sends limited signals even before a choice is made, based on how much data loss you can accept.
EEA and UK traffic handling
We make sure the setup meets what Google requires for visitors in the EEA and UK to keep receiving personalized ads and remarketing, since Google enforces this at the account level.
What we need, and the proof your tags respect consent.
Access we need
Edit access to Google Tag Manager and to whichever consent banner tool your site uses, plus a way to view the site as a fresh visitor who has not yet made a choice.
What is delivered
A working consent setup wired into your existing banner, a short note on which mode we chose and why, and confirmation your tags respect both a yes and a no answer.
The acceptance test
We load the site as a new visitor, deny consent, and confirm ad and analytics tags either do not fire or send only the limited signal advanced mode allows, then repeat with consent granted.
Out of scope
We do not write your privacy policy or decide what your cookie banner should say. That is a legal question for your own advisor, not a technical one for us.
How the setup runs.
01
Review your current banner
We check what consent tool you already have and whether it can send the signals Google Tag Manager needs.
02
Wire the signals
We connect the banner's choices to the four consent signals and set the initialization trigger so tags respect them.
03
Test both answers
We test the site as a visitor who says yes and one who says no, confirming tags behave correctly either way.
Consent mode v2, answered.
Google's requirement is specifically for visitors in the EEA and the UK, but many sites still get some traffic from those regions even without targeting them. If any EEA or UK visitors reach your site, this protects your account.
Google can restrict how your ads serve to EEA and UK users, and in some cases limit remarketing and personalized ad features across your account, not just for that traffic segment.
Basic mode blocks Google tags entirely until a visitor answers the banner. Advanced mode lets tags send a smaller, cookieless signal even before an answer, which preserves more data but is a more involved setup.
It will not restrict anything for them, since the strict requirement is EEA and UK specific. Some Canadian businesses still choose the same setup as a general good practice around consent under PIPEDA.
Get your consent signals set up the way Google expects.
Let us know which consent tool your site already uses, and a free proposal will be in your inbox within a business day.