Compliance verification: proof your banner is respected
Scan your pages while refusing consent, monitor continuously, keep the proof.
The principle
An installed banner proves nothing: what matters is what runs when a visitor refuses. Compliance verification loads your pages in a real browser while refusing consent, then lists everything that still fires: tracker domains contacted, non-essential cookies and storage set, including on a second navigation.
Run a verification
In the app: open a banner → Compliance tab → "Verify now". The "Suggest pages" button proposes up to 5 representative pages (one per template: home, product, article…) — the verdict is per page.
Verdicts: Compliant (no leak), Warnings (non-essential cookies without trackers), Violations (trackers run despite refusal). Cookieless Google Consent Mode pings (gcs=G100) are recognized as compliant and reported separately — a site using Consent Mode correctly is not penalized.
Monitor continuously
Add your pages to recurring monitoring: each page is re-verified automatically, and you get an email (plus your webhooks) if a compliant page starts leaking — a tag added by a marketing team, a site-builder setting re-enabled. A regression never announces itself.
The proof
Every verification is dated and archived: verdict, detected items, a screenshot of the page as measured, and the request log. The dashboard's Scan history gathers results across all your banners. That is your audit evidence.
Good to know
Processing triggered from your server escapes any banner: cover it with the server SDK. And if a tag is injected by your hosting settings (e.g. Webflow's Google Analytics integration), the report tells you — remove it from the settings and let the banner manage it.