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.
Use the Consent Initialization - All Pages trigger for the CookieHub tag.
Check that Google Tag Manager and CookieHub are 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 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.

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

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.
Ensure that the CookieHub tag uses the Consent Initialization - All Pages trigger.

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.

Verify that the CookieHub tag fires before Google Analytics, Google Ads, or other Google tags.
Ensure that the CookieHub tag uses the Consent Initialization - All Pages trigger.
Remove any additional consent checks configured on the CookieHub tag itself.
Avoid loading Google tags directly in the website HTML when also using GTM.
Use Google Tag Assistant and GTM Preview mode to verify the execution order.

Make sure you have enabled consent mode in the CookieHub tag and the default consent for the analytics and marketing categories is set to Denied.
When using advanced Consent Mode, it is normal to see tags loading before consent has been granted. Google tags may still send anonymous cookieless requests while consent is denied.
Verify that consent defaults are initialized before Google tags execute.

Verify that the tag has been configured correctly and that it's firing on the right triggers.
Configure additional consent checks according to this guide: Additional consent
If a custom consent cookie name is configured in the Consent storage section of your domain settings, the stored consent state is not available while the Consent Initialization - All Pages trigger runs, so tags relying on Page view alone are evaluated before the consent state is known. Add cookiehub_consent_update as a firing trigger for those tags: Custom consent cookie name

If you can see the CookieHub dialog with no text, it is because you have configured a language in the CookieHub GTM template that hasn't been enabled in the dashboard. To fix this, either change the Language setting in the CookieHub GTM tag to As configured in the CookieHub dashboard or enable the language in the Settings tab for your domain in the CookieHub dashboard.