Cookiebot finds strange cookies.

Comments

2 comments

  • Hi Harald,

    Cookiebot does not create/set any unexpected or unnecessary cookies on your domain, also you could check all additional information about the cookies in the scan report. In the report generated by Cookiebot you could find information for each cookie or tracker identified, you will be able to see where on your website it was first found by the scanner, what type it is and where applicable – in what line of the source code the script setting the cookie is located.
    However, you could find more detailed information about this following the link: https://support.cookiebot.com/hc/en-us/articles/360004269614-Why-does-your-scanner-find-cookies-and-trackers-that-I-cannot-myself-find-on-my-website-Where-do-they-come-from-

    When a website is being scanned, the Cookiebot scanner crawls it looking for all types of cookies and tracking technology. Please check this article in order to find out which types of cookies and tracking technologies Cookiebot scanner will find while scanning the domain.

    It is also possible Cookiebot to find a large amount of cookies on your website, but these cookies or third party cookies to be set by pull in ads from external networks. This scenario is possible if your website redirects users to other external websites and you have masked the URL so that it appears to the user that the user is still on your website, then the Cookiebot scanner will include these cookies in the scan report in order to provide transparency of the cookies and trackers in use.

    Its really hard to say what is the exact issue and what might went wrong without seeing the domain in question, since this is something unusual and could be caused by several things. This issue could be also caused by some JS function on your website which creates cookies based on timestamp in your local storage. If you want you could share your domain so we could investigate it more detailed. 

    Regards,
    Spas

    0
    Comment actions Permalink
  • Avatar
    Harald

    Turns out, that cookiebot was right and i was wrong. After having a closer look and deobfuscating some third-party ad-related javascripts, i was able to identify the service that was responsible for this. Sorry for the noise and thanks for your detailed answer!

    Best,

    Harald

    0
    Comment actions Permalink

Please sign in to leave a comment.