1.4.0
Plugin version introducing zone returning-visitor support
Yes. Spectare fills slots via JavaScript after the page loads, so it is unaffected by page caching. WP Rocket, W3 Total Cache, WP Super Cache, and LiteSpeed Cache all work without any exclusion rules.
Zones render server-side and are therefore the recommended approach when you want personalised content in the HTML before the page is sent. Because zones run before the page is served rather than after, they work well with aggressive full-page caching, and the transient key Spectare uses includes referrer, UTM parameters, and the visitor’s recent page paths.
Returning-visitor personalisation in zones requires enabling the Returning visitors in zones option under Settings, Spectare. When enabled, the visitor's last three page paths are stored in a first-party cookie on your own domain and forwarded to Spectare with each zone request. The setting is off by default because it adds a cookie to your site, so you should review your cookie policy before turning it on.
Without that setting enabled, a returning visitor who arrives at a zone with no referrer or UTM parameters is treated as a new visitor and receives default content. Slots are unaffected either way and continue reading visit history directly from localStorage.
This is one atom from the Spectare content library. Spectare assembles the right atoms for each visitor in real time, based on who they are and how they arrived.