cookie_content_blocker
This module will help you prevent the loading of specific parts and related scripts of a page until consent for placing Cookies and related technologies is given. This module is primarily intended to support compliance with the GDPR.
Unlike similar modules, Cookie Content Blocker prevents the rendering of specific content and scripts at server level instead of removing it after it was already rendered on the client side. This way we can guarantee that no tracking or cookies can be placed before consent is given.
A client-side approach for injecting the consented content is chosen to be able to provide out-of-the-box compatibility with external caching systems like Varnish.
This module provides:
- An API to block content that should not be displayed before the user gives consent
- Integration with Core Media and OEmbed to block third party content, like YouTube or Vimeo
- Integration with Core CKEditor to help editors block (third party) content
Example:
Usages
Some examples of parts of your site content that should potentially be blocked until consent is given because they may leak personal data and/or allow cross site/device tracking:
- (Google) Maps,
- (Facebook/Twitter, AddThis, AddToAny, etc.) social share buttons,
- (Youtube/Vimeo) video's
- Webfonts,
- .. all other kinds of third party scripts, pixels or embedded content.
With this module you won't need a complete Cookie wall, but is designed to integrate well with Cookie Manager like Cookiebot or EU Cookie Compliance Blocked parts of your content will dynamically be loaded and shown only after giving consent. No page refresh is needed and no additional calls are made to the back-end.
Documentation
Please read the documentation to further your understanding on how to use the Cookie Content Blocker module and it's submodule(s).