Title: CookieHug
Author: CookieHug CMP
Published: September 13, 2026
Last modified: September 13, 2026
---
Search plugins
# CookieHug
By [CookieHug CMP](https://profiles.wordpress.org/cookiehug/)
[Download](https://downloads.wordpress.org/plugin/cookiehug.0.2.6.zip)
* [Details](https://wordpress.org/plugins/cookiehug/#description)
* [Reviews](https://wordpress.org/plugins/cookiehug/#reviews)
* [Installation](https://wordpress.org/plugins/cookiehug/#installation)
* [Development](https://wordpress.org/plugins/cookiehug/#developers)
[Support](https://wordpress.org/support/plugin/cookiehug/)
## Description
**CookieHug is a platform-first cookie consent solution.** The WordPress plugin
does three things and nothing more:
1. Pairs your site with a CookieHug account via a one-time handshake.
2. Injects the consent banner snippet into `` on every page.
3. Gives you a one-click link back to the CookieHug dashboard where you actually configure
things.
**Everything else — banner texts, colours, categories, Google Consent Mode v2, cookie
scan results, translations — is managed in the CookieHug dashboard, not in WordPress.**
This is by design. It means:
* Config changes propagate instantly without touching the site.
* Upgrades to the consent logic happen on the platform side — no plugin update
required for most fixes.
* The plugin surface area stays tiny, which is what you want from something that
runs on every request.
If you’re looking for a plugin where you edit banner text in the WP admin, this
isn’t it. Use the CookieHug dashboard.
### WP Consent API
CookieHug integrates with the [WP Consent API](https://wordpress.org/plugins/wp-consent-api/).
When that plugin is active, every choice a visitor makes in the CookieHug banner
is mirrored into the shared Consent API, so any other plugin on your site can gate
its own cookies and scripts with `wp_has_consent()`. CookieHug registers as the
site’s consent management plugin and sets the consent type to opt-in (non-essential
categories denied until the visitor consents).
Category mapping (CookieHug WP Consent API):
* necessary functional (always allowed)
* preferences preferences
* statistics statistics, statistics-anonymous
* marketing marketing
This is required for, and verified by, Google’s CMP Partner Program: it is not enough
to support Consent Mode — a WordPress plugin must also use the WP Consent API.
### External services
This plugin connects your site to **CookieHug**, a hosted consent-management service
operated at https://cookiehug.com. The plugin is a connector — the consent banner,
cookie scanning, and all configuration run on the CookieHug platform — so it has
to communicate with that service to function. Nothing is sent until you click **
Connect with CookieHug** and complete the handshake; an unconnected plugin makes
no external requests.
What is sent to cookiehug.com, and when:
* **During connection (one-time handshake):** your site URL, site name, WordPress
version, PHP version, and the plugin version, so the dashboard can register and
identify the site.
* **Periodic heartbeat (about once a day, and when you open the plugin’s settings
page):** the connection key, the current plugin / WordPress / PHP versions, and
a software freshness report: the newest WordPress core version your site already
knows about, plus the list of installed plugins (slug, name, version, whether
it is active, and the newest version WordPress has already detected for it).
Only component names and version numbers are sent, never content or user data.
The dashboard uses this to show the site as active and to warn you about outdated
software. This runs only while the site is connected.
* **Status checks (from wp-admin):** the connection key, to retrieve the account/
plan/license state shown on the settings page.
* **Consent banner script (on every front-end page view):** visitors’ browsers
load `https://cookiehug.com/api/script/.js`. Standard web-request metadata(
IP address, user agent) reaches CookieHug as part of serving that script, exactly
as it would for any third-party script. The banner’s consent logic and the choices
visitors make are handled by the CookieHug platform.
Use of the CookieHug service is governed by its Terms of Service and Privacy Policy:
* Terms of Service: https://cookiehug.com/terms
* Privacy Policy: https://cookiehug.com/privacy
A CookieHug account is required. The service is provided by CookieHug and is not
affiliated with WordPress.org.
## Screenshots
[⌊Plugin settings page with an active connection.⌉⌊Plugin settings page with an
active connection.⌉[
Plugin settings page with an active connection.
## Installation
1. Upload the plugin ZIP to **Plugins Add New Upload Plugin**, or extract into `
wp-content/plugins/cookiehug/`.
2. Activate via **Plugins Installed Plugins**.
3. Go to **CookieHug** in the admin menu and click **Connect with CookieHug**.
4. Confirm the connection on the CookieHug dashboard. You’ll be bounced back to WordPress
with the connection saved.
5. The banner starts appearing on the frontend automatically.
## FAQ
### How do I change the banner colours / text / categories?
Click **Open CookieHug dashboard** on the plugin settings page. Everything is configured
there. The plugin never exposes those controls locally — that’s intentional.
### Does the plugin store any personal data?
No. The plugin stores a license key, a connection key (hashed on the server), and
a domain ID. No visitor data ever touches the plugin — consent events go directly
from the banner script to the CookieHug backend.
### What happens when I deactivate / uninstall?
Deactivation stops the snippet from loading. Uninstall (Plugins Delete) removes
all `cookiehug_*` options and transients. The remote connection is _not_ revoked
automatically on uninstall — do that from the plugin’s settings page before deleting,
or from the CookieHug dashboard.
### Can I self-host or point the plugin at a staging CookieHug instance?
Yes — add to `wp-config.php`:
```
add_filter( 'cookiehug_api_base', function() { return 'https://cookiehug.test'; } );
```
## Reviews
There are no reviews for this plugin.
## Contributors & Developers
“CookieHug” is open source software. The following people have contributed to this
plugin.
Contributors
* [ CookieHug CMP ](https://profiles.wordpress.org/cookiehug/)
[Translate “CookieHug” into your language.](https://translate.wordpress.org/projects/wp-plugins/cookiehug)
### Interested in development?
[Browse the code](https://plugins.trac.wordpress.org/browser/cookiehug/), check
out the [SVN repository](https://plugins.svn.wordpress.org/cookiehug/), or subscribe
to the [development log](https://plugins.trac.wordpress.org/log/cookiehug/) by [RSS](https://plugins.trac.wordpress.org/log/cookiehug/?limit=100&mode=stop_on_copy&format=rss).
## Changelog
#### 0.2.6
* New `[cookiehug_declaration]` shortcode: renders the cookie declaration table
on any page or post (the loader is enqueued only where the shortcode is used).
#### 0.2.5
* Resubmission build for the WordPress.org review. No code changes compared with
0.2.4: every PHP class already carries the CookieHug_ prefix; the version number
is bumped only so this build is distinguishable from the earlier 0.2.4 upload.
#### 0.2.4
* Declare compatibility with WordPress 7.1.
* readme: the External services section now spells out the software freshness report
sent with the daily heartbeat (installed plugins with their versions and update
state).
* Admin: the Disconnect confirmation labels are passed through wp_localize_script(),
so they can be translated like the rest of the plugin.
* Internal: all PHP classes are renamed from CH_* to CookieHug_* so every global
symbol carries the plugin prefix (WordPress.org naming rule). No functional change.
#### 0.2.3
* The daily heartbeat now includes a software freshness report: WordPress core
version, the list of installed plugins with their versions, and which updates
WordPress has already queued. The CookieHug dashboard uses it to warn the site
administrator about outdated software before it becomes a security problem. No
content or personal data is sent — only component names and version numbers.
#### 0.2.2
* Add an “Updates” diagnostics panel to the settings screen: shows the installed
version, a live check against the CookieHug update server (with the exact HTTP
result), whether a newer version is available, and whether WordPress has queued
the update. Includes a one-click “Force update check”. Helps pinpoint why an
update might not appear (server firewall / caching plugin) without touching the
server.
#### 0.2.1
* Add a “WP Consent API” status panel on the CookieHug settings screen: shows whether
the WP Consent API plugin is active and confirms CookieHug is registered as the
consent manager (consent type opt-in). Offers a one-click install link when the
API is missing.
#### 0.2.0
* Integrate with the WP Consent API: visitor choices in the CookieHug banner are
mirrored into the shared consent bus (wp_set_consent), so other plugins can read
consent via wp_has_consent(). Required for Google’s CMP Partner Program.
* Load the consent banner via wp_enqueue_script() instead of a raw printed tag (
WordPress.org compliance).
* Use wp_safe_redirect() with the platform host allow-listed for the connect/SSO
hops.
* Drop the manual load_plugin_textdomain() call (translations load just-in-time
since WP 4.6).
#### 0.1.1
* Add a periodic heartbeat (daily, plus when opening the settings page) so the
dashboard shows an accurate “last seen” and current WP/PHP/plugin versions.
* Ship the self-updater so future versions surface as a normal WordPress update.
#### 0.1.0
* Initial public release. Connect flow, dashboard passthrough, banner snippet injection.
## Meta
* Version **0.2.6**
* Last updated **20 hours ago**
* Active installations **Fewer than 10**
* WordPress version ** 6.0 or higher **
* Tested up to **7.1**
* PHP version ** 7.4 or higher **
* Tags
* [consent](https://wordpress.org/plugins/tags/consent/)[consent mode](https://wordpress.org/plugins/tags/consent-mode/)
[cookies](https://wordpress.org/plugins/tags/cookies/)[GDPR](https://wordpress.org/plugins/tags/gdpr/)
[privacy](https://wordpress.org/plugins/tags/privacy/)
* [Advanced View](https://wordpress.org/plugins/cookiehug/advanced/)
## Ratings
No reviews have been submitted yet.
[Your review](https://wordpress.org/support/plugin/cookiehug/reviews/#new-post)
[See all reviews](https://wordpress.org/support/plugin/cookiehug/reviews/)
## Contributors
* [ CookieHug CMP ](https://profiles.wordpress.org/cookiehug/)
## Support
Got something to say? Need help?
[View support forum](https://wordpress.org/support/plugin/cookiehug/)