Issue with Transition from CookieBot to Compilanz

  • Resolved webesi

    (@webesi)


    10 months, 1 week ago

    Dear Compilanz Support Team,

    I am reaching out to seek assistance regarding an issue we are facing during our transition from CookieBot to Compilanz for several of our websites.

    We have successfully integrated Compilanz into our websites, replacing CookieBot. However, when conducting a compliance test using https://www.cookiebot.com/en/compliance-test/, we are encountering a critical error related to Requirement 1 (ePR), specifically concerning prior consent on non-essential cookies and trackers.

    The error message states:

    “Requirement 1 (ePR) Prior consent on other than strictly necessary cookies and trackers You do not collect consent for cookies and trackers other than strictly necessary ones. The use of non-essential cookies and trackers requires explicit consent from individuals before any data collection, as mandated by the ePrivacy Directive.”

    This is perplexing because our understanding was that Compilanz would handle the collection of explicit consent for non-essential cookies and trackers. We are unsure why this error is occurring and would greatly appreciate your guidance on how to resolve it.

    Could you please provide us with insights or steps to ensure that our websites are compliant with the ePrivacy Directive, particularly regarding the explicit consent collection for non-essential cookies and trackers?

    Thank you for your attention to this matter. We look forward to your prompt response and assistance.

    Best regards

    The page I need help with: [log in to see the link]

Viewing 1 replies (of 1 total)
  • Plugin Contributor jarnovos

    (@jarnovos)

    Hi @webesi,

    You are loading the Facebook Pixel and Analytics without consent at the moment, so that would seem to be why the report flags the site.

    You can move the the Facebook Pixel script to Complianz -> Integrations -> Script Center -> “Add a third-party script” field (without including the <script></script> and <noscript> parts), set it to load on consent for the “Marketing” category.

    This will make the FB Pixel load after receiving Marketing consent; make sure to remove your current implementation as well.

    Analytics appears to be loaded from your GTM container, so you can follow the steps in this article under (Step-by-step) Firing tags based on consent in Tag Manager, so that the tag only fires after receiving consent for the Statistics category.

    Kind regards, Jarno

Viewing 1 replies (of 1 total)
  • The topic ‘Issue with Transition from CookieBot to Compilanz’ is closed to new replies.