Fix caching conflicts (WP Rocket and similar)
Stop aggressive caching and JS optimization from breaking tracking.
Performance plugins and CDNs can interfere with tracking when they minify, combine, delay, or cache JavaScript. If tracking is inconsistent on a site with heavy caching, exclude iTracker360 from those optimizations.
What to exclude
- JavaScript optimization. Exclude the iTracker360 script from minification, concatenation, and any "delay JavaScript execution" feature so it loads normally.
- Cookie-aware caching. Add the
iTracker360_cookie prefix to your cache's "never cache these cookies" rule so a visitor's tracked session isn't served a cached page. - Clear caches. After changing settings, clear the page cache, the CDN cache, and your browser cache, then re-test.
These settings exist in most caching tools (WP Rocket, other WordPress cache plugins, and CDN dashboards) under their file-optimization and advanced/cookie rules.