After connecting the WordPress plugin to your Kukie.io account, you can configure the most common settings directly from the WordPress admin without logging into the Kukie.io dashboard. Everything the plugin saves is stored in your Kukie.io account, so the plugin and the dashboard never disagree. For a full overview of plugin features, visit kukie.io/wordpress.
The plugin menu
Since plugin version 1.8.0 the Kukie entry in the WordPress admin sidebar has four pages:
- Dashboard - banner status, consents today, plan, verification and accessibility widget state, plus consent totals and the last cookie scan.
- Consent banner - three tabs: Design (layout, position, revisit button, live preview), Google Consent Mode v2 and Microsoft UET. Bookmarks to the older separate Banner Design, Google Consent Mode v2 and Microsoft UET pages redirect to the matching tab.
- Accessibility widget - switch on and configure the Kukie accessibility widget for this site.
- Settings - banner script on/off, script position, verification, banner language and the connection details.
Finding Your Site Key
Your site key is displayed on the Kukie.io dashboard when you open your site. You can find it under Settings → Site Key on the site overview page, and on the plugin's Settings page under Connection. The site key is a UUID that identifies your site and is embedded in the banner script.
Consent banner: Design
The Design tab lets you pick the banner layout (popup, bottom bar, top bar, floating), its position for the floating layout, and every revisit-button option (position, style, icon, text, colours, offsets) with a live preview. Colours, texts, categories, custom CSS and the banner logo are managed in the Kukie.io Banner Editor; changes there are applied to your WordPress site automatically, no plugin update needed.
Consent banner: Google Consent Mode v2
The Google Consent Mode v2 tab has a toggle for Google Consent Mode v2 (GCM v2) and one for auto-blocking known third-party scripts until consent is given. When GCM v2 is enabled, the banner script automatically fires gtag('consent', 'default', ...) and gtag('consent', 'update', ...) calls based on your visitors' consent choices, so Google Analytics, Google Ads and other Google tags adjust their behaviour without any additional code.
Enabling GCM v2 in the plugin is equivalent to toggling it on in the Banner Editor's Integrations tab. The default consent states depend on the visitor's region and are managed through region rules in the dashboard. A Google Tag Manager container ID is entered in the Banner Editor's Integrations tab, not in the plugin.
Consent banner: Microsoft UET
The Microsoft UET tab has a single toggle that forwards visitor consent choices to Microsoft Advertising Universal Event Tracking tags.
Accessibility widget
The Accessibility widget page switches on the Kukie accessibility widget for this site and mirrors the dashboard's settings: position, button size, colour (or inherit the banner theme), hide on mobile, which modules visitors see, which languages the panel offers and its default language, and the accessibility statement link. The widget is delivered inside the same Kukie script as the banner, so there is nothing extra to install. Panel texts are reworded per language in the dashboard.
The widget is a plan feature. On plans without it the page explains what the widget does and which plan includes it, with an upgrade link; the settings are shown but cannot be saved. Changes take effect once the banner script cache refreshes, usually within a minute or two.
Language Settings
On the Settings page, Banner language follows WPML, Polylang or the WordPress site language automatically, or forces one language. Auto-Translate, the default language and the enabled languages sync to your Kukie.io account. Custom text overrides and RTL support are managed in the Banner Editor's Texts & Languages tab - see Configure Texts & Languages.
Region Rules
The consent model shown to each visitor depends on their detected region. You can configure region-specific rules (opt-in for EU, opt-out for US, etc.) in the Banner Editor's Regions tab. See Region Rules & Geo-Detection for full details.
Script Position
Choose where the banner script is injected in your WordPress pages:
- Head - uses the
wp_headhook. Recommended for best auto-blocking performance. - Body - uses the
wp_footerhook. Use this if you experience conflicts with other head scripts. - Manual - the plugin injects nothing; copy the embed code shown on the page into your theme's header template.
Triggering Scans from WordPress
Click Run New Scan on the plugin dashboard to trigger a cookie scan. The scan runs on the Kukie.io servers (using the same fan-out scanner architecture), not on your WordPress server. The dashboard refreshes its data every minute and shows the result when the scan completes.
Scan limits follow your plan's settings (maximum pages per scan, scan queue limits).
Verifying Installation
Click Verify on the plugin's Settings page to confirm that the banner script is properly loaded on your site. The plugin sends a verification request to Kukie.io, which fetches your homepage and checks for the presence of the c.js script with your site key.
Dashboard Data and Sync
The plugin caches dashboard data (consent stats, last scan info) for 5 minutes to minimise API calls, and refreshes it every minute while the Dashboard page is open. Settings changes sync to Kukie.io in real time.
