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.