Integrating Burst with your consent management plugin is quite easy. There are 2 things to consider;
- Burst uses javascript. You’ll need to be able to block javascript with your consent management tool
- Burst has an option for Cookieless tracking, but it is possible to add a cookie after consent for more detailed tracking. We will explain how Complianz does this. If you’re not comfortable integrating this with your plugin, please forward this article to your preferred plugin.
Blocking Burst’s Javascript
Burst is loaded with a single Javascript, these are the attributes:
You should be able to block burst.min.js, if you can target script by id, you could use ‘burst-js’.
When Complianz blocks burst.min.js it will change the script to below example:
Using Cookieless tracking and Consent
You can use Cookieless tracking without integration, but if you want to use cookies nonetheless to get more detailed results after consent, you will need to initialize Burst after consent. This is an example of how Complianz implemented this and you might want to show your consent plugin’s author.
Adding Burst to your Cookie Policy
If you’re using Cookieless tracking only, please use this information from Cookiedatabase.org to use for your privacy policy: https://cookiedatabase.org/service/burst-statistics/
If you’re using cookies with Burst, please use this description on your cookie policy for the cookie: burst_uid
| Cookie | burst_uid |
|---|---|
| Function | to store and track interaction locally |
| Retention | 1 month |
| Purpose | Statistics |
| Data | Anonymous ID |
| Service | First Party – Burst Statistics |
Source: https://cookiedatabase.org/cookie/burst-statistics/burst_uid/
