Please note: this feature will be released in version 2.3.0.
To keep your statistics accurate and free from manipulation, Burst automatically detects suspicious data from bots or attackers. In some cases, a single visitor (usually not human) may generate thousands of requests in a very short time. These requests distort your analytics, leading to incorrect graphs, visitor counts, conversion percentages, and more.
When Burst detects this, you will get a notice about this.
“Burst has detected an anomalous number of visits (1234 in 24 hours) from one user.”
You can click the “fix” button to remove these visits. As cookieless tracking is less accurate, it is possible that this is a false positive. As of 2.2.8, a new fingerprinting library will be introduced, which will greatly improve accuracy, which will make these notifications more accurate as well.
This ensures your reports reflect actual user behavior — not bots or attacks.
Customizing the Cleanup Threshold
You can easily change the sensitivity of this cleanup process using WordPress filters in a MU plugin.
Example: Increase threshold to 3000 visits per day
add_filter( 'burst_data_cleanup_treshold', function( $treshold ) {
return 3000;
} );
Example: Adjust the time interval to 3 days
add_filter( 'burst_data_cleanup_interval_days', function( $days ) {
return 3;
} );
This gives you full control over what is considered “malicious” in your specific use case.
When Should You Adjust This?
- High-traffic sites: If legitimate users or crawlers generate high request volumes, consider increasing the threshold.
- Cookieless tracking: with cookieless tracking it is possible to get false positives on this notice, if for example a lot of users with the same browser, os, ip etc, are visiting the site at the same time.
Summary
Burst automatically removes abnormal visit spikes to keep your stats reliable. You can fine-tune this behavior using simple filters in a MU plugin. Want to learn how to create one? Read our guide:
👉 How to add filters with MU plugins – quick & easy