Description
KEKSONAUT (https://keksonaut.com) is a hosted cookie banner and consent
management service for websites in Germany, Austria, Switzerland and the
rest of Europe. This plugin connects your WordPress site to it: it loads the
KEKSONAUT banner early in the page head and adds settings and connection
diagnostics under Settings → KEKSONAUT.
What the plugin does on your site:
- Loads the KEKSONAUT banner (runtime) for the website whose public
Settings ID you enter. - Sets Google Consent Mode v2 defaults before the banner and before tags
printed later in the page: advertising, analytics and personalisation
start as “denied”. The banner updates the signals after the visitor’s
choice. - Holds back the scripts and iframes of the services you configured until
the visitor allows them (see the FAQ for the limits). - WooCommerce: order attribution (the
sbjs_*cookies) starts only after
the visitor allows the service “WooCommerce Order Attribution”. - WP Consent API: registers as the consent tool (opt-in) and passes every
choice on, so plugins that support the API follow the banner.
Banner layout, texts, colours, languages, categories and services are set
up in the KEKSONAUT web app. Its scan lists the cookies and services found
on your website and can add recognised services to your banner draft; you
review and publish the banner there. A KEKSONAUT account and a website set
up in it are required. The data processing agreement (AVV) is part of the
terms accepted during registration; no separate step is needed.
Free plan: one website with 5,000 page views per month, free of charge
with no time limit. Paid plans and their limits are listed at
https://keksonaut.com/en/pricing.
Scope: Google Consent Mode v2 signals and configurable script/iframe
blocking. KEKSONAUT is not a TCF-certified CMP. Configure the relevant services
and their script integrations, and verify the result on your site. Scripts or
iframes that start before the runtime has loaded its settings cannot be
blocked retroactively. Site owners remain responsible for their consent setup
and legal obligations.
No runtime or consent defaults are added until a valid Settings ID and HTTPS
API base are configured. Simply opening the plugin settings makes no requests
to the KEKSONAUT API.
Configuration
- Settings ID — the public settings ID shown in the KEKSONAUT dashboard
(not the internal website ID). - API base URL (optional) — empty means
https://api.keksonaut.com.
Dedicated or self-hosted deployments may set an HTTPS base URL with an
optional path, without query, fragment or credentials. - API key (optional, diagnostics only) — see the FAQ.
External services
This plugin integrates with KEKSONAUT, https://keksonaut.com, to deliver a
configured consent banner and retain consent evidence. Saving a Settings ID
connects your site’s visitors to the configured service. Until it is configured,
the plugin adds no front-end integration and makes no diagnostic requests.
What is loaded or sent, and when:
- Runtime and banner assets — on front-end page views with a valid
configuration, the browser requestshttps://api.keksonaut.com/runtime.js
(or the configured API host). Banner branding and configured logo assets may
also be requested. HTTP requests expose the visitor’s IP address, user agent
and browser-controlled referrer information to the asset host. - Banner settings and page counts — on page load the runtime requests
the path/runtime/settings/{Settings ID}from that API host. The
service receives the Settings ID and normal HTTP request information. It
records aggregate page counts per website and day for service statistics
and plan quotas. - Browser storage — the runtime stores category/service choices, banner
version and decision validity inlocalStorage(cm:consent) by default.
Depending on the service plan and website settings,sessionStorageor a
first-party consent cookie (cm_consent_{Settings ID}) can be used instead.
Decision validity is configurable in the service (default: 365 days). - Consent evidence — when a decision grants at least one optional category
or service, the runtime posts the Settings ID, decision type, banner version
and category/service choices to/runtime/consent/update. The current
service records the website host, origin verification result, user agent,
timestamp, banner version and a truncated, salted IP hash scoped to that
website. The raw IP address is not stored in the consent event. Showing the
banner, rejecting all optional processing or fully withdrawing consent does
not create a consent event. Retention is configured per website (default:
365 days); infrastructure request logging is governed by the service policy. - Manual diagnostics — only when an administrator with
manage_options
requests diagnostics, the WordPress server fetches the public settings
endpoint. If an API key is configured, it also requests/api/v1/websites
with that key in an Authorization header. The API host receives the server’s
IP address and HTTP headers, the Settings ID and, for the authentication
check only, the API key. Diagnostics use a bot user agent so that the current
service excludes them from page counts. This does not send the key to site
visitors.
Service provider: KEKSONAUT (https://keksonaut.com), Germany.
Contact: info@keksonaut.com
Legal notice: https://keksonaut.com/de/impressum
Terms of service: https://keksonaut.com/de/agb
Privacy policy: https://keksonaut.com/de/datenschutz
Installation
- In WordPress, go to Plugins → Add Plugin (“Add New” in older versions),
search for “KEKSONAUT”, click Install Now and then Activate. - Create a free account at https://app.keksonaut.com, add your website and
publish its banner. - Go to Settings → KEKSONAUT, enter the website’s Settings ID from the app
and save. Use Run diagnostics to check the connection if needed. - Test your site while logged out in a private window, including accepting,
rejecting and reopening preferences. Check that your configured optional
services wait for the appropriate consent. Clear page caches after changes.
Alternatively, download the plugin ZIP in the app and upload it through
Plugins → Add Plugin → Upload Plugin, then activate it.
Avoid installing multiple copies of the plugin. For a migration from an
older cookiemonster folder, see the release installation instructions
before switching folders; both copies use the same configuration options.
FAQ
Where is the banner configured?
In the KEKSONAUT web app at https://app.keksonaut.com. Layout, texts, colours,
categories and services are managed in the app. Publish and verify the banner
there before relying on it on a public website.
Is there a free plan?
Yes. The Free plan covers one website with 5,000 page views per month, with
no time limit. Paid plans for more websites or page views are listed at
https://keksonaut.com/en/pricing.
Does it support Google Consent Mode v2?
Yes. The plugin prints the Consent Mode defaults in the page head before the
banner’s runtime: ad_storage, ad_user_data, ad_personalization and
analytics_storage start as “denied”. After the visitor’s choice the banner
sends the matching update. Tags printed before the plugin (for example
hard-coded high up in the theme) still need to be moved or deferred. Consent
Mode controls how Google tags behave; it does not stop network requests by
itself.
Does installing the plugin automatically block every tracker?
No. Blocking applies to the services you configured in KEKSONAUT, once the
banner settings have loaded. Scripts present in the page HTML must use
deferred markup: type="text/plain" with data-cm-src and data-cm-service;
iframes use data-cm-src. Check conflicts with caching or script optimisation
tools and test before publishing.
Does it work with WooCommerce?
Yes. WooCommerce order attribution starts only when the visitor allows the
service “WooCommerce Order Attribution” in your banner. The KEKSONAUT scan
recognises WooCommerce’s order attribution script and adds the service to the
banner draft; until you publish the banner with it, order attribution stays
off. Cart and session cookies that WooCommerce needs to work are not affected.
Settings → KEKSONAUT shows under Integrations what is active on your site.
Does it support the WP Consent API?
Yes. When the WP Consent API plugin is active, KEKSONAUT registers as the
consent management plugin with the consent type opt-in and sets the API’s
categories from the banner’s choice (statistics also sets
statistics-anonymous). The WP Consent API stores these values in its own
cookies (wp_consent_*) in the visitor’s browser.
Where is the data processed?
The hosted service at api.keksonaut.com runs on KEKSONAUT’s own server in a
data centre in Lauterbourg, France (EU). The privacy policy and the data
processing agreement name the service providers involved. A self-hosted
deployment has its own operator and policies.
Does the plugin make my website GDPR compliant?
No plugin can do that on its own. KEKSONAUT asks visitors for consent and
holds back the services you configured; whether your website meets your
legal obligations depends on your services, texts and processing. You remain
responsible for that.
Is the plugin available in other languages?
The settings screen is available in English, German (Germany, also formal; Austria; Switzerland) and Spanish (Spain). The banner’s own texts are set per language in the KEKSONAUT app.
Does the plugin store visitor decisions in WordPress?
The plugin stores configuration in WordPress: Settings ID, optional API base
URL and optional API key. The service’s runtime stores the visitor’s decision
in the browser and may send consent evidence to the service as described below.
Uninstall removes configuration options for the current WordPress site.
Network-wide multisite cleanup is not implemented; options on other sites may
remain. Uninstall does not remove browser storage or external-service records.
Do I need an API key?
No. The browser uses the public Settings ID. An API key only enables the
optional authentication check that the WordPress server runs when you request
diagnostics. Prefer define( 'COOKIEMONSTER_API_KEY', 'cm_live_...' ); in the
file wp-config.php; it takes precedence over a key saved in the settings. The key
is never part of the site’s front-end markup. An empty password field keeps a
saved key; Remove stored API key deletes it (not a wp-config.php constant).
Can visitors change their choice?
The runtime offers a preferences button. If you disable it in the dashboard,
provide an accessible link such as <a href="#" data-cm-open>Cookie settings</a>
on your site and verify that it works.
Can I self-host or use a dedicated endpoint?
Set the API base URL to the HTTPS base URL of your deployment. Server-side
diagnostics accept public HTTPS endpoints and reject unsafe destinations.
The external-service details below describe the default hosted service.
Screenshots
Changelog
0.6.1
- New directory name “KEKSONAUT – Cookie Banner & Consent (DSGVO/GDPR)” and a rewritten description, installation guide and FAQ.
- Translations: the settings screen in German (Germany, also formal; Austria; Switzerland) and Spanish (Spain) is bundled. The text domain is now the directory slug keksonaut-consent, so translations from translate.wordpress.org load as well and take precedence.
- The banner integration and its settings are unchanged.
0.6.0
- WooCommerce: order attribution (sbjs_* cookies) starts only after the visitor allows the banner’s service “WooCommerce Order Attribution” and stops when the choice is withdrawn.
- WP Consent API: KEKSONAUT registers as the consent tool (opt-in) and passes every banner choice to the API.
- Settings → KEKSONAUT shows the active integrations.
0.5.4
- Plugin URI points to the plugin page on keksonaut.com; the readme describes the directory installation and the free plan.
0.5.3
- keksonaut.com for new default connections and service links; saved endpoints (including api.keksonaut.de), settings IDs and API keys are preserved.
0.5.2
- The public banner configuration survives script optimisers that remove data attributes or URL parameters (PageSpeed Ninja’s ress-safe marker); runtime 0.6.2 fallbacks.
0.5.1
- Installation on PHP 7.2 with WordPress 6.0 or newer; plugin header prepared for WordPress.org.
0.5.0
- HTTPS-only API endpoints, protected diagnostics, API keys kept out of the settings HTML, Google Consent Mode defaults before the runtime, the keksonaut-consent translation domain, corrected installation, blocking and external-service documentation.
0.4.0 and earlier
- 0.4.0: renamed to KEKSONAUT. 0.3.0: GPLv2 or later, optional API base URL, uninstall cleanup, translations. 0.2.0: runtime URL fix, wp-config.php API key. 0.1.0: first release.

