My cookie plugin says compliant, but the scan disagrees
Your WordPress consent plugin shows a green dashboard, yet a scan finds trackers before consent. Why both can be true, and which one to trust.
Lukas Kontur · · 8 min read
You set up a consent plugin on your WordPress or WooCommerce site. The dashboard shows a full progress bar, the cookie scan lists every cookie neatly in a category, and the banner appears. Then a scan report says that Google Analytics or the Meta Pixel runs before anyone clicks the banner. Who is right? Usually both: they measure different things. This guide explains what each one checks, the six most common reasons they disagree, and a ten-minute browser test that shows you what your visitors actually get.
The symptoms
- Your consent plugin's dashboard looks complete, but a scan reports trackers before consent, analytics cookies before consent (
_ga) or marketing cookies before consent (_fbp,_ttp). - The plugin's own cookie scan lists
_gacorrectly as "statistics", yet the scan report says it was set before the banner was answered. - You open your own site and see no problem, but a customer, an agency or a scan does.
This is common. In our scan of 97,304 EU websites, 31.1% set analytics cookies before the visitor made any choice, and 18.3% set marketing cookies (full study). Most of those sites had some kind of banner.
What your plugin's dashboard measures
A plugin dashboard tells you whether you finished the setup. Complianz, for example, says its dashboard "shows your progress in completing all tasks that Complianz lays out for you" (Complianz: why can't I reach 100%). That is a checklist of settings, documents and answers, not a test of what the browser does.
The vendors say this themselves. Complianz's plugin page states: "We cannot guarantee compliance for your website. A correct configuration of this plugin by a website administrator is always required." (WordPress.org: Complianz). The CookieYes plugin page says that installing the plugin alone does not make your site compliant (WordPress.org: CookieYes).
What your plugin's cookie scan measures
The built-in cookie scan finds cookies so that you can describe and categorise them in your banner and cookie policy. It answers "which cookies exist on my site?", not "which cookies are set before consent?". It also has limits that the vendors document:
- Complianz has a local scan that "loads your site's pages (including homepage, login, etc.) in the background" and a cloud scan that checks "your homepage only" (Complianz: troubleshooting services and cookies).
- CookieYes scans up to your plan's page limit and "will scan only the first set of identified URLs". Cookies on pages beyond the limit are not detected and not blocked (CookieYes: pages per scan).
- Cookiebot crawls your site once a month on its standard plans, and the free plan covers up to 50 subpages (Cookiebot pricing).
A cookie that is listed and categorised correctly can still be set too early. Listing it is step one; blocking it until consent is a separate job.
What a browser scan measures
A behaviour scan, like ours, opens your site as a brand-new visitor in a clean browser, records every request and cookie before the banner is answered, then clicks Reject, reloads and records again. It does not read your settings. It only sees what the browser receives. That is why it can disagree with a dashboard that is 100% complete.
Why they disagree
The causes we see most often on WordPress sites:
- A caching or optimisation plugin changes the page. Minify, combine, delay and defer features can move the consent script behind your trackers, or serve a page that was cached before you changed a setting. Complianz warns that "cached scripts may serve an outdated version of the banner" (Complianz: caching and optimisation plugins).
- A script the plugin does not recognise. Consent plugins block services they know. A pixel added by another plugin, by your theme or by a code snippet can pass straight through.
- Google Tag Manager fires the tags. The plugin may hand the decision to GTM correctly, but a tag in the container without a consent rule fires anyway. See our GTM Consent Mode v2 guide.
- The cookie comes from the server. A plugin can set a cookie in the page's response headers before any script runs. No browser-side blocking can stop that. Our Meta Pixel on WooCommerce guide shows a real example.
- The banner behaves differently by region. With geolocation switched on, plugins show different banners or none at all depending on where the visitor is. Complianz documents this under Settings, General, GEO IP (Complianz: geolocation); CookieYes under Cookie Banner, General, Geo Target Banner (CookieYes: banner in specific regions). A scan from one country can see something you never see from another.
- Your own browser is not a new visitor. You accepted the banner months ago, you are logged in as an administrator, or an ad blocker hides the trackers. Complianz even asks you to disable ad blockers for its own scan, because they "prevent cookies from being placed" (Complianz: cookie scan results). Your normal browser window is the worst place to test.
How to check it yourself
Ten minutes, stock Chrome, no extensions.
- Log out of WordPress, then open a new private window (three-dot menu, "New Incognito window"). Private windows start without your cookies, and extensions only run there if you allowed them.
- Press F12 to open DevTools and click Network. Tick Disable cache (Chrome DevTools: Network reference).
- Load your site. Do not touch the banner.
- Type these into the filter box, one at a time:
collect(GA4),facebook,tiktok,hotjar,clarity. Anything listed was sent before consent. - Open Application, Cookies and your site's address. Look for
_ga,_fbp,_ttpand similar. Your consent plugin's own cookie (for examplecmplz_cookies orcookieyes-consent) is expected; it stores the choice. - For each request you found, click it and open the Initiator tab. The file name usually points to the cause: a folder under
wp-content/plugins/,googletagmanager.com/gtm.js, or a combined file from a caching plugin. - Click the first request in the list (your page itself, with the filter cleared) and check Response Headers for
Set-Cookielines that set tracking cookies. Those come from the server. - Click Reject (or "Deny"), clear the Network list, reload and repeat steps 4 and 5. Nothing new should appear.
- In a fresh private window, click Accept and check that your analytics and ads do load. A setup that blocks everything forever is broken too.
If your result matches the scan, trust the scan and move on to the fix. If your private window is clean but the scan is not, compare what differs: the page you tested (try a product page and the cart), the region, or a cached version. Clearing every cache and testing again often explains it.
The fix
Match the cause you found to the guide for your plugin:
- Complianz: Complianz not blocking GA4 or Meta Pixel, and if cookies stay after Deny, Complianz: Reject clicked, but the GA4 cookies stay.
- CookieYes: CookieYes not blocking cookies before consent.
- Cookiebot: Cookiebot: visitors click Deny, but tracking continues.
- Pixels added by WooCommerce plugins: Meta Pixel fires before consent on WooCommerce.
- Tags in Google Tag Manager: Google Consent Mode v2 in GTM: the five mistakes that leak data.
Whatever the plugin, the same three habits help:
- Exclude the consent plugin's script from every minify, combine, delay and defer feature, then clear all caches.
- Keep one copy of each tracker. If GA4 or a pixel is added by two plugins, or by a plugin and GTM, remove one.
- Re-run the private-window test after every plugin, theme or GTM change. Your dashboard will not turn red when an update changes the order in which scripts load.
How to verify the fix
Repeat the test in a new private window for each run:
- No click: none of the filters show requests, and no tracking cookies are listed.
- Reject, reload, then a product page and the cart: still nothing.
- Accept: your analytics and ad requests appear, and their cookies are set.
Then run a scan again and check that the finding is gone. If you use our WordPress plugin, the new score also shows in your WordPress dashboard.
Background: Pre-consent tracking explained.
Check your site in 1 minute
Our free scan loads your site as a new visitor, records what happens before and after the banner, and shows the exact request or cookie that leaked. No signup needed. Run a free scan.
Get alerted when it breaks
A dashboard stays green when a plugin update quietly breaks blocking. With monitoring, we re-scan your site on a schedule and email you when tracking before consent appears. The free plan includes one monitored site with a weekly re-scan and email alerts. Create an account and add your site.
Last updated: