Thread Starter
203X
(@ryder203)
I mean, if I open a new clean session in chrome without being logged into my WP backend, I can accept cookies, then the burst UID cookie is set – but why? Is the cookieless tracking option in burst misleading? At the cookie policy one can read it’s a tracking cookie. If I deny at the cookie hint, the cookie is not set – which is OK, but if accepted it should not be there at all, since I chose cookieless tracking.
Hi @ryder203,
First the solution to disable cookies after consent: If you want to use cookieless tracking before and after consent, you can turn off the Burst Statistics integration in Complianz.
Now the reason why we place a cookie after consent. We had to make some decisions when making the integration with Complianz. Tracking with cookies is more accurate and gives more control to the user. This is why we decided that after consent, a cookie will be set We don’t have plans to give more options configuring cookieless tracking. But if you want you can open a feature request and when enough people would like this feature we will build it.
Hope this answers your question. If you have more questions, feel free to ask.
Kind regards,
Hessel
Thread Starter
203X
(@ryder203)
Thanks for the explanation, Sir. A hint regarding that at the big Burst cookieless setting DIV would be nice. As it is now it can be confusing for admins and visitors (especially if admins create their own cookie hint texts regarding tracking).
Hi @ryder203,
I understand. We’ll add some clarification and maybe a link to an article going into more detail. Thank you for making Burst better 🙂
I’ll close this support topic for now. If you have another question or need any help, let us know.
Kind regards,
Hessel
