WordPress cookie consent that holds trackers until visitors choose
Add a cookie consent banner to every WordPress site you connect, from one dashboard. Analytics, ad pixels and embeds wait for the visitor's answer, Reject all sits beside Accept all, and every choice is recorded with the banner the visitor saw.
Included on Agency and Scale. A $15 a month add-on on Solo and Studio.
Updated

What is WordPress cookie consent?
WordPress cookie consent means asking visitors before non-essential cookies and trackers run on a WordPress site, then honoring and recording their choice. Analytics tags, advertising pixels and embedded videos have to wait for the answer. A banner that shows a message while those trackers load anyway is a notice, not consent.
WPCentrify runs cookie consent on every WordPress site you connect. It shows a banner with Reject all, Accept all and Manage preferences, holds trackers until the visitor chooses, sends Google Consent Mode v2 signals, lists the third parties each site loads and records every answer with the banner wording that was showing.
WPCentrify cookie consent at a glance
- Holds analytics, ad pixels and embeds until the visitor chooses, including code pasted into the theme header.
- Reject all sits beside Accept all with the same weight, and every category starts switched off.
- Google Consent Mode v2 signals, basic by default, while trackers from other companies are held too.
- Respects Global Privacy Control.
- Records every answer with the banner and policy version that were showing, exportable as CSV.
- Lists the third parties each site loads, by name, and checks the live page from outside.
- Writes privacy policy, cookie policy and terms of use pages from templates.
- Runs on every site you manage from one dashboard, and stands down if another consent plugin is active.
Tested on a real WordPress site
On 8 November 2026 we built a WordPress 7.1.4 site with the Twenty Twenty-Five theme, pasted a Google Analytics 4 tag and a Meta pixel into the header the way most people add them, and embedded a YouTube video on the homepage. Then we visited it as a first-time visitor in a fresh Chromium browser and recorded every request and cookie.

| Visitor action | Google Analytics | Meta pixel | YouTube embed | Cookies set |
|---|---|---|---|---|
| Page opened, no click | Held | Held | Held | None |
| Clicked Reject all | Held | Held | Held | Only the choice cookie |
| Clicked Accept all | Loaded | Loaded | Loaded | _ga, _ga_*, Meta and YouTube cookies |
This is one site, tested by us on our own product, so treat it as an example of the method. You can run the same check on any site in five minutes with our guide to testing a WordPress cookie banner.
What it holds back until visitors choose
Trackers reach a WordPress site in three ways: added by a plugin, pasted into the theme, or loaded later by another script such as a tag manager. WPCentrify holds all three until the visitor accepts the category they belong to.
- Analytics: Google Analytics, Google Tag Manager containers, Microsoft Clarity, Hotjar and similar tools.
- Advertising: the Meta pixel, Google Ads, TikTok, LinkedIn and other ad tags.
- Embeds: YouTube, Vimeo and Google Maps. An embed shows a short note and an Allow and show button instead of loading behind the visitor's back.
- Everything else it recognizes: chat widgets, call tracking and pixels sent with fetch or beacon requests, not only script tags.
What keeps working: carts, logins and form submissions, because they are strictly necessary. Security checks and payment forms such as reCAPTCHA, Cloudflare Turnstile and Stripe are never held back, because a contact form nobody can send is worse than any tracker. If the business relies on a product to run, such as call tracking that swaps phone numbers, you can mark it to always load and the decision is recorded with the reason.
The banner your visitors see
The banner is built to the rules regulators in the EU and UK keep repeating, and the parts that matter most cannot be switched off.
- Reject all and Accept all side by side, with the same weight, on the first layer. There is no setting to make Reject all smaller.
- Manage preferences opens four categories: strictly necessary, functional, analytics and marketing. Everything except strictly necessary starts switched off.
- No close button and no "by browsing you agree". Scrolling, clicking away or pressing Escape is not consent.
- A button on every page to change the choice, so withdrawing is as easy as agreeing.
- Your wording, links, colors, position and width, so the banner matches each site.

The banner carries a small "Powered by WPCentrify" line. Workspaces with White label can hide it.
Google Consent Mode v2, without letting other trackers through
Google Consent Mode tells Google tags whether the visitor said yes. WPCentrify sends Consent Mode v2 signals on every site with the banner switched on, so Google Analytics and Google Ads behave the way the visitor chose.
- Basic mode by default. Google tags do not load until the visitor accepts.
- Advanced mode if you choose it for a site. Google tags load at once and send cookieless pings while consent is denied.
- Everything else is still held. Consent Mode only speaks to Google. Meta, Microsoft Clarity, TikTok and the rest wait for the visitor too.
Our guide explains basic and advanced Consent Mode and why Google Analytics numbers drop when consent works.
A record of every answer
When somebody asks what a visitor agreed to, the answer is in the dashboard.
- Each record holds the time, the choices made, and which version of the banner and policy was showing. It keeps a shortened IP address, not the full one, and no browser details.
- The wording is kept too. Every published version of the banner is stored, so a record can be matched to the exact words the visitor saw.
- Export any time as a CSV file, per site.
- Ask everyone again when you add trackers or change what visitors are agreeing to.
- Answers last 180 days by default, adjustable from 1 to 365 days. The choice cookie is set by the server, so Safari keeps it for the whole period rather than the seven days it allows for cookies written by scripts.
See what each site loads
You cannot ask consent for trackers you do not know about. What's on my site lists the third parties each site loads, gathered from real page views and from checks of the site's pages, and names the product behind each one, such as Google Analytics, Meta Pixel or Microsoft Clarity.
- A third party it does not recognize is shown as a question for you to answer, not ignored.
- Decide which category a product belongs to, or mark it to always load, and the decision is recorded.
- Is it working? checks the live homepage the way a visitor gets it and tells you if anything that should wait is loading early.
Cookies already set, caches and speed plugins
Three things that make consent tools look broken on real sites, handled for you:
- Cookies set before a refusal. When a visitor rejects, the site's own tracker cookies are cleared. No script on any site can delete another company's cookies, such as those on facebook.com, because browsers do not allow it.
- Page caches. A cached page keeps showing the old banner until the cache turns over, so WPCentrify empties the site's page caches whenever the banner changes.
- Speed plugins. Delaying or combining JavaScript can load a banner after the trackers it should stop. The consent script is excluded from those settings in popular speed plugins such as WP Rocket, LiteSpeed Cache and Perfmatters.
Privacy policy, cookie policy and terms, written for you
A banner should link to a cookie policy and a privacy policy, and many sites have neither. From the same Consent tab, WPCentrify writes a privacy policy, a cookie policy and terms of use from templates filled with the business's details, plus a HIPAA Notice of Privacy Practices for US clinics.
- It asks only for the details the chosen documents need.
- Pages are created as drafts by default, so they can be reviewed first.
- A page you already have is never replaced unless you tick it.
- It is guidance, not legal advice, and the screen says so.
Built for anyone who runs more than one WordPress site
Most consent plugins are set up one site at a time, each with its own settings screen and its own records. WPCentrify puts cookie consent beside updates, backups and uptime in the dashboard you use to manage multiple WordPress sites.
| A consent plugin on each site | WPCentrify | |
|---|---|---|
| Where you set it up | In each site's wp-admin | From one dashboard, site by site |
| What to install | A consent plugin per site, kept updated | Nothing beyond the WPCentrify plugin that connects the site |
| Consent records | Inside each site or each vendor account | Per site, in the same dashboard |
| Seeing what each site loads | Per site, in each tool | Per site, from the same dashboard |
| Status across sites | Open each site to check | Beside updates, backups and uptime |
Comparing specific tools? See our best cookie consent plugins for WordPress, and what to check before you switch from CookieYes, Complianz or WP Legal Pages.
What it does not do
- It is not a Google-certified CMP and does not support IAB TCF. Google requires a certified CMP for AdSense, Ad Manager and AdMob publishers serving personalized ads in the EEA, the UK and Switzerland. If that is you, use a certified tool.
- It has no "Do Not Sell or Share" opt-out link. Global Privacy Control is respected, but a separate opt-out flow for US state laws is not built.
- It cannot delete other companies' cookies, because browsers do not let any site do that.
- The live page check reads the page as it arrives. It cannot see trackers that a script adds after the page has loaded, which is what the in-browser test covers.
- It is not legal advice. It gives you the tools and records; which rules apply to a site is a question for whoever handles its privacy compliance.
Pricing
Cookie consent and legal pages are included on the Agency and Scale plans and are a $15 a month add-on on Solo and Studio. Plan prices are still to be revealed. The free plan does not include cookie consent. See pricing for what each plan includes.
How to turn on cookie consent for a WordPress site
- Connect the site. Install the WPCentrify plugin on the WordPress site and connect it to your dashboard. Nothing else needs installing for cookie consent.
- Review what the site loads. Open the site's Consent tab and look at What's on my site. It lists the third parties the site loads, by name, so you can decide how each one is treated.
- Set the banner and Consent Mode. Under What it says, set the wording, links, colors and position. Leave Google Consent Mode v2 on basic unless you have decided advanced mode is right for the site.
- Publish the banner. Publish it. The site's page caches are emptied so visitors get the new banner straight away.
- Check it works. Open Is it working? and check the live page, then open the site in a private window and confirm in DevTools that trackers wait for Accept all.
Questions about WordPress cookie consent
WordPress cookie consent means asking visitors before non-essential cookies and trackers, such as analytics and advertising tags, run on a WordPress site, then honoring and recording their choice. A banner that shows a notice while the trackers load anyway is not consent: the trackers have to wait for the answer.
Yes. It holds analytics, advertising and embed trackers until the visitor chooses, including code pasted into the theme header and scripts added later by other code. On our WordPress test site, Google Analytics, the Meta pixel and a YouTube embed loaded only after Accept all.
Yes. Most tracking code on WordPress sites is pasted into the header as inline code with no file address. WPCentrify recognizes that code and holds it until the visitor accepts, which is what our test site used.
Yes. It sends Consent Mode v2 signals to Google tags, in basic mode by default, with advanced mode available per site. It also holds back trackers from other companies, such as Meta and Microsoft Clarity, which Consent Mode does not control.
Yes. Global Privacy Control is respected by default, and visitors whose browser sends it can still open their choices again from the button on every page.
Yes. A small button on every page reopens the choices, so withdrawing is as easy as agreeing. Cookies the site set for a category the visitor turns off are cleared where the browser allows it.
For 180 days by default, and you can set anything from 1 to 365 days. The choice cookie is written by the server, so Safari keeps it for the full period instead of the seven days it allows cookies written by scripts.
Yes. Every answer is recorded with the time, the choices made and the banner and policy version that were showing, and the records for a site can be exported as a CSV file. Full IP addresses and browser details are not stored.
No. WPCentrify is not a Google-certified CMP and does not support IAB TCF. Google requires a certified CMP for AdSense, Ad Manager and AdMob publishers serving personalized ads in the EEA, the UK and Switzerland, so a site in that position should use a certified tool.
Yes. Carts, logins and payment forms keep working because they are strictly necessary, and security checks such as reCAPTCHA and Cloudflare Turnstile are never held back. Page caches are emptied when the banner changes, and the consent script is excluded from the delay and combine settings of popular speed plugins.
WPCentrify stands down and shows no banner while another consent manager is active, so a site never shows two banners. The dashboard names the other product so you can decide which one to keep.
Yes. It can write a privacy policy, a cookie policy and terms of use from templates filled with the business's details, and a HIPAA Notice of Privacy Practices for US clinics. Pages are created as drafts by default and an existing page is never replaced unless you choose to. It is guidance, not legal advice.
Cookie consent and legal pages are included on the Agency and Scale plans, and are a $15 a month add-on on the Solo and Studio plans. Plan prices are still to be revealed. The free plan does not include cookie consent.
No. WPCentrify gives you the banner, the blocking, the records and page drafts that help you meet privacy rules, but it is not legal advice and does not guarantee compliance. The site owner stays responsible for the final legal position.
Related reading
How to add a cookie consent banner to WordPress
Six steps, a five-minute test, and why a banner can show without blocking.
Read the guideBest cookie consent plugins for WordPress
Nine tools compared on blocking, records, Consent Mode and price.
Read the comparisonCookie consent on 30+ WordPress sites
What went wrong when we fixed consent across client sites after a legal notice.
Read the storyRelated features: traffic analytics, fleet dashboard, white label and how WPCentrify handles GDPR
Turn on cookie consent across every site you manage
Hold trackers until visitors choose, keep a record of every answer and see what each site loads, from one dashboard.
Included on Agency and Scale. A $15 a month add-on on Solo and Studio.