Burst is designed to work with any caching plugin, but in some cases the caching might lead to unexpected results. For example, if a the loading of a Burst script is delayed so much that users might have left already before the hit is registered.
In most cases, you’d want the script to load as early as possible. This is what most tools, like Google Analytics, recommend to do. However, this early loading comes with small performance cost. Which is why we offer turbo mode. Turbo mode delays the loading of the Burst scripts, so your page loads as fast as possible, without any blocking from Burst. The downside of this approach is, that, just like with the caching plugins, you might miss some quick leavers, bounces.
If you want to exclude Burst from your caching plugin, you should exclude all scripts that include:
burst.min.js (or in debug mode) burst.js. If you have enabled cookieless tracking, you should exclude burst-cookieless.min.js, or burst.min.js.
This is the same for the combined method (settings and script concatenated in one file) and for the default script. Only the paths differ, but most plugins will let you add a part of the path.