WordPress: Configure Burst Statistics to save data
Burst stores statistics locally, but is not automatically data-efficient in every setting. Current versions offer different privacy levels.
Requirements
You need WordPress administration access and should determine which statistics values are actually needed.
Consciously select Cookieless
By default, Burst can use cookies. The current version also offers cookieless tracking and various visitor recognition methods. For “We don’t save!” The term “cookieless” should not be the sole deciding factor, but rather whether cookies, private mode or device fingerprinting are actually used.
Avoid external integrations
Evaluate optional integrations such as Google Search Console or voluntary data releases separately and only activate them if they are really needed. For minimal local statistics, avoid unnecessary external connections.
Check
After the change, check browser storage, requests and the visitor characteristics displayed in Burst with test calls.
Reset
If the selected privacy level prevents required functions, specifically reset to the previous setting and re-evaluate the additional recognition.
Server level remains separate
The same applies here: A WordPress plugin that works locally does not change the access/security logs of the web server or host.
Basics for classification
Don't just pay attention to cookies when evaluating: Cookieless is not automatically tracking-free. If “unique visitors” are recorded, also note Unique visitors without recognition .
Related guides
Sources and verification
This guide is based on multiple current sources. Vendor documentation is not treated as proof that every concrete installation automatically follows the same privacy characteristics.
Important: IP processing is not IP storage
An IP address has to be processed to establish and deliver a network connection. Hosting providers, firewalls or DDoS protection may also process or retain it for a limited time for security purposes. No Logging distinguishes this security layer from unnecessary persistent visitor logging by the website, application and ordinary access logs.