Skip to main content

Troubleshooting

Despite CookieHub's straightforward integration process, it's not uncommon to encounter issues when implementing it on a website or application. Fortunately, many of these issues can be resolved with a few simple steps. This troubleshooting guide aims to provide solutions to common problems that may arise during the implementation of CookieHub. We'll cover issues such as the cookie banner not displaying, consent not being registered, conflicts with other scripts, and more. So, if you're having trouble with CookieHub, read on for some potential solutions.

CookieHub notification and settings dialog​

  • 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 the CookieHub functionality and prevent the automatic cookie blocker from running 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.
  • 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 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.
  • 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.

Compliance​

  • Check the latest scan result in the CookieHub dashboard for your domain. The scan may have failed to identify any cookies
  • Make sure you don't have any other cookie consent management platform active on the site as that will prevent the CookieHub scanners from identifying the cookies in use.
  • Ensure that the CookieHub script has been implemented correctly on your website and that it is loading before any scripts that set cookies.
  • When CookieHub is implementing using the Google Tag Manager template, make sure that additional consent has been configured properly according to this guide: Additional consent
  • If you are using any scripts not supported by the automatic cookie blocker, you may need to manually adjust the html code: Conditional HTML tags
  • Confirm that the cookies have been categorized correctly in the CookieHub portal and that they are not marked as 'Hidden'.