CookieBoss – Cookie Consent & GDPR Compliance

Description

A free GDPR cookie banner that works the moment you activate it. Your visitors see a consent banner in your site’s language with Accept, Reject and Manage choices, Google Consent Mode v2 is set before your Google tags load, and WooCommerce cart and checkout keep working. No account, no setup, and the default banner is served from your own site without contacting any outside service. It is one small deferred script. CookieBoss is a Cookiebot alternative run by an EU company: start without an account, and connect one when you want cookie scanning, your own banner design and consent statistics.

Free, without an account

  • Banner live on activation. Accept All, Reject All and Manage Preferences on the first layer, with per-category choices (analytics, marketing, functional).
  • Your site’s language. The banner follows the language of each page, in 53 languages, and falls back to English.
  • Google Consent Mode v2. All consent types are denied by default before any Google tag runs, then updated when the visitor chooses. URL passthrough and ads data redaction are optional.
  • Blocking Mode (optional). Holds back known tracking scripts, such as Google Analytics, Meta Pixel and Hotjar, until the visitor consents to their category.
  • WooCommerce. Cart and checkout keep working: WooCommerce’s own cookies are treated as necessary and payment gateway scripts are never blocked. Scripts from known WooCommerce marketing and analytics extensions are tagged with their consent category.
  • Cookie & script scanner in WordPress. Checks your front page for known tracking scripts and cookies and suggests a category for each.
  • Consent Preferences block. Add it to your privacy policy page so visitors can change their choice at any time.
  • Admin Preview. Hide the banner for yourself while you edit; visitors still see it.
  • Nothing leaves your site. The default banner makes no external requests. The visitor’s choice is stored in a first-party cookie on your domain.

What connecting a CookieBoss account adds

The “Connect to CookieBoss” button links a free account in one click (sign in or sign up in a popup, no credit card). Your site then loads its own banner, compiled for your settings, from the CookieBoss CDN.

  • Your own banner design: bottom bar, modal or preference center layout, your colours and your texts.
  • Cookie scanning from CookieBoss servers, with the cookies it finds listed and categorised for your cookie declaration.
  • Consent statistics in the CookieBoss dashboard: banner views, consent rate, Accept All and Reject All.
  • Switching made easier: import wizards in WordPress bring your configuration over from Cookiebot or Cookie Information.

Paid plans start at €9/month and add more banner languages, more frequent scans and removal of the “Powered by CookieBoss” link. From the Pro plan: geo rules (opt-in for EU visitors, other rules where the law allows them) and Google Consent Mode v2 verified on your live site. From the Business plan: A/B tests of banner variants, measured on your own traffic with significance testing, so you can raise your consent rate within the law. Plans and limits are at cookieboss.io/pricing.

Compliance by design

  • Reject is as easy as Accept. Reject All sits on the first layer, next to Accept All, in the same style.
  • Nothing is pre-ticked. Analytics, marketing and functional are off until the visitor turns them on.
  • Nothing is stored before a choice. The banner writes its consent cookie only after the visitor accepts, rejects or saves preferences, and sets no visitor ID before then.
  • Consent expires. By default, visitors are asked again after 12 months.

A banner is one part of compliance. You still need a cookie policy that lists the cookies your site uses; the CookieBoss scanner helps you build that list.

Languages

The banner text ships in 53 languages, including all 24 official EU languages, and follows each page’s language automatically. With a connected account the banner uses the languages you set up in the dashboard: one on the free plan, as many as you need on paid plans. The plugin’s admin screens can be translated through translate.wordpress.org.

Automatic script blocking

When Blocking Mode is on, the plugin rewrites the script tags of known tracking services so they don’t run until the visitor consents:

  • Analytics: Google Analytics, Google Tag Manager, Hotjar, Matomo, MonsterInsights, ExactMetrics, Site Kit
  • Marketing: Meta (Facebook) Pixel, Pinterest Tag, TikTok Pixel, LinkedIn Insight, Google Ads, X (Twitter) UWT
  • Functional: HubSpot, Intercom, Drift, Crisp, LiveChat

Scripts loaded through WordPress’s script system are recognised by their handle or source URL. Code pasted straight into a theme or a header/footer plugin is not rewritten; give such a script type="text/plain" and data-cookieconsent="analytics" (or marketing, functional) and the banner runs it after consent.

See the “External services” section below for the CookieBoss endpoints this plugin contacts.

External services

Before you connect an account, the plugin uses its bundled default banner (assets/js/consent-local.js), served from your own site. It contacts no external service: no geo lookup, no analytics, no CookieBoss request of any kind. The visitor’s choice is stored in a first-party cookie on your domain.

After you connect a CookieBoss account, the plugin uses the CookieBoss service (cookieboss.io), operated by Transformination OÜ. It contacts these CookieBoss endpoints:

  • cdn.cookieboss.io — serves your consent banner script (loaded on every page; your Site ID is part of the script URL). Also contacted from your server to verify your Site ID when you click Verify in the settings.
  • a.cookieboss.io — receives consent events when a visitor interacts with the banner: the choice made, the page path, and a random visitor ID that the banner stores only after the visitor’s choice. Used for your consent statistics.
  • api.cookieboss.io — OAuth authentication calls (token exchange, token metadata, token revocation) when you connect or disconnect the plugin, and consent-analytics API calls for the admin dashboard widget (your Site ID and API key are sent to retrieve aggregate consent statistics).
  • app.cookieboss.io — the CookieBoss sign-in and authorization page, opened in a browser popup when you use the one-click “Connect to CookieBoss” flow.

The banner sends no names, email addresses or form contents to these services.

The plugin also contains lists of well-known third-party domains (for example googletagmanager.com, connect.facebook.net, maps.googleapis.com). These are detection signatures used to recognize tracking scripts already present on your site so they can be held back until consent — the plugin never contacts these domains itself.

Use of the CookieBoss service is subject to its terms and privacy policy:

  • Terms of Service: https://cookieboss.io/terms
  • Privacy Policy: https://cookieboss.io/privacy

Screenshots

Installation

  1. In WordPress, go to Plugins Add New, search for “CookieBoss” and click Install Now, then Activate.
  2. The consent banner is now live on your site, and a short setup wizard opens.
  3. Wizard step 1: check the recommended settings (Google Consent Mode v2 on, Blocking Mode off, Admin Preview on) and click Save & Continue.
  4. Wizard step 2, optional: click “Connect to CookieBoss” to link a free account, or choose “Maybe later: keep the default banner”.
  5. Wizard step 3 shows your site with the banner. You can change everything later under Settings CookieBoss.

To install manually, upload the plugin folder to /wp-content/plugins/ and activate it on the Plugins screen.

FAQ

Do I need an account?

No. Without an account the plugin shows its default banner: opt-in for every visitor, in your site’s language, with Google Consent Mode v2 and optional Blocking Mode, and nothing sent outside your site. Connect a free account (cookieboss.io/signup, no credit card) when you want your own banner design, cookie scanning and consent statistics.

Is it free?

Yes. The plugin and the default banner are free with no time limit. A free CookieBoss account covers one site; its banner uses one language and shows a small “Powered by CookieBoss” link. Paid plans start at €9/month for more languages, more frequent scans and no link; multi-domain plans start at €19/month. See cookieboss.io/pricing.

Does it support Google Consent Mode v2?

Yes, with or without an account. The plugin sets the Consent Mode v2 default state (all consent types denied, security_storage granted) in the page head before any Google tag loads, and the banner sends the update when the visitor chooses. Google requires Consent Mode v2 to use Google Ads measurement and personalisation for visitors in the EEA. Turn it off under Settings CookieBoss if you set Consent Mode defaults elsewhere, for example in Google Tag Manager.

Does it work with WP Rocket and other caching plugins?

Yes. Page caching is no problem: the banner decides what to show in the visitor’s browser, so a cached page works for everyone. The consent script and the Consent Mode defaults also carry the attributes that caching and optimisation plugins use to leave a script alone (data-cfasync=”false”, data-no-optimize, data-no-minify, data-no-defer, data-noptimize). LiteSpeed Cache, Autoptimize, SiteGround Optimizer and Cloudflare Rocket Loader respect these.

If a “delay JavaScript” setting still holds the banner back, exclude it by hand. Use the keyword cookieboss, which matches the script both before connecting (served from your site) and after (served from cdn.cookieboss.io), and wait_for_update, which matches the Consent Mode defaults:

  • WP Rocket — File Optimization: add both keywords to “Excluded JavaScript Files” and to the “Delay JavaScript execution” exclusions.
  • LiteSpeed Cache — Page Optimization JS Settings: add both to “JS Excludes”, and to “JS Deferred / Delayed Excludes” if enabled.
  • W3 Total Cache — Performance Minify: add the CookieBoss script to “Never minify the following JS files”.
  • Autoptimize — JavaScript Options: add cookieboss, wait_for_update to “Exclude scripts from Autoptimize”.

This matters: the banner and the Consent Mode defaults must run before other scripts to hold cookies back.

Is my data stored in the EU?

Without an account, there is no data to store: the banner runs on your site and the visitor’s choice stays in a cookie in their browser. With a connected account, consent data is stored on Cloudflare with the database region-pinned to the EU (Western Europe). The service is operated by Transformination OÜ, a company registered in Tallinn, Estonia, which acts as your data processor; a Data Processing Agreement is available. The banner script itself is delivered from Cloudflare’s global network so it loads fast everywhere.

How is this different from Cookiebot or CookieYes?

All three put a consent banner on your site and support Google Consent Mode v2. What sets CookieBoss apart:

  • The banner works without an account, and the default banner makes no external requests at all.
  • Connected sites load a script compiled for their own settings, so visitors download only what that site uses.
  • It is run by an EU company, with consent data stored in the EU.
  • Its focus is your consent rate within the law: consent statistics on every account, and A/B tests of banner variants with significance testing on the Business plan.
  • If you already use Cookiebot or Cookie Information, the plugin’s import wizards bring your configuration over.

Which suits you best depends on your site; you can try CookieBoss without an account and keep your current tool running until you switch.

Will it slow down my site?

The script loads with defer, so it does not block page rendering. The default banner is a single file served from your own site: about 30 KB compressed, most of which is the banner text in 53 languages; WordPress.org requires plugin code to be human-readable, so it is not minified. A connected site loads a minified script compiled for its own settings and languages, typically around 10 KB compressed.

What does Blocking Mode do?

When enabled, the plugin prevents known tracking scripts (Google Analytics, Meta Pixel and others) from running until the visitor consents to the relevant category. It changes their script type to text/plain and adds a data-cookieconsent attribute; the banner restores them after consent.

Where do I find my Site ID?

You don’t need one: “Connect to CookieBoss” sets it for you. To enter it by hand, log in to app.cookieboss.io, open your site, and copy the Site ID from the Installation Script section.

Can I hide the banner while editing my site?

Yes. Enable “Admin Preview Mode” in the settings to hide the banner and unblock all scripts when logged in as an administrator. Visitors still see the banner normally.

Can I customize the banner design?

The default banner uses a neutral bottom-bar design. To change layout (bottom bar, modal, preference center), colours, texts or animations, connect a free account and edit the banner in the CookieBoss dashboard.

What is URL passthrough?

URL passthrough passes ad click information (gclid, dclid) through page URLs even when ad_storage consent is denied. This improves Google Ads conversion modeling without setting cookies.

What is ads data redaction?

When enabled, ad click identifiers are removed from network requests when ad_storage consent is denied. This provides stricter privacy but may reduce conversion modeling accuracy.

Reviews

There are no reviews for this plugin.

Contributors & Developers

“CookieBoss – Cookie Consent & GDPR Compliance” is open source software. The following people have contributed to this plugin.

Contributors

“CookieBoss – Cookie Consent & GDPR Compliance” has been translated into 3 locales. Thank you to the translators for their contributions.

Translate “CookieBoss – Cookie Consent & GDPR Compliance” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Changelog

1.2.1

  • Fixed: in the centred (modal) banner layout, visitors can now save their own choice of categories. The switches were shown, but only Accept All and Reject All could be clicked.
  • Improved: the default banner’s buttons use a darker green, so their white text meets WCAG AA contrast.
  • New: other scripts can follow the visitor’s choice with window.__cookieboss.onConsent(callback). The CookieBoss Google Tag Manager template uses it.
  • New listing screenshots.

1.2.0

  • New: a consent banner works the moment you activate the plugin, no account needed. The bundled default banner follows your site’s language (53 languages), asks every visitor for opt-in consent, supports Google Consent Mode v2 and Blocking Mode, and contacts no external service.
  • New: the setup wizard now starts with your live banner and recommended settings; connecting a CookieBoss account is an optional second step that unlocks cookie scanning, your own banner design and consent statistics.
  • New: the wizard’s live preview shows the banner even when Admin Preview hides it for you.
  • Fixed: saving the settings page no longer clears the Site ID and silently switches the banner off.
  • Security: the OAuth connection callback requires the manage_options capability, and the CDN exemption in Blocking Mode matches the host exactly.
  • Links to cookieboss.io from the plugin now carry campaign parameters.

1.1.1

  • New: guided 3-step setup wizard on first activation — connect, apply recommended settings, and confirm your banner is live in about two minutes.
  • New: “Switching from another consent plugin?” prompt that offers a faster path when a competing consent plugin is detected.
  • Improved: consent scripts now resist interference from caching and JavaScript-optimization plugins (WP Rocket, LiteSpeed, Autoptimize, Cloudflare Rocket Loader), so the banner and Google Consent Mode defaults are no longer delayed or broken.
  • Fixed: the in-admin consent statistics widget now loads and displays your banner’s impression and consent-rate data.
  • The “Cookie Consent Preferences” block now ships block.json metadata for editor discovery.

1.1.0

  • New: one-click “Connect to CookieBoss” — OAuth flow opens a popup, you sign in (or sign up) at app.cookieboss.io, pick a site, and the plugin is configured automatically. No more copying Site IDs by hand.
  • Manual Site ID input remains available as a fallback below the Connect button.
  • New: Disconnect button to revoke the connection and clear stored credentials.

1.0.1

  • Auto-save Site ID when Verify succeeds — eliminates the contradiction between the green Verify message and the orange “Not configured” Connection Status pill (#157)
  • Fixed duplicate “Settings saved.” admin notice after saving plugin settings (#159)

1.0.0

  • Initial release
  • Site ID configuration with CDN verification
  • Enable/disable toggle
  • Automatic consent script injection
  • Google Consent Mode v2 default state injection (all categories denied by default)
  • GCM URL passthrough and ads data redaction options
  • Automatic script blocking for 20+ known tracking scripts (GA, GTM, Facebook, Hotjar, etc.)
  • Script identification by both WordPress handle and source URL
  • Admin preview mode — hide banner for logged-in administrators
  • Admin notice when plugin is active but not configured
  • Settings page with organized sections (General, Script Blocking, GCM, Admin)
  • Quick links to dashboard and documentation
  • Clean uninstall — removes all options and user meta