Support » Plugin: Cookiebot | GDPR Compliant Cookie Consent and Notice » Reported Cookie Files Not Set After Consent

  • Resolved rapportdesign

    (@rapportdesign)


    I’ve noticed there are a few cookie files listed in my report, which aren’t actually set, even after consent.

    I wondered if you could explain why this might be?

    Examples are… https://snag.gy/0aIn24.jpg

    Since integrating Zoho, I’ve noticed a load of new cookie files being set before consent. I’ve initiated a re-scan to try and establish if they’re necessary or not. If not, I’ll contact Zoho and maybe log an issue on your Git Hub page to see if anyone can help.

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

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author cookiebot

    (@cookiebot)

    Hi @rapportdesign

    Please read the following article for clarification:

    Why does your scanner find cookies and trackers that I cannot myself find on my website? Where do they come from?

    You could reach out to Zoho and ask if they would like to integrate with Cookiebot.

    Regards

    • This reply was modified 8 months, 1 week ago by cookiebot.
    • This reply was modified 8 months, 1 week ago by cookiebot.

    Thanks for the link to that article…

    In a previous post, I’d asked who was to blame if a cookie file that’s being set by a plugin, had been blocked by Cookiebot until consent, but due to a glitch in a plugin update, the cookie file was now getting set again without consent. The answer was the site owner.

    Due to almost daily plugin updates, this seems very difficult to keep on top of.

    I’ve recently discovered such an issue with Add To Any Share Buttons, so it does happen.

    The article you’ve just provided says “The browsers of today are simply not advanced enough to see all the cookies and trackers being set.”, yet the video here shows using the browser to identify if you’ve correctly marked up scripts for prior consent… https://www.youtube.com/watch?v=MeHycvV2QCQ

    Now that I know there are cookie files being set and the tools used for checking them, aren’t up to the job, I can’t see how the blame can possibly be put onto the site owner.

    Surely a piece of code setting the advanced cookie, which can only be detected by a scanner that has been developed and refined over the past 6 years, is the responsibility of the person who produced that code? I realise they may have terms that cover them, but I still don’t understand how site owners can stop themselves from being liable.

    Again, I’m not venting my frustration at Cookiebot. I realise you’re dealing with an awkward area and are offering one of the best solutions out there, but I’m sure you can see why this is frustrating from a website owners point of view.

    My report has come back and the Zoho cookies aren’t necessary, so I’ll be contacting them now.

    Plugin Author cookiebot

    (@cookiebot)

    @rapportdesign

    We do understand your frustration.

    Now that I know there are cookie files being set and the tools used for checking them, aren’t up to the job, I can’t see how the blame can possibly be put onto the site owner.

    At least you know that there is something going on through the cookie report, and in the case of https://snag.gy/0aIn24.jpg, you can find out which page on your website the cookies were detected. Next step is to see if there is anything related to twitter on that page, and take it from there.

    Surely a piece of code setting the advanced cookie, which can only be detected by a scanner that has been developed and refined over the past 6 years, is the responsibility of the person who produced that code? I realise they may have terms that cover them, but I still don’t understand how site owners can stop themselves from being liable.

    Advocate General’s opinion:

    AG Bobek opinion: the operator of a website embedding a plugin such as the #Facebook Like button, which causes the collection and transmission of a users’ personal data, is jointly responsible for that stage of the data processing

    The Twitter cookie is on the Home page and there is a Twitter feed.
    The problem is, even after consent, the cookie file isn’t set.

    “It is also important to understand that many cookies are so-called dynamic cookies. These – unlike ‘classical’ http/Javascript cookies – are not being set when the website is loaded. They are being set during the visit depending on the user’s behavior on your website.”
    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-

    I meant to mention in my last post, it would be great if the report could indicate the user simulated action, which tool place to detect the cookie.
    I realise this is probably asking a bit too much, but it would be a good feature to consider.

    Plugin Author cookiebot

    (@cookiebot)

    Hi @rapportdesign,

    If you tag up twitter related widgets and scripts with the “marketing” attribute, you should be good.

    Thanks for the suggestion. We will consider this feature, however, we cannot promise when or if it will be implemented.

    Have a nice day!

    My issue with Twitter is that I can’t see the cookie being set, even after consent.

    I thought marking the scripts up with the data-cookieconsent attribute, just categorised the cookie files, allowing the user to choose which ones to accept.

    I don’t understand how this will allow me to see cookie files being set in the browser, which I’m not already.

    Anyway, I’ve tried it (including the type=”text/plain”) and I can now see a personalization_id cookie file is set, which may not be directly related to this change, as I haven’t seen details of this before.

    Still, no sign on the cookie files originally discussed… https://snag.gy/0aIn24.jpg

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Reported Cookie Files Not Set After Consent’ is closed to new replies.