How to Implement Consent Mode V2 With Cookiebot CMP

Yes, and the choice determines how you configure every Google tag. Basic blocks tags entirely until consent is given. Advanced lets tags load and adjust their own behavior according to the consent state. The configuration paths diverge from that decision, so it is worth settling before you start editing tags.

Set the tag to require additional consent before loading, choosing the appropriate storage type in its consent settings. Then change the trigger: remove the all pages trigger and use a consent update trigger instead, so the tag only evaluates after the visitor has interacted with the banner.

You leave tags free to fire as normal and set additional consent checks to not set. That sounds like doing less, and functionally it is. The tags carry their own consent logic, so adding a blocking layer on top prevents them sending the cookieless pings that make advanced mode worth using.

Create it as a custom event trigger using the event name your consent platform pushes to the data layer. The platform fires that event automatically whenever someone accepts, declines or saves preferences, so no custom code is needed. It simply has to exist as a trigger before you can assign it.

Yes. A direct script installation needs the consent mode line added inline to enable it. Template-based installations through a tag manager handle this as part of the configuration. Sites that were set up years ago on a direct script are the ones most likely to be missing it.

The consent settings described here are Google's mechanism. Third-party pixels such as Meta, LinkedIn and TikTok need gating behind the consent update trigger rather than relying on built-in consent logic, because they have none. A container correctly configured for Google can still be firing third-party tags without permission.

Advanced, for most sites running meaningful ad spend, since basic mode leaves you with no data at all from visitors who decline. Basic is defensible for a small site prioritizing simplicity. The tradeoff is measurement completeness rather than compliance, as both modes satisfy the legal requirement.

Check each tag in your container's consent overview to confirm it has moved from unconfigured to configured with the right settings. Then use preview mode to watch behavior before and after accepting, verifying Google tags fire in advanced mode while third-party pixels stay blocked until consent.