Title: ConsentCook Author: Arched Published: Ògún 14, 2026 Last modified: Ògún 30, 2026 --- Ṣàwárí àwọn plugin ![](https://ps.w.org/consentcook/assets/banner-772x250.png?rev=3647285) ![](https://ps.w.org/consentcook/assets/icon-256x256.png?rev=3647285) # ConsentCook Láti ọwọ́ [Arched](https://profiles.wordpress.org/lewisgmorris/) [Ṣe ìgbàsílẹ̀](https://downloads.wordpress.org/plugin/consentcook.1.2.1.zip) * [Àwọn àlàyé](https://yor.wordpress.org/plugins/consentcook/#description) * [Àwọn àgbéyẹ̀wò](https://yor.wordpress.org/plugins/consentcook/#reviews) * [Ìgbéwọlẹ̀](https://yor.wordpress.org/plugins/consentcook/#installation) * [Ìdàgbàsókè](https://yor.wordpress.org/plugins/consentcook/#developers) [Ìrànlọ́wọ́](https://wordpress.org/support/plugin/consentcook/) ## Àpèjúwe 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Ìtumọ̀ Yorùbá: ’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Ìtumọ̀ Yorùbá: ’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. ### External services This plugin connects your site to ConsentCook (https://consentcook.com), the service that provides the banner. Once connected: * Every public page loads the banner script and your siteÌtumọ̀ Yorùbá: ’s published banner settings from consentcook.com. * When a visitor makes a choice on the banner, that choice is sent to ConsentCook so it can be recorded and enforced. * If the banner hits a problem in a visitorÌtumọ̀ Yorùbá: ’s browser, a limited error report may be sent to ConsentCook so it can be fixed. No other visitor data is collected by the plugin itself. Pressing Connect opens ConsentCook so you can sign in there; your password stays with ConsentCook and is never shared with this site. While an administrator has the pluginÌtumọ̀ Yorùbá: ’s settings page open, the site also fetches your published banner settings so the screen can show what is live. That request identifies your site only by its public key, carries no visitor data, and is remembered for five minutes. If your host blocks outgoing requests, the screen says so and everything else keeps working. Terms: https://consentcook.com/legal/terms Privacy policy: https://consentcook. com/legal/privacy-policy ## Àwọn àwòrán ìbòjú [⌊Settings → ConsentCook before connecting: one button, and the manual site-key fallback.⌉⌊Settings → ConsentCook before connecting: one button, and the manual site-key fallback.⌉[ Settings ConsentCook before connecting: one button, and the manual site-key fallback. [⌊Choosing which ConsentCook site this WordPress install belongs to.⌉⌊Choosing which ConsentCook site this WordPress install belongs to.⌉[ Choosing which ConsentCook site this WordPress install belongs to. [⌊Settings → ConsentCook once connected, showing what is being published to the site.⌉⌊Settings → ConsentCook once connected, showing what is being published to the site.⌉[ Settings ConsentCook once connected, showing what is being published to the site. [⌊The consent banner on the front end, styled from the ConsentCook dashboard.⌉⌊The consent banner on the front end, styled from the ConsentCook dashboard.⌉[ The consent banner on the front end, styled from the ConsentCook dashboard. [⌊The privacy preferences panel, where a visitor chooses category by category.⌉⌊ The privacy preferences panel, where a visitor chooses category by category.⌉[ The privacy preferences panel, where a visitor chooses category by category. ## Ìgbéwọlẹ̀ 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. ## FAQ ### Do I need a ConsentCook account? Yes — the plugin is the bridge between your site and ConsentCook, so it does nothing until you connect one. The free plan covers one site and does not ask for a card. ### What does the plugin store on my site? Almost nothing: your siteÌtumọ̀ Yorùbá: ’s public key and whether the banner is switched on. Your ConsentCook password is never seen or stored by WordPress. ### What happens if I deactivate it or never connect? Nothing at all — the banner is not shown and your site does not contact ConsentCook. ### Who is responsible for my visitors’ data? You remain the data controller for your site. ConsentCook acts as a processor for the consent choices recorded and enforced through the service. ## Àwọn àgbéyẹ̀wò Kò sí àwọn àgbéyẹ̀wò fún plugin yìí. ## Àwọn Olùkópa & Olùgbéejáde “ConsentCook” jẹ́ ètò ìṣàmúlò orísun ṣíṣí sílẹ̀. Àwọn ènìyàn wọ̀nyí ti ṣe ìkópa sí plugin yìí. Àwọn Olùkópa * [ Arched ](https://profiles.wordpress.org/lewisgmorris/) [Túmọ̀ “ConsentCook” sí èdè rẹ.](https://translate.wordpress.org/projects/wp-plugins/consentcook) ### Ṣe o nífẹ̀ẹ́ sí ìdàgbàsókè? [Ṣàwárí koodu](https://plugins.trac.wordpress.org/browser/consentcook/), ṣàyẹ̀wò [ibi ìpamọ́ SVN](https://plugins.svn.wordpress.org/consentcook/), tàbí ṣe àgbékalẹ̀ sí [àkọsílẹ̀ ìdàgbàsókè](https://plugins.trac.wordpress.org/log/consentcook/) nípasẹ̀ [RSS](https://plugins.trac.wordpress.org/log/consentcook/?limit=100&mode=stop_on_copy&format=rss). ## Àkọsílẹ̀ àwọn àyípadà #### 1.2.1 * Fixed a background timer that never stopped. If our banner script could not load on a page — because a visitor uses an ad blocker, or the siteÌtumọ̀ Yorùbá:’ s security settings block it — the plugin kept checking for it ten times a second for as long as the page stayed open. It now gives up quietly after ten seconds. Nothing about how consent is recorded has changed. #### 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Ìtumọ̀ Yorùbá: ’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Ìtumọ̀ Yorùbá: ’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. ## Àkójọpọ̀ Meta * Ẹ̀yà **1.2.1** * Ìgbàgbọ́hùn tó kẹ́yìn **ọ̀sẹ̀ 2 sẹ́yìn** * Àwọn ìgbéwọlẹ̀ tó ṣiṣẹ́ **Tó kéré sí 10** * Ẹ̀yà WordPress ** 5.7 tàbí ju bẹ́ẹ̀ lọ ** * Dánwò dé **7.0.4** * Ẹ̀yà PHP ** 7.4 tàbí ju bẹ́ẹ̀ lọ ** * Èdè * [English (US)](https://wordpress.org/plugins/consentcook/) * Àwọn àmì * [CMP](https://yor.wordpress.org/plugins/tags/cmp/)[consent](https://yor.wordpress.org/plugins/tags/consent/) [consent mode](https://yor.wordpress.org/plugins/tags/consent-mode/)[cookies](https://yor.wordpress.org/plugins/tags/cookies/) [GDPR](https://yor.wordpress.org/plugins/tags/gdpr/) * [Ìwòye Tó Péye](https://yor.wordpress.org/plugins/consentcook/advanced/) ## Àwọn ìbò Kò sí ìwádìí tí a tíì fi ránṣẹ́. [Your review](https://wordpress.org/support/plugin/consentcook/reviews/#new-post) [Wo gbogbo àwọn àgbéyẹ̀wò](https://wordpress.org/support/plugin/consentcook/reviews/) ## Àwọn Olùkópa * [ Arched ](https://profiles.wordpress.org/lewisgmorris/) ## Ìrànlọ́wọ́ Nǹkan wà tí o fẹ́ sọ? Ṣé o nílò ìrànlọ́wọ́? [Wo àpéjọ ìrànlọ́wọ́](https://wordpress.org/support/plugin/consentcook/)