- Separate the outcome of a banner interaction from the observed network behavior.
- Keep failed or uncertain interactions visible as untested.
- Give engineers a reproducible question rather than a legal verdict.
Test the behavior behind the banner
A visible banner does not tell you which services run before a visitor makes a choice. Consent testing compares observations across fresh browsing contexts: no decision, an attempted rejection and an attempted acceptance. The aim is to identify differences worth investigating.
TruCookie’s workflow associates requests, cookie names and interaction evidence with each scenario. An unsuccessful attempt to click a control is not recorded as a successful refusal.
A useful engineering handoff
A finding should identify the tested domain, run time, scenario and observed host or cookie name. This gives an engineer a starting point for reviewing tag configuration, embedded widgets or consent callbacks.
Reproduce the behavior on the authorized site and confirm the intended policy with the relevant owner. A recognized tracking endpoint is a technical signal; its presence alone does not settle legal compliance.
Understand the coverage
A single run cannot establish what every visitor sees. Geography, device, browser, authentication and delayed events can change the result. The current product workflow is based on Chromium and independent scenario contexts, not a complete cross-browser test matrix.
Public customer scanning is not open in this release. Explore the guide to see how to interpret the workflow before connecting a website.