Test a consent interface by observing the website before and after each choice. The presence of an attractive banner does not prove that connected tools respond to a visitor’s preferences.
Before you begin
Use the approved privacy requirements and a fresh browser state for each independent case. Record page, browser, region assumptions, and consent-manager configuration.
What to do
- Load the page without choosing anything and record the tools, requests, and storage present at that point.
- In a separate fresh test, reject optional categories and perform the relevant interactions. Check the behavior against the configured requirements.
- Repeat with acceptance, then with a selected category combination if supported. Confirm only the intended controls change.
- Reopen preferences and change the choice. Check how future requests and storage behavior respond, including embedded tools loaded after the initial visit.
- Test important pages and mobile controls, then record expected results, observed exceptions, and any vendor-specific limitations.
How to check the result
The test record should state which tools were observed in each state. A banner disappearing or a preference being saved is only part of the result. Cookie absence alone does not prove that no data was transmitted.
If you need help
If a tool ignores preferences, identify its installation route before changing rules. Provide the page, choice sequence, and redacted request evidence. Avoid broad claims about legal compliance or complete absence of tracking from a narrow test.
Related help
- Create an inventory of website tracking and embedded tools
- Understand what Google consent mode does in a website setup
Official references
Reviewed October 31, 2026. Interfaces, vendor availability, and account features can change. Check your current account before making changes.
