CookieHub notification and Preference Center

The cookie consent dialog does not appear on my websiteCopy Anchor Link

• 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 you have implemented Content Security Policy (CSP) configurations on your website, it is possible that they are preventing CookieHub from being loaded. In this case, you will need to modify your CSP rules to allow the CookieHub code to be loaded.

Consent dialog isn't closed on consentCopy Anchor Link

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.

The cookie consent dialog keeps reappearing even after the user has given consentCopy Anchor Link

• 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.

The cookie consent dialog is not styled correctlyCopy Anchor Link

• 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.