ConsentCook

ConsentCook shows your visitors a cookie banner, records their choices, and holds tracking back until they have said yes. This plugin connects your WordPress site to your ConsentCook account and places the banner on every page for you — nothing to paste, and nothing in your theme to edit. Everything about the banner — how it looks, what it says, which languages and regions it covers — is managed in your ConsentCook dashboard, and anything you publish there reaches your site on its own. The plugin's only job is the connection, and it makes sure the banner loads before any tracking does. Connecting takes about a minute. Press Connect ConsentCook in the plugin's settings, sign in, choose your site, and you are done. Your ConsentCook password stays with ConsentCook — WordPress never sees it — and until you connect, the plugin does nothing at all. ConsentCook has a free plan for one site with no card needed, and nothing in this plugin is locked behind payment. For developers

• The banner script is placed at the earliest point of the page head, so consent is resolved before analytics and marketing tags run. If a theme hard-codes analytics above the head output, move those tags after ConsentCook.
• When the WP Consent API plugin is active, ConsentCook keeps its consent categories in sync with it.
• Sites enforcing a strict nonce-based Content Security Policy can supply the request nonce through the consentcook_csp_nonce filter.

1. In WordPress, go to Plugins → Add New Plugin and search for ConsentCook.
2. Press Install Now, then Activate.
3. Go to Settings → ConsentCook.
4. Press Connect ConsentCook, sign in, choose your site, and allow the connection.

If the connect step will not go through on your host, open “Enter a site key manually” and paste the public site key shown on your ConsentCook setup page. Everything works the same afterwards.

1.2.0

• Your site now tells Google to hold off on storing anything until a visitor has chosen, from the very first line of the page, without waiting for anything to download. Before this, that instruction only arrived once our script had loaded — so on a slow connection, or for a visitor using an ad blocker that stopped the script, your site sent no instruction at all and Google was left to its own defaults. Nothing about your banner, your settings or your visitors' choices changes; this only closes the gap before the script arrives.

1.1.0

• The settings screen now shows what ConsentCook is publishing to this site: how many categories and languages the banner covers, which regions it has rules for, and whether trackers are held before consent. It reads the same public configuration a visitor's browser downloads, and the screen stays complete when a host blocks outgoing requests.
• Being connected but switched off now says so, instead of looking the same as never having connected.
• Links through to ConsentCook, including for sites that have not connected yet.
• The loader is now registered through WordPress's script API instead of being printed by hand. It still prints at the earliest head priority, so consent is still resolved before analytics and marketing tags run.
• The site key is attached through script_loader_tag, which applies on every supported WordPress version.

1.0.2

• Complete connections on hosts that block outbound loopback requests.

1.0.1

• Ship the connector the source actually contains.

1.0.0

• Secure one-click account connection with PKCE.
• Canonical early widget injection with styling kept in ConsentCook.
• Manual public-site-key fallback and WP Consent API support.