Consent Checker
Enter your website address and this tool loads it in a real browser, then shows you which ad and analytics tags run before a visitor makes any consent choice. Nothing is clicked on your banner. You see what a first-time visitor's browser does on its own.
What this tool checks
- Ad platforms that fire before consent — Google Ads, Meta, TikTok, LinkedIn, Microsoft, Reddit, Pinterest, and more. If any store data before the visitor agrees, that data reaches the ad platform whether or not they consent.
- Analytics running before consent — Google Analytics and others.
- Google Consent Mode — whether your tags default to denied (correct) or granted (a problem).
- Global Privacy Control — whether a US opt-out signal is respected.
- A consent mechanism — whether a recognised consent banner or a standard consent framework is present at all.
Why tracking before consent matters
Since June 15, 2026, Google Consent Mode's ad_storage signal is the only thing controlling whether data from your Google Analytics tag reaches Google Ads. The old Google Signals backstop is gone. If your tags fire before consent, visitor data flows to ad platforms regardless of the choice they make. (More on that in Google's June 2026 Consent Mode change.)
This is not only an EU concern. California businesses are receiving demand letters under the California Invasion of Privacy Act over tracking pixels that fired before consent. Whether you are covered by GDPR, the UK GDPR, the CCPA, or one of the growing list of US state laws depends on
where your visitors are, which is why you can run this scan as an EU, UK, or California visitor.
How to read your results
- Looks good — nothing identifying ran before a consent choice, or your tags correctly wait in a denied state.
- Worth a look — analytics ran before consent, or tracking is running with no consent banner we could detect. Worth confirming your obligations.
- Needs attention — a consent banner is present but ad tags stored data before consent anyway, or Consent Mode defaults to granted. The mechanism exists and is not doing its job.
How it works
The tool opens your page in a real browser from the region you choose, waits for the page to finish loading its tags, and records every request, cookie, and consent signal that happens before any consent choice. It never clicks your banner and never submits anything. It reflects exactly what a fresh visitor from that region sees.
One limitation worth knowing: if your site blocks automated browsers, the tool will say so rather than guess. And a scan reflects one region at a time, because many sites behave differently for EU versus US visitors.
Fix it automatically
Conversion Bridge sets this up correctly by default. It holds every tag until the visitor agrees, then applies their exact choice to each analytics and ad platform on your site, using your existing cookie banner. If your scan turned up tracking before consent, Conversion Bridge is the no-code way to fix it on WordPress.
Frequently asked questions
Yes. Enter a URL and scan any public website at no cost.
No. It only records what your site does on its own before any consent choice is made. That is the important part: a properly configured site should not track before the visitor agrees.
Many sites show a consent banner or block tracking only for visitors in certain regions. Scanning as an EU, UK, or California visitor shows what each of those visitors actually experiences.
There are hundreds of consent tools and the checker can only recognise so many by name. If your banner uses a standard consent framework it is detected automatically, but a less common tool may not be. The scan still correctly reports what tracking ran before consent, which is what matters.
No. If a tag fires through Tag Manager before consent, the tool sees it the same as any other tag. If Tag Manager correctly holds tags until consent, the tool shows nothing fired. It measures the outcome, not how the tag was delivered.
No. The tool checks client-side tracking before consent, which is the most common problem. It cannot see purely server-side tracking, and compliance depends on more than tracking behaviour. Treat a clean result as a good sign, not legal advice.