Skip to content

Your cookie plugin says "compliant". Check what the browser does

A green consent dashboard is not a browser test. A 10-minute check in a private Chrome window shows what visitors really get before and after the banner.

Lukas Kontur · · 7 min read

Most consent plugins have a dashboard with a progress bar, a list of cookies and a few green ticks. Once everything is green, it is natural to assume the job is done. But a dashboard checks your settings. It does not watch what happens in a visitor's browser, and that is where tracking either waits for consent or does not.

This post gives you a simple routine: three runs in a private Chrome window, a short results sheet, and what to do with the result. It takes about ten minutes and works for any consent plugin and any website builder.

Why the dashboard and the browser can disagree

A consent plugin can only hold back the scripts it knows about and loads before. Anything that slips past it runs as usual, while the dashboard keeps showing the settings you saved. The vendors are open about this. Complianz's plugin page says: "We cannot guarantee compliance for your website. A correct configuration of this plugin by a website administrator is always required." (WordPress.org: Complianz).

Typical ways a script slips past:

  • a caching or speed plugin that delays, combines or moves the consent script,
  • a pixel added by another plugin, the theme or a pasted snippet,
  • a tag in Google Tag Manager with no consent rule,
  • a cookie set by the server before any script runs.

We go through each of these, with the vendors' own documentation, in My cookie plugin says compliant, but the scan disagrees.

How often does the browser disagree? When we clicked Reject on EU websites, 48.3% of the 22,445 sites with a conclusive test still had non-essential cookies afterwards (reject button study). That covers all consent tools, not one plugin in particular.

Before you start

You need Google Chrome and nothing else. A few rules make the test reliable:

  • Use a private window every time. Your normal window remembers that you accepted the banner months ago. A private window (three-dot menu, "New Incognito window") behaves like a first-time visitor.
  • Close the private window between runs. That throws away its cookies, so each run starts clean.
  • Log out of your website's admin area before you start. Many systems treat logged-in owners differently from visitors.
  • Do not trust an ad blocker. In Chrome, an extension only runs in a private window if you switched on Allow in Incognito for it (Chrome Enterprise Help). If you did that for an ad blocker, switch it off for the test, or it will hide exactly the trackers you are looking for.

Open DevTools with F12 (Mac: Cmd + Option + I) before you type your address, click the Network tab and tick Disable cache (Chrome DevTools: Network reference).

Run 1: load the page and do nothing

  1. In a new private window with DevTools open, load your homepage. Do not touch the banner.
  2. In the Network filter box, type each of these in turn: collect (Google Analytics), facebook (Meta Pixel), tiktok, hotjar, clarity, doubleclick. Write down every filter that shows requests.
  3. Click the Application tab, open Cookies and click your site's address. Write down tracking cookies such as _ga, _fbp or _ttp.
  4. Leave out your consent plugin's own cookie. It stores the visitor's choice and is expected.

If anything showed up, a tracker ran before the visitor had a chance to decide. Click the request and open the Initiator tab: the file name usually tells you which plugin or tag started it.

Run 2: click Reject, then reload

  1. Close the window, open a new private window with DevTools, and load your homepage.
  2. Click your banner's reject button ("Reject all", "Deny", "Decline" or similar).
  3. Clear the Network list with the "clear" icon, then reload the page.
  4. Repeat the filters and the cookie check from run 1.
  5. Open one more page, ideally a product page or the cart, and check again.

Everything you see now was sent or stored after the visitor said no. Cookies that were set before the click may simply be left over; trackers that send new requests after the reload are still running.

Run 3: click Accept

  1. Close the window and open a new private window with DevTools.
  2. Load your homepage and click Accept.
  3. Check that your analytics and ad requests now appear and their cookies are set.

This run matters more than it looks. A setup that blocks everything, even after Accept, costs you the data of every visitor who agreed. If nothing loads after Accept, the plugin blocks a script but never releases it, usually because the script is assigned to a different category than the button the visitor clicks.

Your results sheet

Copy this into a note and fill it in for each run:

RunRequests found (filters)Tracking cookies foundInitiator file
1. No click
2. Reject + reload
3. Accept

A healthy result is: run 1 empty, run 2 empty, run 3 full. The Initiator column is what you hand to whoever maintains your site, or what you search for in your plugin's documentation.

One exception: some sites deliberately load Google tags in "advanced" Consent Mode, where the tags send requests without cookies before consent. If you chose that mode, collect requests in runs 1 and 2 are expected, but _ga cookies are not. Our GTM Consent Mode v2 guide explains the difference.

What to do with the result

If runs 1 and 2 were clean and run 3 was full, your plugin is doing its job on the pages you tested. Keep the sheet; you will want to compare it after the next update.

If something leaked, go to the guide for your plugin:

If your private window was clean but a scan disagrees, look at what was different: another page (a product page, the cart, a blog post), a cached version of the page, or a region-specific banner setting. Clear every cache and run the test again on the page the scan names.

When to repeat the test

A consent setup does not stay fixed on its own. Repeat the three runs:

  • after updating your consent plugin, a caching plugin or any tracking plugin,
  • after changing your theme or adding a code snippet,
  • after publishing a new version of your Google Tag Manager container,
  • before a big campaign, when you add new pixels for ads.

That is a lot of private windows. It is also exactly the kind of check that is easy to forget the week a plugin update goes out.

Check your site in 1 minute

Our free scan runs the same three steps in a clean browser: it records everything before the banner, clicks Reject and reloads, and lists every request and cookie with the file that started it. No signup needed. Run a free scan.

Get alerted when it breaks

With monitoring, we repeat the scan on a schedule and email you when a tracker starts running before consent or keeps running after Reject. The free plan includes one monitored site with a weekly re-scan and email alerts. Create an account and add your site.

Last updated: