CookieHub Docs

CookieHub notification and Preference Center

  • Check if the CookieHub implementation script is added to the website and loaded correctly.
  • Check that the code is not blocked by any ad-blocker or security software.
  • If you are using a caching plugin or service, try clearing the cache and checking again.
  • Make sure that the code is exactly as shown in the Implementation tab of your CookieHub dashboard.
  • Ensure that no plugin or code is interfering with the CookieHub code. Performance improvement techniques that delay the loading of external JavaScript code can break CookieHub functionality and prevent consent defaults from loading before tracking scripts.
  • If your website sets a Content Security Policy (CSP), open the browser console and look for CSP violations. A violation for the CookieHub script, for an inline script, or for a .json file under cdn.cookiehub.eu/client/ each stops the consent dialog from appearing. This often happens after the CSP is changed for another service, such as Cloudflare Turnstile. Content Security Policy (CSP) gives the policy CookieHub needs, including for nonce-based policies.

If the Microsoft UET integration is enabled, CookieHub sets UET's default consent with an inline script that it adds to the page. A script-src that allows the install snippet with a nonce or a hash, but contains neither 'strict-dynamic' nor 'unsafe-inline', blocks this script. The consent dialog works, but UET gets no consent default, and the browser console reports a CSP violation for an inline script that starts with window.uetq.

Add 'strict-dynamic' or 'unsafe-inline' to script-src. See Content Security Policy (CSP).

The most common cause is CookieHub loading more than once: the script is in the page HTML and in Google Tag Manager, or in GTM and a CMS plugin, or a GTM tag fires twice on the same page. The dialog shows once, but the second instance keeps it from closing and can break Consent Mode and blocking. Remove every installation point but one.

  • Check if the CookieHub implementation script is added to the website only once. Adding the script multiple times can cause the consent dialog to be shown repeatedly.
  • Check for any conflicting code that may be causing the issue.
  • Make sure that you are using the code on the same top level domain as created in the CookieHub dashboard.
  • Check for any conflicting code that may be causing the issue.
  • Check if you have a cookie or ad blocker active in your browser. It may prevent CookieHub from setting cookies.
  • If the Secure cookie mode is set to Force in the Consent storage section of your domain settings, the consent cookie carries the Secure attribute on every page. Browsers do not send it back on pages served over HTTP, so consent does not persist there. Verify which pages are served over HTTP, or set the mode to Auto.
  • Make sure that the code is exactly as shown in the Implementation tab of your CookieHub dashboard.
  • Ensure that the 8 character CookieHub code in the implementation code on your website matches the code shown in your CookieHub dashboard.
  • Your website's CSS may be conflicting with the default styles used by CookieHub.
  • We use caching methods for fast loading and performance. Widgets are cached on our edge servers for 2 minutes and in the client's browser cache for up to 24 hours. If changes are not visible after 2 minutes, try a hard refresh: Ctrl + F5 on Windows or Command + R on Mac.

On this page