Kjeks Google
Google Tag Manager and Google Analytics 4 for Kjeks, using Consent Mode v2. Signals default to denied and the container is withheld until consent is granted through the Kjeks consent layer.
by Per Søderlind · github.com/soderlind/kjeks-google · website
★ 0stars
3release downloads
7composer installs
0forks
Install
The author publishes release zips, so WP-CLI can install straight from GitHub:
wp plugin install https://github.com/soderlind/kjeks-google/releases/download/0.4.0/kjeks-google.zipAlso on Packagist as soderlind/kjeks-google:
composer require soderlind/kjeks-googleFrom the readme
Kjeks Google
Google Tag Manager and Google Analytics 4 for
Kjeks, wired through Consent Mode v2.
Requires the Kjeks plugin.
Part of the kjeks family — an adapter over the Kjeks public API. See the
kjeks ecosystem overview.
Installation
1. Install and activate Kjeks first — this add-on requires it.
2. Download the latest kjeks-google.zip.
3. In WordPress, go to Plugins → Add New → Upload Plugin and upload the zip.
4. Activate the plugin (on multisite, Network Activate it).
The plugin updates itself automatically via GitHub releases using plugin-update-checker.
How it works
Two layers keep Google inside the Kjeks consent layer (see Kjeks grilling Q7):
1. Consent Mode v2 defaults are denied — before any Google code runs, the
add-on sets adstorage, aduserdata, adpersonalization, and
analyticsstorage to denied.
2. The container is gated — the GTM/gtag container is registered with Kjeks
as an inert script and only activates when the configured category is
granted, so Google can never load before consent.
When the visitor changes their choice, the add-on pushes a Consent Mode
update, mapping:
| Kjeks category | Consent Mode signals |
| --- | --- |
| analytics grant
Read the full README on GitHub →