Cookie Compliance Agent Manual
All pages and this page's sections

Add Cookie Compliance on WordPress

Cookbook · platform Last verified View raw markdown (for agents)

In short: install the Cookie Compliance for WordPress plugin and connect it with your App ID and App Secret Key (plugin 3.1.12 and older label it App Key). Do not paste the Manual Integration snippet into a theme or a "header scripts" plugin.

You need #

The wrong way #

<!-- pasted into header.php, a custom HTML widget, or "Insert Headers and Footers" -->
<script>var huOptions = { "appID": "…" };</script>
<script src="https://cdn.hu-manity.co/hu-banner.min.js"></script>

On WordPress that fights the plugin (two banners, two consent stores) and skips plugin features (config pull, Script blocking engine control, WP Consent API interop). The dashboard Manual Integration snippet is for non-WordPress sites.

The right way #

  1. In wp-admin → Plugins → Add New, search Cookie Compliance (slug cookie-notice on wordpress.org/plugins/cookie-notice/). Install and activate Cookie Compliance.
  2. Open the plugin's admin screen and connect with the App ID and App Secret Key from the Cookie Compliance dashboard Integrations page for that domain. You can also sign in or sign up from the plugin: if the account has apps but none for this site, the plugin (3.1.13 or later) asks which app to use or offers to create one.
  3. Publish (or confirm published) configuration in the Cookie Compliance dashboard. The plugin pulls config on a schedule and via Pull latest settings (Pull Configuration in plugin 3.1.12 and older) — Admin Portal changes are not live on the WP site until a pull.
  4. Leave analytics plugins and tags alone. The product blocks them before consent; do not delete Site Kit / MonsterInsights / etc. solely to "make consent work."
  5. If a hand-rolled cookie popup or another CMP is still in the theme, remove it.

Banner engine: a new app starts on v2, whether it is created in the dashboard, through MCP, or from the plugin (3.1.13 or later: signup, or a sign-in that creates an app for this site). Connecting an app that already exists keeps that app's engine, and an app switched back to v1 stays on v1. The plugin picks the CDN path from the app's engine on each settings pull, so you do not paste a script URL. When the engine changes, the plugin shows a notice offering to purge the page cache; you can also run Pull latest settings. On a v2 site, the plugin's new admin interface also lets you choose a Standard or Compact banner.

Check it works #

Same verification table as the install-banner skill (private window, strictest region or geo off, no preview badge, no tracking cookies before consent, allow-all then hu-consent cookie). Extra WordPress checks:

# Check Pass
W1 View source The plugin injected the banner script pair early in <head> (not a theme paste you added). No second, hand-pasted huOptions block.
W2 Plugin connected App ID matches the dashboard domain; the plugin's Domain Info card shows Protection: Active, not Not connected.

Gotchas #