Troubleshooting

Always test in a private browser window: a stored choice from an earlier visit changes what you see.

A tracker runs before consent

1. Check that Custom Code blocking is on, on the Script Blocking tab.
2. Find the script’s address in the browser’s developer tools (Network tab). If the plugin does not recognise it, add a Block by address rule with part of the address and the right category.
3. If the script is added by Google Tag Manager, update the plugin to 1.8.10 or newer: earlier versions could not see tags that GTM adds.
4. Server-side tracking cannot be blocked from the browser. Configure it to respect consent separately.

Google Tag Manager does not show consent updates

• Check that Consent Mode v2 is on, on the Integration tab.
• Test in a fresh session with no kncc_consent cookie, and click a banner button while Preview is open.
• Make sure GTM is not loaded twice, for example by both a plugin and the theme.

The Meta Pixel fires on analytics consent

Update to version 1.8.10 or newer. From that version, tags in a GTM container wait for their own category. See the blog post.

The banner looks wrong with my theme

Switch General → Text and font style to Plugin style. If something still overrides the banner, see the CSS tips in Shortcodes, CSS and developers.

The banner is behind another element

The banner’s z-index is 999999. Raise it with custom CSS if your theme’s overlay sits on top.

Pages are cached

The plugin works with page caching: blocked scripts and embeds are the same for every visitor, and the visitor’s browser decides what to release. WP Rocket, LiteSpeed Cache and Autoptimize are configured automatically. With another plugin that delays or merges JavaScript, exclude kncc-consent and knccGuard from it.

Statistics are empty

Statistics start from the first choice a visitor makes after installing. Check them again after a few visits.

wp_consent_statistics stays “deny” after Accept all

Clear the site’s cookies or use a private window, reload with Ctrl+Shift+R, and check that the WP Consent API plugin is active.

The policy page warns about missing translations

Create the translated policy page in each language and add the [kncc_cookie_policy] shortcode to it.

Still stuck?

Ask in the support forum on WordPress.org (opens in a new tab). I answer it myself.