0.4.0
Package version introducing initialVariantId
2 (_variant, _error)
SSE control frames
When a page is personalised on the server, a visitor can convert without the browser ever re-rendering the section. If the client component does not know which arrangement the server showed, that conversion has nothing to attribute to, and the content that earned it gets no credit.
initialVariantId closes that gap. Your server fetch returns a variantId alongside the assembly and intent. Pass all three into PersonalisedSection and the arrangement the visitor actually saw becomes the attribution anchor for any later conversion, whether or not a fresh client render happens.
The same care applies if you parse the assembly stream yourself. Only frames carrying a component belong in the page; the control frames alongside them carry the variant identifier and the end of the stream, and the JSON responses carry flags when default content is served in place of a fresh build. Keep the variant identifier with the visit and send it with the conversion, and attribution is complete from the first server-rendered visit.
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.