Configuring Complianz for Burst

Have you experienced a sudden drop in statistics, or do you see unexplainable differences between statistics in Burst and another statistics plugin? If you have both Burst Statistics and Complianz installed, or any other fully integrated cookie banner plugin, this is exactly what might happen. The problem most likely is that you have configured your cookie banner plugin to require consent for the statistics category.

Checking for attributes

You can check this by right clicking in your website, click “view source”, and search for the burst.min.js, or burst.js if you’re en debug mode. If the script the following attributes: type=”text/plain” data-service=”burst” data-category=”statistics”, then you are sure that statistics are not tracked without consent, which will lower statistics with about 80-90% in our experience.

Differences in requirements per country

In most countries you do not require consent for anonymous statistics that is hosted on your own webserver: which is what Burst does. Some countries, like in the United Kingdom for example, do require consent for statistics however. But countries like Germany, The Netherlands, Belgium, France, do not require consent as long as the data is registered anonymously, and hosted on your own server. Please check with your legal advisor if this applies to your situation first.

Methods to resolve the issue

There are several methods to allow statistics tracking without consent.

• Whitelist Burst. For example in Complianz, you can whitelist the Burst Statistics script
• In the Complianz wizard, in consent / statistics configuration, on the question “Do you want to ask consent for statistics?”, answer “no”.
• In Complianz/Integrations/Plugins, disable the Burst integration.

Then check you still see the text/plain attribute in the Burst Statistics script.

For other cookie banner plugins you may need to follow similar steps. Following one of the above steps should allow tracking of statistics without requiring consent first.