Consent Mode v2 Basic vs Advanced: Simple Explanation

Basic mode in plain English

In a basic setup, Google tags are usually held back until the visitor gives the relevant consent. This is easier to reason about because optional tags should not run before the choice.

Advanced mode in plain English

In an advanced setup, Google tags may load before consent but behave differently based on the consent state. This can be more complex to verify because some requests may happen before a visitor accepts.

Which one should a small website start with?

Most small teams should start with the setup they can explain and verify. If you cannot clearly test what happens before reject, after reject, and after accept, the setup is too complex for day one.

What CleanCMP focuses on

CleanCMP focuses on a clear banner, visible category-to-signal mapping, GTM and direct install paths, cookie scanning, and proof records. That gives you a practical foundation before deciding whether you need a more advanced tag behavior.

How to verify either setup

Use GTM Preview, Tag Assistant, and browser storage checks. The important thing is not the label basic or advanced. The important thing is whether the actual tags behave as expected for a fresh visitor, reject all, accept all, and reload.

FAQs

Is advanced Consent Mode automatically better?

Not for every website. It can be useful, but it is also harder to understand and verify.

Does CleanCMP force one mode?

CleanCMP helps with the consent layer and mapping. Your final tag behavior depends on how you configure GTM and your Google tags.

What should I test first?

Test a fresh visitor and reject all before testing accept all. That catches most timing and default-state mistakes.