Skip to Content
DashboardImplementation

Implementation

Implementation method

The Implementation tab is where you can find information on how to correctly implement CookieHub into your website. Proper implementation is crucial to ensure that tracking data and cookies are not lost or set prior to consent. Depending on your current setup and CMS, CookieHub can be implemented in various ways. To make this process as easy as possible, CookieHub provides an Implementation Assistant to guide you through the process. Choose from the following implementation methods: Google Tag Manager, Wordpress plugin or manual insertion of the code.

Implementation assistant

Installation status

The Installation status section is updated after each scan and provides an overview of whether CookieHub is correctly installed and configured on your website. It also highlights any issues that need to be addressed.

Possible statuses and their meanings are outlined below:

  • CookieHub is correctly set up on your website
    No issues were detected, and CookieHub is functioning as expected.

  • There were X cookies detected that are either set prior to consent or haven’t been categorized yet
    Some cookies are being set before consent is granted or are not yet categorized. Update your cookie configurations to address this issue.

  • The crawler was unable to get a response from your domain, most likely due to a timeout
    The domain did not respond during the scan. Verify that your website is accessible and try again.

  • The crawler received a “Page Not Found” error from your domain
    The entry URL returned a 404 error. Ensure the domain and entry URL are correct in your settings.

  • The crawler received an “Access Denied” error from your domain
    The scan could not proceed due to access restrictions. Verify if authentication is required and adjust the domain’s settings accordingly.

  • The crawler received an “Access Forbidden” error from your domain
    The domain is blocking access. You may need to whitelist the CookieHub crawler IP addresses.

  • The entry URL is redirecting to an external domain or a page that is not allowed to be crawled due to scan settings
    Check that your domain hasn’t been moved, and confirm the entry URL is correct and within the scan scope.

  • The crawler encountered an error
    The scan failed due to an unspecified issue. Verify the domain and entry URL, then retry or contact support for assistance.

  • A legacy CookieHub installation was detected
    An outdated CookieHub setup is in use. Consider upgrading to the latest version.

  • A CookieHub installation was not detected on your website
    CookieHub does not appear to be installed. Verify that the script or installation method has been correctly implemented.

  • A CookieHub installation was not detected on your website. The CookieHub request was blocked by CSP
    The Content Security Policy (CSP) on your domain is blocking CookieHub requests. Update the CSP configuration to allow CookieHub.

  • Legacy Google Tag Manager template is in use
    An older version of the CookieHub GTM template is detected, which does not fully support Consent Mode v2. Follow the upgrade instructions to update the template.

  • CookieHub is loaded more than once
    Multiple instances of CookieHub are being loaded on your website, which can cause conflicts. Ensure only one installation method is used, and remove any additional installations.

  • Incorrect domain code detected
    The domain code being used is incorrect. Replace it with the correct domain code.

  • Consent mode v2 is not correctly set up. Consent mode variables are granted by default when they should be denied
    Update your Consent Mode v2 configuration to ensure variables are correctly denied by default.

  • Consent mode v2 is not correctly set up. Tracking Google requests without Consent mode settings were detected
    Google tracking requests are bypassing Consent Mode. Reconfigure your settings to enforce compliance.

  • Outdated version of Consent mode detected
    The domain is using an older version of Consent Mode. Update the CookieHub script or GTM template to a version that supports Consent Mode v2.

  • Old CookieHub version detected
    An outdated version of CookieHub is installed. Upgrade to the latest version via the Overview tab in the CookieHub dashboard.

Last updated on