Skip to content
TagSentry
Blog

Guide · Setup

Cookie consent on WordPress: what we found on 370 sites

We pressed Reject on 50 WordPress sites and half kept tracking. Why tags beat the consent plugin, how to choose one, and how to check your own site.

Shaun Brown · November 2, 2026 · 7 min read

The short answer

On WordPress, a consent plugin such as Complianz or CookieYes shows the banner, but your tags only wait for the answer if they load after the plugin or are wired to it. We pressed Reject on 50 random WordPress sites and 25 kept tracking, including 14 of the 16 where a Google tag or the Meta pixel sat above the consent plugin. Any of the big plugins can work: check the order in your page source, then check what your browser sends after you press Reject.

A consent plugin shows the banner and keeps a record of each answer. The harder part is getting that answer to your tags, so they wait for a yes. Plugins use three methods: blocking scripts, Google Consent Mode and the WP Consent API.

Blocking means the plugin holds known tracker scripts in your page until the visitor agrees. Google Consent Mode is how a site tells Google Analytics and Google Ads whether they may use cookies. It only speaks to Google's own tags, and Google Consent Mode v2, explained covers its four signals.

The WP Consent API is a free plugin that, in its own words, "standardizes the communication of accepted consent categories between plugins". Your consent plugin writes the answer there, and plugins like Site Kit read it.

A tag that none of these reaches runs as soon as the page loads, whatever the banner says.

What we found on 370 WordPress sites

On 2 November 2026 we took 3,000 random sites from the Tranco list of popular domains, ranked 10,000 to 300,000. Of the 1,833 that answered, 370 ran on WordPress. We read the order of tags in each page, then loaded the 151 with a consent tool in a fresh browser.

If the banner had a Reject button, we pressed it, cleared tracking cookies and loaded the page again. It's the same script we used for our GDPR banner test.

What we sawSites
WordPress sites370
Loading a Google tag279
...with no consent tool at all153
Running a consent tool151
Reject on the banner's first screen, pressed, page reloaded50
Still tracking after Reject25
...with a Google Analytics cookie (_ga or _ga_…) back14
...with Meta's _fbp cookie back7

On 50 of the 151 sites with a consent tool, a Google tag or the Meta pixel loaded above it, with no denied default first. The order made the difference. Of the 50 sites where we pressed Reject, 16 had a tag above the consent tool, and 14 of those kept tracking. On the other 34, it was 11.

The 25 ran 11 different named tools, CookieYes, Complianz and Cookiebot among them, and the same tools ran on sites that held everything. How a plugin was set up mattered more than which plugin it was. We aren't naming the sites, and each page was loaded once per step, so treat this as a snapshot.

Why tags beat the banner

The most common cause is a tag loaded above the plugin. A tag that runs before the consent plugin has loaded can't be held by it. On WordPress that's easy to do by accident.

On the 50 sites (of all 151) with a tag above the consent tool, it was Tag Manager on 30 and a gtag.js snippet on 29 (some had both). Site Kit's tag sat above it on 7, and code from PixelYourSite (5), GTM4WP (5) and MonsterInsights (2) did too.

Google is clear about this: the consent default must come "before any commands that send measurement data", and "the order of the code here is vital. If your consent code is called out of order, consent defaults won't work."

A tag above the plugin is fine if a denied default comes first. Six sites had a Google tag above their consent tool but wrote a Consent Mode default of "denied" before it. That's the order Google asks for.

The other cause is a tracker that isn't Google. Meta's pixel, Microsoft Clarity, LinkedIn and TikTok don't read Google's Consent Mode. They need the plugin's blocking, or a consent setting in Tag Manager. After Reject, a tracker other than Google (Meta, LinkedIn, Microsoft, TikTok and others) still received data on 12 of the 25 sites.

Site Kit is Google's own plugin for adding Analytics and Ads to WordPress. It has a consent mode setting under Site Kit › Settings › Admin Settings. When it's on, Site Kit writes a denied default for the EEA, the UK and Switzerland before its tag. It doesn't show a banner.

Site Kit's own page says "the WP Consent API plugin as well as a consent management plugin must also be installed and configured", and names Complianz, Cookiebot and CookieYes as working with it.

Of the 48 sites running Site Kit, 7 had its consent mode on. The WP Consent API showed up on 8 of the 370 sites.

Choosing a plugin

Most of the big plugins show a banner, record consent and support Google Consent Mode v2, by their own listings. Some put parts of that in a paid version or an account. Where they differ most is setup, price and where your records are kept.

PluginActive installsWorth knowing, from its listing
Complianz1,000,000+Free version includes a cookie scan and script blocking; WP Consent API support
CookieYes1,000,000+Consent Mode v2 (Advanced and Basic); WP Consent API support
Cookie Compliance (Cookie Notice)800,000+Automatic script blocking comes with "Connected mode", which signs you in to its web app
GDPR Cookie Compliance300,000+Built-in integrations for Tag Manager, Google Analytics, Meta Pixel and GTM4WP
WPConsent200,000+Self-hosted; consent logs (Pro) are kept in your WordPress database
iubenda200,000+Detects and blocks common third-party scripts; Basic and Advanced Consent Mode
Cookiebot100,000+Blocks cookies before consent; banner settings by region (paid)
Real Cookie Banner100,000+Content blockers set up per service; ready-made templates in PRO

Install counts are from WordPress.org on 2 November 2026.

Set it up so it works

  1. Turn on the plugin's Consent Mode setting if you run any Google tag. If Site Kit's consent mode is on, Site Kit's page says the consent plugin doesn't need its own Consent Mode features: connect the two through the WP Consent API instead.
  2. Put nothing above the plugin. Open your homepage, choose View page source, and find the plugin's script (search for its name). No googletagmanager.com or fbevents.js line should come before it, unless a gtag('consent', 'default' line with "denied" comes first.
  3. Bring tracking plugins under its control. Site Kit, GTM4WP, MonsterInsights, PixelYourSite and the Meta and WooCommerce pixel plugins add their own tags. Use the consent plugin's integration for each, or the WP Consent API where both support it.
  4. Give non-Google trackers their own consent. Meta, Microsoft Clarity, LinkedIn, TikTok and Hotjar need the plugin's blocking, or a consent setting in Tag Manager.
  5. Exclude consent scripts from caching and optimiser plugins. WP Rocket, Autoptimize, LiteSpeed Cache and Cloudflare's Rocket Loader can delay or merge scripts, and a delayed consent script loses the race. The first three have an exclude list; for Rocket Loader, add data-cfasync="false" to the consent script's tag.

If your tags live in Tag Manager, Google Tag Manager consent mode shows where the default has to go.

Check your own site

  1. Open your site in a private window, from somewhere your banner shows.
  2. Press Reject (or "Deny", "Necessary only").
  3. Open developer tools (F12) › Application › Cookies, delete _ga, any cookie starting _ga_, _gcl_au and _fbp (leave the rest, so your Reject is kept), then reload.
  4. If any of them comes back, a tag ran without your visitor's yes.

For Google's tags, a request can still be fine if it carries denied consent, because Google sends cookieless pings in that state. How to check Consent Mode v2 is working shows how to read the gcs value on each request.

Where TagSentry fits

TagSentry is one line, pasted first in your <head> with a header-code plugin or your child theme. Before any tag runs it sets every Consent Mode signal to denied. Where visitors can opt out, it switches tracking on moments after the page loads, unless they opted out.

When you add it, the Install screen reads your homepage and names any Google tag that loads before our line, such as Google Analytics, and tracking plugins like PixelYourSite, HubSpot or the Meta pixel, with WordPress steps to move them.

Already running Complianz, CookieYes or Cookiebot? Keep it. Our line stands aside, with no second banner, and monitors your events for visitors who accept analytics there (Complianz and CookieYes need their Consent Mode option on). When you're ready, deactivate the plugin first, then choose our banner in Settings › Install straight away, or visitors may see two banners.

The install guide has the WordPress steps, and there are side-by-side looks at TagSentry vs Complianz and TagSentry vs CookieYes. Consent is free up to 10,000 page views a month.

Sources

  1. WordPress.org: Complianz plugin listing
  2. WordPress.org: CookieYes plugin listing
  3. WordPress.org: Cookie Compliance (Cookie Notice) plugin listing
  4. WordPress.org: GDPR Cookie Compliance plugin listing
  5. WordPress.org: WPConsent plugin listing
  6. WordPress.org: iubenda plugin listing
  7. WordPress.org: Cookiebot plugin listing
  8. WordPress.org: Real Cookie Banner plugin listing
  9. WordPress.org: WP Consent API
  10. Site Kit by Google: Consent mode
  11. Google for Developers: Set up consent mode on websites
  12. EUR-Lex: ePrivacy Directive 2002/58/EC (consolidated), Article 5(3)
  13. Cloudflare: Ignore JavaScripts in Rocket Loader
  14. Tranco: a research-oriented top sites ranking