Integrations / Personalisation
Session AI
Server-side event delivery to the Session AI (formerly ZineOne) In-Session Marketing Platform. Forwards behavioural events into a Session AI REST/webhook channel so the platform can build each visitor's real-time context and intent for in-session personalisation. Identity is keyed on customer id (cid) and email; event attributes are sent as flat key/value pairs inside the events array.
Datafly Signal delivers first-party events to Session AI server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Session AI expects.
Why route Session AI through Datafly Signal
Profiles update from the server, not the browser
Events reach Session AI even when a tracker blocker or a failed page unload would have dropped a client-side call, so the profile reflects what actually happened.
Delivery is batched, rate-limited, and retried
Signal buffers to Kafka, respects the Session AI rate limit, and retries on 429 or transient failure rather than dropping the event.
One consent decision governs every destination
Session AI is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.
What ships in the blueprint
Mapped events
add_to_cartbegin_checkoutloginpagepurchaseremove_from_cartsearchsign_upview_cartview_itemVertical presets
Default. Each preset starts from a working configuration for that vertical rather than a blank field map.
Full field mappings, configuration fields, and troubleshooting are in the Session AI documentation.
Frequently asked questions
Does Datafly Signal integrate with Session AI?
Yes. Datafly Signal delivers first-party events to Session AI server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Session AI expects. The integration is included in every deployment at no additional cost.
How is server-side Session AI tracking different from the Session AI tag?
The Session AI tag runs in the visitor's browser, so it is subject to ad blockers, tracking prevention, and page-unload races. Signal collects the event through a first-party endpoint on your own domain and delivers it to Session AI from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Session AI?
The blueprint ships with mappings for add_to_cart, begin_checkout, login, page, purchase, remove_from_cart, search, sign_up, and more. Any event in your schema can be mapped to Session AI through pipeline configuration without a code change.
Do I need to keep the Session AI tag on my site?
No. Signal delivers to Session AI from the server, so no client-side Session AI script is required on your site.
Other personalisation integrations
Ready to move Session AI server-side?
See how Datafly Signal delivers first-party events to Session AI from infrastructure you control, with hashed identity and consent enforcement built in.