CookieHug regularly visits your site the way a real user does and walks through four consent scenarios — before a regulator, a customer or Google does. The result: one aggregate indicator in your domain dashboard.
Each scenario is a separate, real browser run through your site.
We visit and click nothing. Statistics and marketing trackers must not fire — and tracking cookies must not be written — before the user decides.
The default command must fire before Google tags — we verify this across a dozen subpages, not just the homepage.
We click “Reject all” and browse on: statistics and marketing must stay silent. We also parse gcs signals, so Google's legal cookieless pings don't cause false alarms.
We click “Accept all” and check that GA4 and Ads actually receive granted signals. A banner that blocks measurement permanently loses you data — we catch that too.
Nothing to configure, no audits to remember.
Each scenario refreshes automatically with the nightly scan. You can also trigger any of them manually from the dashboard.
One consent health indicator per domain: either every scenario passes, or you see exactly which one fails and why.
When something's off, you get an email with the specific URLs and problems — not a PDF to analyse yourself.
We detect a consent script delayed or cached locally by plugins like WP Rocket — with a concrete hint on what to exclude from the cache.
The scanner inventories cookies and trackers. Consent health tests behaviour: whether the banner actually blocks before consent and after reject, and unlocks after accept. It's a functional test, not a list.
No. The scenarios run automatically for every domain with the snippet deployed. You see the results in the domain dashboard and can queue any scenario manually.
You get an email alert with the list of pages and problems plus a fix hint. The result and details stay in the dashboard until the next scan confirms the fix.
GDPR- and Consent Mode v2-compliant consent plus an anomaly radar — in a single script.