Closed (fixed)
Project:
Cookie Content Blocker
Version:
2.0.0
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
11 Jun 2018 at 08:33 UTC
Updated:
20 Mar 2023 at 08:14 UTC
Jump to comment: Most recent
Comments
Comment #2
steven buteneers commentedComment #3
mrpauldriver commentedYes it would be good to see this.
In the case of remote video media, my understanding is that YouTube sets marketing cookies, but Vimeo only sets statistical cookies.
This might be an important distinction for some.
https://cookiedatabase.org/cookie/vimeo/vuid/
Comment #4
dmsmidtI wouldn't be so sure about Vimeo. It's not clear enough what happens with your user data. Their privacy and cookie statements are full of statements I doubt are valid for EU citizens.
There is a reason there still are European video platforms.
For example: "By using any of our websites, apps, or players, you consent to the placement and use of cookies and similar technologies on your device". A.F.A.I.K. This just isn't allowed when personal data is involved or tracking could be possible.
Comment #5
Mortarion commented+1 for this feature request
This would be very useful to differ between offered applications that need a consent. In example one category blocks all videos on a webpage, while another category blocks a map application like google maps or mapbox. I would not go with a single "external" category since its ofter required to differ between the provider of the external services. A site visitor could say: "I don't want to allow tracking from Google, but for everything else, it is ok"
Comment #6
anruetherI think therer are two potential layers one would want to differenciate:
Comment #7
dmsmidtNote that lots of consent managers don't support accepting/refusing cookies per provider/third party. I know Onetrust does, but Cookiebot or EU cookie compliance don't. So I don't see us supporting that soon.
Our clients have never requested to differentiate between categories. In practice often one category fits all and is blocking already more than most agencies offer.
I'm happy to review patches, since I do see added value.
Comment #8
anybodyWell we've switched to https://www.drupal.org/project/cookies/ which solves all of that in combination. Perhaps that's the better choice for others here too isntead of eucc + ccb?
If you'd like to you can close this @maintainer. At least for Drupal 8/9.
Comment #9
steven buteneers commentedComment #14
sanderjonk commentedComment #15
steven buteneers commented