Skip to Content
InstallationTroubleshooting

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 Consent Mode implementation problems.

CookieHub also includes built-in diagnostics that help identify Consent Mode implementation issues such as missing consent signals, incorrect defaults, and late consent initialization. Diagnostic results are available through the Action Center and domain scan reports in the CookieHub dashboard.

Late consent means that Google tags started executing before consent defaults were initialized.

When using Google Consent Mode, consent defaults should be established before Google tags load so that Google Analytics, Google Ads, and other Google services can correctly interpret the user’s consent state from the beginning of the page lifecycle.

If Google tags initialize before consent defaults are available, CookieHub diagnostics may report:

  • Late consent initialization
  • Missing consent signals
  • Tracking activity before consent signals were initialized
  • Outdated or unsupported Consent Mode configurations
  • Incorrect consent defaults

These issues are usually caused by implementation ordering problems rather than a failure in CookieHub itself.

CookieHub diagnostics monitor Consent Mode implementations and can detect issues such as:

  • Google tags loading before consent defaults
  • Missing or incomplete consent signals
  • Consent defaults initialized too late
  • Outdated Consent Mode implementations
  • Incorrect consent default states
  • Tracking requests occurring before consent initialization

Diagnostic results are available through:

  • Action Center alerts
  • Domain scan reports
  • Google Consent Mode diagnostics

If diagnostics report a Consent Mode issue, review the implementation order of CookieHub and Google tags before modifying consent settings.

Late consent issues are most commonly caused by script ordering or loading behavior.

Common causes include:

  • Incorrect script ordering
  • Async or deferred loading of the CookieHub script
  • Google Tag Manager trigger misconfiguration
  • Direct gtag.js implementations loading before CookieHub
  • Performance optimization plugins delaying CookieHub loading
  • Multiple consent management platforms running simultaneously
  • CDN or caching systems rewriting script execution order
  • Google tag gateway (GTG) implementations exposing existing timing issues
  • Deferred CMP loading in WordPress, Shopify, or page-builder environments

Google tag gateway (GTG) itself does not bypass Consent Mode. In most cases, GTG-related issues occur because Google tags become available earlier in the page lifecycle while consent defaults are still loading.

For additional information about GTG implementations, see:

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

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.

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

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

No content is shown in the dialog

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

Direct script installations

Google tags load before CookieHub

  • Ensure that the CookieHub script is loaded before any gtag.js, Google Analytics, or Google Ads scripts.
  • Avoid using async or defer on the CookieHub script.
  • Verify that performance optimization tools are not delaying the CookieHub script.
  • Inspect the page source and browser network requests to verify execution order.

Correct ordering:

<script src="https://cookiehub.net/..." type="text/javascript"></script>
<script async src="https://www.googletagmanager.com/gtag/js?id=G-XXXXXXXX"></script>

Incorrect ordering:

<script async src="https://www.googletagmanager.com/gtag/js?id=G-XXXXXXXX"></script>
<script src="https://cookiehub.net/..." type="text/javascript"></script>

WordPress

  • Ensure that caching or optimization plugins are not delaying the CookieHub script.
  • Disable JavaScript deferral or delay features for CookieHub.
  • Avoid installing multiple consent management plugins simultaneously.
  • Verify that GTM plugins are not injecting Google tags before CookieHub initializes.
  • If using GTM, use the Consent Initialization - All Pages trigger.

Shopify

  • Verify that CookieHub is loaded before any manually installed Google Analytics or Google Ads scripts.
  • Review theme customizations and third-party apps that may inject tracking scripts before CookieHub loads.
  • Avoid duplicate Google tag installations through both Shopify integrations and GTM.
  • Verify implementation order using browser DevTools and Google Tag Assistant.

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

Analytical data

Analytics data decreased after implementing

  • It is normal to see some decrease in analytical data since some users may not allow analytical cookies or may simply ignore the cookie consent banner. It’s important to note that the drop in data is not necessarily a direct result of implementing CookieHub, but rather a consequence of increased awareness of data privacy and users’ choices to limit data collection.
  • In certain scenarios, users may choose to ignore the banner and proceed to browse the website, resulting in a significant decrease in analytical data after implementing CookieHub. You can enable the Block user interface feature to force users to take action and that will usually result in less decrease in analytical data.

Analytics data doesn’t match sessions reported by CookieHub

  • The number of sessions reported by CookieHub is based on the number of times the widget is loaded from your site, which may not be an accurate representation of the number of sessions reported by analytics services due to potential caching of the widget in the user’s browser. Typically, one session should be detected for each unique user visiting the website each day.
  • Data collected by Google Analytics and Google Ads in anonymous mode when using advanced Consent Mode is not available and does not count in reports. However, once the user has given consent, Consent Mode can use previously collected anonymous data to improve attribution and conversion modeling.
Last updated on
Matomo Tag ManagerInstallation