Atoms / Library

featureanalyticsconversionjourneyattributionflow

Visitor journeys now show which atoms were seen at every step

WordPress, React, and script paths unified

Integration parity

Atom-level across every page in the session

Attribution depth

Spectare now connects the full page journey a visitor took with the specific content atoms they saw along the way. When a visitor converts, the platform records not just which page they converted on but the entire sequence of pages they visited and which atoms were shown to them at each stop. You can see that a developer who converted on your pricing page had previously seen your SSR performance atom on the homepage and your API reference atom on the docs page.

This applies consistently whether your site uses the WordPress plugin, the React package, or the JavaScript snippet. Previously the script path and the React package reported conversion data differently. They now send identical journey and atom-exposure payloads, so your analytics are comparable regardless of how Spectare is integrated into your stack.

The WordPress plugin handles cross-page attribution by holding atom exposure data in session storage as visitors move between pages. When a conversion fires on a destination page, the atom IDs recorded on earlier pages in the same session are included automatically. Nothing extra needs to be configured to get this behaviour.

The Flow view in the Spectare admin renders these journeys as a page-level Sankey diagram. With atom attribution now attached to each node in that diagram, you can drill from a high-level journey pattern down to the individual pieces of content that characterised converting paths versus non-converting ones.

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.