Start free

Does your cookie banner’s “Reject” actually work?

We click your banner’s “Reject all”, reload, and list every tracker and cookie that still loads. Evidence and fixes in about a minute.

  • Free
  • no signup
  • about a minute
Short answer

Paste your store’s address and we open it in a real browser with no cookies, click your own reject button, reload, and record what still fires. If a pixel or analytics tag loads after “Reject”, you see which one, when it fired and the cookie it set, with steps to fix it.

How the test works

  1. 01

    A brand-new visitor

    A real browser with no cookies opens your homepage and records every request and cookie.

  2. 02

    We find your banner

    Even inside frames and shadow DOM. AI reads unusual button wording in any language.

  3. 03

    We click your reject button

    “Reject all”, “Only necessary”, “Refuse”, whatever yours says, then reload.

  4. 04

    We record what still fires

    Every analytics, ad and session-replay request and cookie, with timing and vendor.

What you get back

One page you can send to your developer. Free, no signup, and the top problems show their full evidence.

  • A grade for consent, with what was and wasn’t checked
  • Every tracker after Reject, with the second it fired
  • The request and cookie behind each finding
  • Steps for your consent tool and Tag Manager
2 trackers kept going after Rejectnorthline-shop.example · example
TimeTrackerMoment
3.3sGoogle AnalyticsBefore a choice
4.9sTikTok PixelBefore a choice
+0.8sMeta PixelAfter Reject
+1.2sTikTok PixelAfter Reject
–Google AdsWaited for consent

Why trackers keep firing after “Reject”

In most shops we test, the banner is fine. Something around it skips the consent tool.

  1. 01A tracking snippet hard-coded in the theme, or added by an app or plugin, bypasses the consent tool.
  2. 02Tags in Google Tag Manager fire on “All Pages” instead of a consent trigger.
  3. 03The consent tool is set to “notice only”, or to a different region, so it never blocks anything.
  4. 04The same pixel is installed twice, and only one copy waits for consent.
  5. 05Cookies set before the refusal are never cleared and keep being read.

Questions about this test

Which banners does the test work with?

Any banner a visitor can click. We recognise OneTrust, Cookiebot, CookieYes, Didomi, Usercentrics, Complianz, iubenda, Borlabs and more, and custom banners work too.

What if my banner only shows in some countries?

Our browser uses British English on Central European time. If your consent tool decides by location, the report reminds you to confirm the banner appears for EU and UK visitors.

Does the test change anything on my site?

No. We only visit your public pages like any visitor would. Nothing is installed, and the click only affects our own browser.

Is it really free?

Yes. The free scan checks your homepage with no signup. A free account keeps the report and re-checks it monthly. Pro tests up to 6 key pages a scan and re-checks daily.

More free tools

Last reviewed 28 October 2026 · Sources and method on the methodology page