Feature request

A direct integration – > for now please refer to this article

Complianz 5.5 will include the possibility to easily upload your custom-made placeholders!

Specific TCF integration for California/CCPA

A LinkedIn placeholder is now used to replace LinkedIn embeds, before marketing consent.

Complianz is a rather heavy plugin. On every page request our sites have more than 150 queries with “select * from wp_cmplz_cookies where ID = ‘XX’”. A little load optimization would be great.

Complianz 6.0 will take Consent Management to the next level. We have redesigned the way consent is stored, to prepare for ever-changing privacy legislation around the globe.

https://wordpress.org/support/topic/headless-wordpress-3/ Look at how to leverage REST-API to use Complianz on decoupled front-end.

According to Dutch law, the cookie preferences must be immediately visible to website visitors. A button with ‘view preferences’ does not meet the requirements.

Currently the (empty) google tag manager container code is loaded (https://www.googletagmanager.com/gtm.js?id=GTM-XXYYZZZ), when someone visits the website the first time. That means, even before the user does approve the consent, Google learns about the user. This is a situation comparable to Google fonts handling. Can you block the container code as long, as there is no […]

Hi, I want propose to support wp-rocket iframe lazy loading. I have read the rationale behind the decision to disable it here: https://wordpress.org/support/topic/wp-rocket-integration/#post-13241154. But the iframes are not lazyloaded for users not needing the banner. Also in the forum answer, it’s said that “If an iframe is blocked by Complianz, it is effectively lazy loaded” […]