Vendor requests after Reject
After Reject is clicked, the check watches for requests to non-Google tracking vendors. Requests that continue after a refusal suggest the tags do not read the banner.
Free tool · Cookie banner reject test
Does Reject stop tracking on your site?
A Reject button should stop optional tracking. This check clicks Reject on your homepage in a separate pass and records what keeps running afterwards.
What this checks
What the check looks at on one homepage load.
Each item is something the scan records from the browser or reads from your published Tag Manager container.
New tracking cookies after Reject
It also looks for tracking cookies set after the click. A cookie that appears after Reject is a sign that something ignored the choice.
Google consent after Reject
Google tags should send a denied state after Reject. If Google is told consent was granted, the consent setup has a fault that needs fixing.
Whether the banner could be operated
The check tries the banner’s Accept and Reject buttons. If it cannot find or click them, it says so rather than guessing at a result.
What the results mean
How to read a result.
Each result says what the check saw. Some are information, and some are gaps to fix. The gaps from this check are listed first, then any other gaps the scan found.
Tracking still runs after Reject
Non-Google vendors sent requests, or set tracking cookies, after Reject was clicked. Treat this as the first item to fix.
Google is told consent was granted after Reject
A Google request after Reject carried a granted consent state, so Google would treat those visits as consented. Check the consent logic in Tag Manager.
Clicking Accept doesn’t update Google Consent Mode
Accept ran, but no consent update reached Google. Accept and Reject should both change the signal Google receives.
We couldn’t click the banner’s Accept or Reject button
Neither button could be operated, so the reject result is unknown. This is not a pass. Test the banner by hand in a private window.
Nothing continued after Reject
No vendor requests or new tracking cookies were seen after Reject. This covers one homepage load on desktop.
How to fix it
Common fixes for what this check reports.
Each one is a change to your site or your tag setup. Your team decides how to make it.
Make Reject change the tags
Tags for optional tracking need to read the Reject choice. In Tag Manager, set consent on each tag rather than relying on the banner alone.
Map Accept and Reject to real signals
Each button should send a consent update. Reject should send denied states, and Accept should send granted ones only where you intend it.
Remove or move tags that skip consent
Vendor scripts pasted into the site code can ignore the banner. Bring them under the same consent rules, or remove them.
Retest by hand
In a private window, click Reject, then open the browser’s network panel and watch for requests to vendors. Repeat on a few other pages.
Limits
What this check can’t see.
The limits of one homepage load, so you can read the result correctly.
- It clicks Reject once, on one homepage load, on desktop, from one region.
- It reads requests the browser sends. It cannot see data a vendor receives through another route, such as server-side events.
- It cannot test pages behind a login, checkout, or any form.
- If the banner cannot be found or clicked, the result is incomplete, and the check says so.
- Whether a Reject button meets your legal duties is a question for your compliance team, not for this check.
Read more
Guides on the setup this check covers.
Background reading for the same setup, with the steps behind each fix.
Other free checkers
Check the rest of your tracking.
The other free checks run the same scan and list the gaps for their own topic first.
Consent Mode v2 checker
Consent Mode tells Google tags what a visitor agreed to. This check reads the consent signals your homepage sends and flags setups that leave out the v2 settings or set the default too late.
Cookie consent checker
Many sites load ad and analytics tags as soon as the page opens. This check loads your homepage once and records what fires before any choice is made on the banner.
Meta Pixel checker
A Meta Pixel that loads twice, or sends the same page view twice, can inflate the numbers Meta reports. This check counts what your homepage sends to Meta and shows where the Pixel is set up more than once.
Google Ads conversion checker
A Google Ads conversion only counts if a tag sends it to Ads. This check reads how your conversions are set up in your published Tag Manager container and whether they are sent to Google Ads.
GA4 checker
This check looks at what your homepage sends to Google Analytics 4. It flags setups with more than one property, retired Universal Analytics tags, and repeated page views.
Personal data tracking checker
Ad and analytics tags sometimes send personal details inside page addresses or request data. This check looks for categories, such as an email field, and never stores the values. It is built with healthcare and banking sites in mind, but any site can run it.
Google Tag Manager checker
This check reads the published Tag Manager container your homepage loads. It looks at how the container is set up, not only at what reaches the browser.
Lead form attribution checker
When a visitor clicks an ad and fills in a form, the campaign details have to survive the trip. This check follows links to your lead pages and looks for the fields that carry them.
FAQ
Cookie banner reject test: common questions.
Answers to the questions we hear most about this check.
Is this checker free?
Yes. Enter your website and the scan loads your live site and reports what it finds. You see the verdict and how many gaps it found right away; enter a work email to see each gap and what it means.
What does the reject test click?
It clicks the banner’s Reject button in a separate pass, after the normal homepage load. It does not submit forms.
What if the test says it could not click the button?
The result is incomplete. The banner may use a layout the check cannot operate. Test it by hand in a private window.
Does a passing result mean my site is compliant?
No. It means the requests and cookies the check watched did not continue after Reject on that homepage load.
Does this check cover logged-in pages?
No. It loads one homepage on desktop and does not sign in anywhere.
Free Tracking Scan
Find your tracking gaps in about 10 seconds.
Enter your website and we check your live site, then list every gap we find, starting with this check’s. No call needed.