Fundamentals
Cookie banner and Consent Mode v2: what each does
Understand the visitor interface, Google signal layer and tracker controls so a visible banner becomes an enforceable choice.
In brief
The banner asks and stores a choice; Consent Mode passes Google-specific state; blocking controls what may execute.
The banner is the visitor interface
A banner explains purposes, offers choices and lets visitors revisit them. Its presence says nothing about whether a script already ran. It must connect to the site's enforcement logic and remember choices according to your policy.
When choosing the visitor interface, review the Consentory cookie consent banner workflow; verify its signal updates and enforcement separately.
Consent Mode is a Google signal layer
Consent Mode sends the four consent states used by supported Google tags. It does not classify every cookie or make independent third-party tags obey the visitor's choice. Google tags may behave differently when consent is denied, especially in Advanced mode.
Blocking is the execution layer
Prior blocking keeps optional scripts, pixels or embeds from running before the relevant permission. It is required for Basic-mode behavior with Google tags and for vendors that do not listen to Google's signals. Blocking must happen before the first request, not after the banner renders.
Follow one analytics-only choice
The visitor chooses Analytics but declines Advertising. The banner records that choice. The integration sets analytics_storage to granted and the three advertising signals to denied. Enforcement lets permitted Analytics behavior proceed while advertising and unrelated optional tags remain controlled by their own rules.
Test the complete chain
Inspect the visible choice, the saved preference, Tag Assistant consent values, the tag firing timeline and browser requests. A mismatch at any layer means the implementation is incomplete, even if a single dashboard reports success.
Try it
Explore the three layers
Collects and stores the visitor's purpose-level choice. It should offer a way to change that choice.
Continue with a related guide
Primary sources
Reviewed 15 October 2026. Validate product interfaces and requirements for your own implementation.
Check the implementation on your site
Consentory helps teams inspect trackers, configure prior blocking and document consent choices. The guides above give you a test plan before rollout.