Skip to content

Documentation

Troubleshooting WordPress Plugin

Troubleshooting WordPress Plugin

Last updated Mar 24, 2026

This guide covers common issues you may encounter with the Kukie.io WordPress plugin and how to resolve them. If you need to confirm the banner is loading correctly, you can also use the Verify Your Installation tool from the Kukie.io dashboard.

If the cookie banner does not appear on your site after installing the plugin:

  1. Check the site key is correct - go to the plugin page in WordPress admin and verify the connection is active (green status indicator). Compare the site key with the one shown in your Kukie.io dashboard.
  2. Check for JavaScript errors - open your browser's developer console (F12) and look for errors related to c.js. Common issues include CORS errors or blocked requests.
  3. Check script injection - view your page source (Ctrl+U) and search for c.js. The script tag should be present in the <head> or before </body>.
  4. Purge your caching plugin - if you use a caching plugin, clear all caches (page cache, object cache, CDN cache) after installing or updating the plugin.
  5. Check domain match - the domain registered in Kukie.io must match your WordPress site's domain. Add ?kukie_debug=1 to your URL and check the browser console for domain matching output.
  6. Check banner status - ensure the banner is enabled in site settings on the Kukie.io dashboard.

If the banner appears but looks broken or unstyled:

  • Clear CDN cache - if you use a CDN (Cloudflare, Fastly, etc.), purge the cached version of the banner script.
  • Check for CSS conflicts - some WordPress themes apply aggressive global CSS rules that can override banner styles. Open the browser developer tools and inspect the banner elements to check for conflicting rules. You can use custom CSS in the Banner Editor to apply fixes.
  • Disable CSS minification temporarily - if a minification plugin is combining or rewriting CSS, try disabling it to see if the banner appearance improves.

Google Consent Mode Not Working

If Google Consent Mode v2 is not firing correctly:

  • Verify GCM is enabled in both places - the toggle must be on in the WordPress plugin settings AND in the Kukie.io dashboard (Banner Editor → Integrations tab). Both must be enabled.
  • Check the browser console - add ?kukie_debug=1 to your URL and look for GCM-related debug output. You should see gtag('consent', 'default', ...) calls. See Debug Mode for more details.
  • Verify GTM is loading after consent - if you are using Google Tag Manager, ensure the GTM container is being injected by the banner script (not hardcoded in your theme). Duplicate GTM snippets can cause consent state conflicts.

Plugin Conflicts

If the banner behaves unexpectedly, a conflicting plugin may be the cause. To identify the conflict:

  1. Deactivate all plugins except Kukie.
  2. Check if the banner works correctly.
  3. Re-activate plugins one by one, testing the banner each time.
  4. When the issue reappears, you have found the conflicting plugin.

Common conflicts:

  • Other cookie/GDPR plugins - having two consent management tools active at the same time causes conflicts. Deactivate any other cookie consent or GDPR compliance plugin (e.g. CookieYes, Complianz, GDPR Cookie Compliance) before using Kukie.
  • Security plugins - some security plugins block inline scripts or external JavaScript. Add the Kukie CDN domain to your allowlist.
  • Page builder plugins - some builders wrap the entire page in their own container, which can interfere with banner positioning. Switch the script position to "Body" in the plugin settings if this occurs.

Caching Plugin Compatibility

Caching and optimisation plugins can interfere with the banner script by minifying, deferring, or delaying it. You must exclude cdn.kukie.io from JavaScript optimisation in your caching plugin.

We have detailed guides for the most popular caching plugins:

Tip: If you are using the Kukie WordPress plugin (version 1.2.0+), the banner script tag includes data-no-minify, data-no-defer, and data-no-delay attributes. Most caching plugins recognise these and automatically skip the script. If your banner still does not load, add the manual exclusion as described in the guides above.

Connection Errors

If the plugin cannot connect to Kukie.io:

  • Invalid API key - verify the key is copied correctly from the Kukie.io dashboard. The key is 64 characters long.
  • Firewall blocking - ensure your WordPress server can make outbound HTTPS requests to app.kukie.io. Some hosting providers block external API calls.
  • SSL issues - the API requires HTTPS. If your server has SSL certificate issues, the connection may fail.

Re-connecting After API Key Change

If you regenerate your API key in the Kukie.io dashboard:

  1. Go to the plugin settings in WordPress admin.
  2. Click Disconnect.
  3. Enter the new API key.
  4. Click Connect.

The old API key is invalidated immediately. The plugin will show a connection error until you reconnect with the new key.

Getting Help

If your issue is not resolved by the steps above, contact us at support@kukie.io. Include your WordPress version, PHP version, the plugin version, and a description of the issue with any console errors you see.

Previous

Configure WordPress Plugin Settings
Next

WP Rocket Compatibility
Was this helpful?