CookieHub Docs

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.
  • When a visitor has allowed nothing beyond Necessary, CookieHub removes undeclared cookies along with the declared ones. Uncheck Delete unknown cookies on deny all in the General section of your domain settings to leave them alone, or categorize the cookie as Necessary in Cookies & Services.
  • Turning Automatic Cookie Removal off does not stop this. That setting controls whether removal runs on page load; removal also runs whenever a visitor responds to the consent dialog, regardless of it.
  • Undeclared cookies are not touched when a visitor allows some categories and denies others, so the same cookie can survive one choice and not the other. See What gets removed.
  • A visitor who has not answered has allowed nothing, so while Automatic Cookie Removal is enabled the page-load removal treats them the same as a visitor who denied all. Categories that are checked by default do not count as allowed until the visitor confirms them.
  • Undeclared cookies are removed as part of that unless Delete unknown cookies on deny all is unchecked. Categorize the cookie as Necessary, or uncheck one of the two settings.
  • Regions configured for implied consent are not affected, since those visitors are treated as having allowed everything until they choose otherwise.

On this page