Debug mode helps you troubleshoot banner issues by outputting detailed information to the browser's developer console. It shows domain matching results, consent state, and configuration details.
How to Activate
Add ?kukie_debug=1 to any page URL on your site:
https://example.com/?kukie_debug=1
https://example.com/products?kukie_debug=1Then open your browser's developer tools (F12 or Ctrl+Shift+I) and switch to the Console tab. You will see debug output prefixed with [Kukie].
What Debug Mode Shows
The debug output includes:
- Domain matching - shows the registered domain from your Kukie.io configuration and the current page hostname, and whether they match. Example:
[Kukie] Domain check: registered="example.com" current="example.com" match=true - Configuration loading - whether the banner configuration was fetched successfully.
- Consent state - the current consent status and which categories are accepted or rejected.
- Region detection - the detected region and which consent model is being applied.
Troubleshooting with Debug Mode
Banner Not Showing
If the banner does not appear, enable debug mode and check for:
- Domain mismatch - the registered domain does not match the current hostname. Verify the domain in your site settings.
- Configuration error - the API returned an error. Check that your site key is correct.
- Banner disabled - the banner is toggled off in site settings.
- Hidden consent model - the region rule for the visitor's location uses the "Hidden" model, which does not display a banner.
www. Normalization
Kukie.io treats www.example.com and example.com as the same domain. Both are normalised by stripping the www. prefix before comparison. Debug mode shows the normalised values.
Tip: Debug mode only activates when the
kukie_debug=1parameter is present. It does not affect your visitors or the banner's normal operation. Remove the parameter when you are done troubleshooting.