Consent before tags: what scanners actually measure
A practical breakdown of pre-consent scripts, Reject All behavior, and why brand-name vendor lists alone are not enough.
Three browser states matter more than one screenshot
A consent banner screenshot cannot prove compliance. What matters is whether non-essential network activity, cookies, and storage appear before a choice, after Reject All, and after Accept All.
ComplianceCheck opens isolated Chromium sessions for each state so leftover cookies from a previous visit do not contaminate the evidence.
Named vendors help; unknown third parties still count
Curated signatures label Google Analytics, Contentsquare, Meta Pixel, and similar tools with human-readable names.
A bundled tracker domain list and a conservative unknown-third-party heuristic catch vendors the catalog has not named yet—without treating every font CDN as a critical fail.
Automation is evidence, not a legal verdict
Geo targeting, login walls, and custom CMP markup can change what automation sees. Treat scan findings as technical signals for remediation and counsel review—not a certificate of compliance.