KjeksKjeks documentation
Everything you need to install, configure, and extend cookie consent for WordPress — from a first activation to filters, REST routes, and CI scanning.
Kjeks is a small family of plugins. Start with the core plugin, then add only the pieces you need. Every guide is split into three levels so you can go as deep as you want:
| Level | For | You'll learn |
|---|---|---|
| 101 | Site owners | Install, activate, show the banner, pick categories. |
| 201 | Builders | Configure consent, register trackers, wire integrations. |
| 301 | Developers | Filters, REST routes, WP-CLI, options, and internals. |
The family
Kjeks
The consent engine: categories, prior blocking, the banner, and the tracker inventory. Works on single-site and multisite.
Add-onGoogle Consent Mode
Loads GTM / GA4 through Consent Mode v2 — signals default to denied until the visitor opts in through Kjeks.
Add-onAI Reviewer
Suggests a category and metadata for each unreviewed tracker using WordPress 7's core AI client. Advisory — you confirm each one.
ToolingScanner
A standalone Node + Playwright scanner that crawls your pages under six consent states and reports what actually loads.
Prerequisites
- WordPress 6.8+ and PHP 8.3+ for the core plugin and the Google add-on.
- WordPress 7.0+ for the AI Reviewer (it uses the core AI client).
- Node 20+ for the standalone scanner.
- The add-ons require the core Kjeks plugin to be active.
A typical workflow
- Install & activate the core plugin and place the banner.
- Declare the trackers your site runs, or let add-ons register them.
- Scan with the discovery scanner to confirm what really loads.
- Review the inventory (optionally with the AI Reviewer) and import it.
- Ship — visitors choose, Kjeks enforces.
Source for every package lives on GitHub:kjeks, kjeks-google,kjeks-ai-reviewer, and kjeks-scanner.