None
Client-side storage used
Zero
Atom IDs exposed to browser
When a visitor browses more than one page in the same session, Spectare automatically avoids repeating the same content assembly. Rather than tracking seen atom IDs in the browser, Spectare issues each assembly an opaque variant ID. On the next request, the client passes that variant ID back to the assemble route, and the server resolves which atoms to exclude without those IDs ever leaving the server.
This approach keeps raw database identifiers entirely on the server side. The browser holds only the short opaque hash returned in the assemble response, which carries no structural information about your content library.
The PersonalisedSection React component handles this automatically. It reads the variantId from each assemble response and passes it as excludeVariantId on the next call, so every slot in a multi-page session surfaces a fresh perspective on your content without any configuration required.
For direct API integrations, store the variantId from the assemble response and include it as excludeVariantId in subsequent assemble requests within the same session. The server handles the rest.
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.