Search
Close this search box.

Documentation

In this article

Categories

Recent articles

Whitelisting inline script

Update in 6.0. Whitelist script URLs and Ids in the Script Center, under Integrations

Complianz uses a regular expression to find 3rd party services in inline scripts. Below we will take an example of a Podcast Player that creates an inline script. The output also contains data related to social media hyperlinks or instagram.com in this specific case. In most use cases we will find instagram.com as a link, directly related to the service which is Instagram itself, or a plugin that provides a service like embedding Instagram posts.

But not in this case. Podcast outputs data collections but does not invoke any Instagram related services. And it does not set any other cookies related to 3rd parties, meaning it can be set before consent. But Complianz blocked the script before consent, even if it didn’t have to.

The reason why Complianz blocked the script is because the user had Instagram embedded and enabled in Complianz, but gave a false positive on the Podcast player. These cases are rare, but might happen. To overcome this you can add a filter to tell Complianz to skip an inline script. All you need is the ID, or a unique part of the inline script.

What you will need:

From 6.0 onwards, you can whitelist scripts/URLs directly in the Script Center (Complianz -> Integrations -> Script Center -> “Whitelist a script”).

Or use the below filter instead:

Join 900.000 users and install The Privacy Suite for WordPress locally, automated or fully customized, and access our awesome support if you need any help!

Complianz has received its Google CMP Certification to conform to requirements for publishers using Google advertising products.