Complianz support

Hi @sebastianalbert,

Thanks for being our first support forum user ??

Burst is automatically integrated with Complianz, so there’s no need to enable it within Complianz. You can select in the “statistics” step in Complianz “yes, but not with any of the above”. This will handle the privacy policy and cookie policy statements in Complianz.

As the statistics are tracked anonymously, there’s currently no need to specifically ask for consent, unless you’re targeting the United Kingdom. In that case, Complianz will automatically handle this for you as well.

If you run a new scan in Complianz, the cookies should get picked up, on the next cookiedatabase.org sync you will get the descriptions as well.

I love what you’re doing with Burst… in one of the Complianz email newsletters I saw you asking for suggestions for Burst.

1. Options to let us more specifically define what constitutes a ‘bounce’ for our site. I’m sure you’re aware of the various possibilities, let us choose different setups based on them.

2. A way of anonymously tracking user hits on specific pages from specific referrers, and an ability to drill down regarding the behaviour of those visitors after they landed on the page. This would give us the ability to better dial-in ad campaigns we may run on specific platforms (ie Facebook, Twitter) but without violating privacy laws and rules.

In other words, if we are running an ad campaign on FB and are driving traffic to a specific landing page with some hoped for results, knowing the percentage of those visitors who landed on that landing page and who followed through with our CTA would be very helpful and would not require them giving up any personal information. The session cookie with the ID required to track where they go on the site can be expired shortly after they leave the site and the ID would be anonymized as well so it cannot be used to identify anyone in particular or track them beyond our own website.

Hi @simeoncn,

Thanks for your suggestion and the kind words. These are in my opinion pretty good ideas.

We keep all suggestions in one place; https://burst-statistics.com/feature-requests/. Please feel free to create your own request.

If you can’t add it, just let me know and I will add these two requests. Thanks!

Kind regards,
Hessel

@simeoncn I almost forgot! The bounce rate is currently set as follows. When a user only visits one page and leaves that page within 5 seconds we call it a bounce.

You can currently change the time if you’d like. This is done by a mu-plugin which you can find here: https://github.com/Really-Simple-Plugins/burst-integrations

So if you want to define the time for a bounce differently you can. That said I think you even want more control over what constitutes as a bounce. So feel free to create a feature request.

Thank you for providing valuable feedback!

Kind regards,
Hessel

OK thanks, I just did post these two requests as different feature requests over at your link. I’ll grab the mu-plugin here shortly as well… would be nice if you can integrate that into the main Burst-Statistics plugin in time.