# Consent mode is configured. Does the website respect the visitor's choice?

Separate permission decisions, banner behaviour and tag configuration, then test accept, reject and changed preferences before approving measurement.

By AdzUp Editorial | 2026-11-21

## Separate the decision from its technical signal

A consent banner, a privacy notice and an advertising tag perform different jobs. A banner presents choices, the business explains its practices, and a technical implementation changes behaviour based on those choices. Seeing a consent setting in a dashboard does not establish that visitors received an appropriate choice or that every script follows it. Ask for evidence of the complete journey rather than a screenshot of one configuration screen.

Google's consent-mode documentation, reviewed on 21 November 2026, describes a mechanism for adjusting tag behaviour. The business remains responsible for obtaining and communicating choices and ensuring tags behave accordingly. This article is an implementation review, not a determination of the legal requirements for a particular business. Have the responsible privacy adviser approve the intended rules before treating technical testing as acceptance.



## Approve the data behaviour before implementation

Google distinguishes basic and advanced consent-mode implementations. Basic mode blocks Google tags until the relevant interaction and consent; advanced mode can load tags with denied defaults and send measurements without cookies. That distinction matters when a team uses the phrase no tracking before consent. Write what the business actually intends to permit before interaction, after rejection and after each available preference choice.

Build a register of analytics, advertising, embedded media, chat and other third-party services on the site. Give each an owner and an approved behaviour. Consent mode does not automatically make every unrelated script follow the same rules. A booking widget added by another team can change the effective website behaviour even when the original analytics implementation remains unchanged and continues to pass its own narrow test.



## Test defaults and updates in a fresh session

Google's implementation guide describes setting defaults before permission is granted and updating the state after the visitor's choice. Its troubleshooting guide identifies issues such as defaults arriving too late or updates failing. Ask the implementer to demonstrate the sequence with the site's actual tag setup. A banner appearing visually before a page finishes loading is not proof that the default state reached the tags first.

Use a written test matrix covering a fresh visit without interaction, rejection, acceptance and a later change of preferences. Test navigation and a return visit as well. Document expected behaviour before recording observations, so the reviewer does not redefine success around what the browser happens to show. Keep test records free of real customer information; synthetic enquiries are sufficient for checking the technical path.



## Keep permission separate from what an enquiry contains

Illustrative example: a counselling provider offers a general contact form alongside appointment enquiries handled by a separate system. The website team tests the consent choices using an invented name and a neutral message. It checks whether form fields, page URLs or analytics events contain information the measurement plan never needed. Agreeing to analytics does not justify collecting every detail a visitor might enter into a form.

This is a hypothetical review, not a description of an AdzUp client's system. For any sector, prefer event names that describe the action without copying the enquiry content. A useful handoff record can say that a form was submitted and which team received it without sending the visitor's message to an advertising platform. Keep the CRM's operational needs distinct from the analytics team's reporting preferences.



## Make acceptance a shared responsibility

The final handover should state the approved implementation approach, responsible owner, tested pages and any unresolved limitations. Include a way for visitors to revisit their choices, then verify that changing a preference updates subsequent behaviour as intended. Google's Tag Assistant can help diagnose Google consent states, but a successful tool result covers only what was actually examined. Review third-party services through appropriate testing rather than assuming they inherit the result.

Repeat the relevant checks when adding a new tag, replacing a banner or introducing a booking provider. Record the change alongside the original approval so future teams can understand the decision. Measurement gaps are not automatically permission to weaken visitor choices, and modelled reporting is not a substitute for that approval. A credible measurement setup explains both what it observes and what it deliberately leaves uncollected.



## Sources

- [Google Tag Platform: Consent mode overview](https://developers.google.com/tag-platform/security/concepts/consent-mode)
- [Google Tag Platform: Set up consent mode on websites](https://developers.google.com/tag-platform/security/guides/consent)
- [Google Tag Platform: Troubleshoot consent mode with Tag Assistant](https://developers.google.com/tag-platform/security/guides/consent-debugging)
