Installation status

The Installation status is displayed in the Implementation tab for your domain. It shows whether CookieHub is correctly installed and configured on your website and highlights any issues that need to be fixed.

You can also request a quick installation scan (takes about 1–3 minutes) to update the status. This scan detects:

  • If CookieHub is installed
  • If it’s working as expected
  • Any configuration or compliance issues

How to run an installation scan

  1. Go to your domain’s Implementation tab.
  2. Click Check installation.
  3. Wait 1–3 minutes for results.
  4. Review the Installation status message and take any recommended actions.

Possible installation statuses

✅ CookieHub is correctly set up on your website

No issues detected — CookieHub is installed and 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 or are uncategorized. Review your cookie configuration to fix.


❌ The crawler was unable to get a response from your domain (timeout)

Your site did not respond during the scan. Check site availability and retry.


❌ The crawler received a “Page Not Found” error (404)

The entry URL is incorrect or the page is missing. Update domain settings.


❌ The crawler received an “Access Denied” error (401)

The site requires authentication. Adjust domain settings to allow scanning.


❌ The crawler received an “Access Forbidden” error (403)

Your site is blocking access. You may need to whitelist CookieHub’s crawler IP addresses.


⚠ The entry URL redirects to an external domain or blocked page

Check if your domain has moved and ensure the entry URL is correct and in scope.


❌ The crawler encountered an unspecified error

Verify domain settings and retry, or contact support.


⚠ A legacy CookieHub installation was detected

An old installation is in use. Upgrade to the latest version.


❌ A CookieHub installation was not detected

Check that the script or installation method is implemented correctly.


❌ A CookieHub installation was not detected — request blocked by CSP

Update your Content Security Policy (CSP) to allow CookieHub requests.


⚠ Legacy Google Tag Manager template is in use

Update to the latest GTM template to ensure full Consent Mode v2 support.


❌ CookieHub is loaded more than once

Remove duplicate installations to avoid conflicts.


❌ Incorrect domain code detected

Replace the script’s domain code with the correct one from your dashboard.


❌ Consent Mode v2 not correctly set up — variables granted by default

Reconfigure so variables are denied by default until consent is given.


❌ Consent Mode v2 not correctly set up — Google requests bypassing Consent Mode

Reconfigure to ensure all Google tracking requests go through Consent Mode.


⚠ Outdated version of Consent Mode detected

Update the script or GTM template to a version supporting Consent Mode v2.


⚠ Old CookieHub version detected

Upgrade to the latest CookieHub version from the Overview tab.