USE CASE:
Checking that a cookie banner really blocks tracking
This page is about checking that a cookie banner really blocks tracking: what your options are for consent checks, what each costs, and the one we would use. We are Mamba Labs, we build Apify actors, and Cookie Consent Audit is ours for consent checks.
Last updated November 2, 2026
The problem
The banner looks compliant. The question regulators ask is different: did any tracker fire before the visitor chose, and did reject actually reject? Many sites fail that test without knowing, because the tag manager loads first and the consent tool second. A privacy team or an agency checking client sites needs the answer per domain, from an address inside the EU.
Traditional Search Tools
- Cookiebot or OneTrust scanners. The consent platforms scan the sites they serve. They report what their own banner controls, which is not the same as what actually fired.
- Browser extensions such as Ghostery. Quick for spotting trackers on one page. They do not record before and after consent, and they run from wherever you sit.
- A privacy consultancy audit. Deep, defensible and priced per site. Right for your own flagship domain, heavy for screening a list of prospects or clients.
- Open the site in a clean browser. Use a fresh profile, open developer tools, load the page and read every request before you click anything. Then reject and reload. Thorough for one site and about twenty minutes each.
Mamba Labs Apify Actors
These are the actors we built for this job. If yours is not covered here, search from the bar at the top of the page or contact us here and tell us what you need.
- Cookie Consent AuditRuns from its Apify Store page on your own list.