Kookiok - Free Cookie Consent Banner, No Limits (GDPR & CCPA)
by KookiOk 1 (0 reviews)

Kookiok - Free Cookie Consent Banner, No Limits (GDPR & CCPA)

Free cookie consent banner for GDPR & CCPA: no page-view limits, no visitor caps, no paywall. One-field setup, auto cookie blocking + policy table.

Kookiok ranks #23,091 among WordPress.org plugins with 30+ active installations, is #1,434 of 5,058 in the Security category, a 1/5 rating from 0 reviews, and was last updated Aug 16, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Tested up to WP 7 (Current: 7.1.4)
v1.3.0 Current Version v1.3.0
Updated 2 months ago Last Update on 16 Aug, 2026
Refreshed 1 week ago Last Refreshed on
#1,434 of 5,058 in Security Top 50% by installs
View on WordPress.org
Rank
#23,091
— No change
Active Installs
30+
+50%
KW Avg Position
138.3
0.6 worse
Downloads
582
+2 today
Support Resolved
0%
— No change
Rating
20%
Review 1 out of 5
1 (0 reviews)

Next Milestone 40

Total Progress 80%
30+ 40+
2,228
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

  • Exact install estimates within tiers
  • Track install growth over time
  • Milestone progress predictions
Upgrade to Pro
Need 2 more installs to reach 40+

Rank Changes

21,936 22,514 23,091 23,668 24,246 01-11-2026 02-11-2026 03-11-2026 04-11-2026 05-11-2026 06-11-2026 07-11-2026 08-11-2026
22,954 23,251 23,549 23,847 24,144 24-10-2026 25-10-2026 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026 02-11-2026 03-11-2026 04-11-2026 05-11-2026 06-11-2026 07-11-2026 08-11-2026
Current #23,091
Change
Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Active Installs 0,000,000+
Growth +0.0%
Peak 0,000,000

Downloads Growth

0 10 01-11-2026 02-11-2026 03-11-2026 04-11-2026 05-11-2026 06-11-2026 07-11-2026 08-11-2026
0 10 24-10-2026 25-10-2026 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026 02-11-2026 03-11-2026 04-11-2026 05-11-2026 06-11-2026 07-11-2026 08-11-2026
Downloads
Growth
Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

1.0
0 reviews
Overall 20%
5
0 (0%)
4
0 (0%)
3
0 (0%)
2
0 (0%)
1
0 (0%)

Frequently Asked Questions

Common questions about Kookiok - Free Cookie Consent Banner, No Limits (GDPR & CCPA)

In your Kookiok dashboard at https://app.kookiok.com. It is a 36-character ID.
Yes, but exclude consent.js / cdn.kookiok.com from any "defer / delay / combine JavaScript" features so the consent script keeps loading first and synchronously.
Yes. Install the free WP Consent API plugin alongside Kookiok and no further setup is needed. Kookiok registers as the site's consent provider, declares the opt-in consent model, and publishes every consent choice through wp_set_consent() - at page load and again whenever the visitor changes their mind. Any plugin that supports the API then gates itself automatically: Burst Statistics, for example, checks wp_has_consent('statistics') and listens for consent changes on its own, so it stops sending beacons before consent without you annotating a single script handle. Kookiok's categories map onto the Consent API's like this: Kookiok "necessary" -> functional (always allowed - strictly necessary needs no consent). Kookiok "preferences" -> preferences. Kookiok "statistics" -> statistics, and also statistics-anonymous. Kookiok "marketing" -> marketing. statistics-anonymous has no separate Kookiok category, so it follows the visitor's "statistics" choice: Kookiok never reports more consent than the visitor actually gave. If the WP Consent API plugin is not installed, or you have not entered a Domain Group ID yet, no bridge script is loaded and no consent type is declared, so nothing on your site changes. (Kookiok still tells the Consent API that it is a consent provider, which is what its Site Health check looks for.) Kookiok declares the optin model, which is what GDPR requires. If you run Kookiok in a pure opt-out configuration, switch it with the kookiok_consent_api_consent_type filter: add_filter( 'kookiok_consent_api_consent_type', function () { return 'optout'; } ); Under optin, a plugin that speaks the Consent API waits for the visitor to agree. That is the correct behaviour under GDPR, and it is worth knowing if your traffic is mostly outside its scope: those plugins will stay quiet until the visitor accepts.
The easiest route is the WP Consent API (see the previous question): Burst Statistics supports it, so with the WP Consent API plugin installed Burst gates itself on Kookiok consent and there is nothing to annotate. For trackers that do not support the API, it is partly automatic with one required step on your side. Known third-party trackers are blocked automatically, and so is a self-hosted Matomo/Piwik that uses the standard matomo. / piwik. file or host names. But a tracker served from your own site's path - Burst Statistics under wp-content/plugins/burst-statistics/, for example - cannot be told apart from your theme's JavaScript by URL, so Kookiok will not guess: you must annotate its script handles with the data-ag-consent attribute (a small script_loader_tag filter in your child theme). Kookiok then keeps those scripts blocked until the visitor consents to the category. The attribute is a supported, stable API, and since August 2026 annotated scripts are handed back under every privacy regulation, including CCPA's opt-out model, so annotation is safe to rely on for US traffic too. Full guide with a copy-paste WordPress filter, including which handles to gate: https://api.kookiok.com/docs/consent-script/script-blocking/
No. The plugin stores only your Domain Group ID and a couple of settings in your WordPress options. Visitor consent is handled by the Kookiok service.
The plugin ships its full, human-readable source. The only compiled asset is the block's build/index.js, minified from src/edit.js with @wordpress/scripts (npm run build); the un-minified source is included in the plugin's own src/ directory.

Sign In / Register

You need to sign in or register to use this feature.