4 ms·
It’s also a remarkably stupid implementation. If you follow the rules [1] in a strict way, the website should be usable if the user denied consent to non-essent
by _5ygc 3y ago
It’s also a remarkably stupid implementation. If you follow the rules [1] in a strict way, the website should be usable if the user denied consent to non-essential cookie usage. You don’t need consent for strictly necessary cookies.
So a bunch of websites don’t actually need a cookie banner, as long as they’re not using non-essential cookies. You could easily get consent for marketing/tracking cookies in an unobtrusive way.
Instead, a lot of websites must have seen a drop in conversion because no one wants to interact with these awful cookie popups that have a hundred toggles.
AFAIK the page-blocking cookie banners don’t just convert worse, they’re actually not permitted (you can’t block the experience to force consent).
On my end: unless your website is very important to me, I’ll just refuse the cookies or hit the back button and load the next search result.
1: https://gdpr.eu/cookies/ https://gdpr.eu/cookies/
- corbezzoli 3y ago> you can’t block the experience That doesn’t sound right. I think interstitial are permitted by the law, I don’t think it actually says anything about “the experience.” > to force consent The vast majority of website will work after clicking No, so that’s not forced. Only rarely I see “accept cookie or subscribe” banners. I’m not even sure that this is not allowed either; user is technically forced to accept either because the “close tab” button is always available.
- _5ygc 3y agoTechnically speaking (I enforce GDPR on a technical level, not legal), you’re right on both counts. The interstitial isn’t forcing anyone to accept the cookies, and isn’t preventing the experience. But… in real-life UX, we all know the users will just hit the most obvious CTA to accept all cookies because their experience is being effectively blocked. The implementation is technically okay, but reminds me of r/MaliciousCompliance.