Skip to main content

Google Tag Manager

When implementing CookieHub using the Google Tag Manager template, some common problems may arise. Here are some solutions to these issues:

  • Make sure you have published the changes to your Google Tag Manager container.
  • Don't configure any Additional Consent Checks for the CookieHub tag as that will prevent the tag from firing.
  • Check that Google Tag Manager and CookieHub 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.
  • 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.
  • Make sure that you are using the the code on the same top level domain as created in the CookieHub dashboard. The 8 character CookieHub domain code is already embedded into the downloaded json file and can only be used on the domain that was 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.

Tags marked with "Still running" in Google Tag Manager preview​

  • The "Still running" status indicates that the user has not granted consent. In this case, information is still transmitted, but are anonymized. After the user consents, the tag should send another request, and the tag status should change to "Succeeded."

CookieHub tag is not firing​

  • Make sure you have published the changes to your Google Tag Manager container.
  • Don't configure any Additional Consent Checks for the CookieHub tag as that will prevent the tag from firing.

Google tag is not firing​

  • Don't configure any Additional Consent Checks for tags with built-in consent mode support.
  • Check if the Google tag has been configured correctly and that it's firing on the right triggers.
  • Ensure that the Google tag is not being blocked by any ad blockers or browser extensions.
  • Use the Google Tag Assistant extension to troubleshoot any issues with the Google tag.
  • Make sure you have enabled Google Consent mode in the CookieHub tag and the default consent for the analytics and marketing categories is set to 'Denied'.
  • When using Google Consent mode, it's normal to see the tag being triggered in the Google Tag Manager preview dialog. It will however not collect any data until the user has consented.
  • Verify that the tag has been configured correctly and that it's firing on the right triggers.