Integrations / Personalisation
Split
Server-side event delivery to Split (Harness Feature Management & Experimentation) via the Events API. Maps Signal events to Split eventTypeId values keyed by the visitor's traffic key so behavioural events attribute to feature-flag treatments and feed experiment metrics. No PII hashing — Split matches on key alone.
Datafly Signal delivers first-party events to Split server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Split expects.
Why route Split through Datafly Signal
Profiles update from the server, not the browser
Events reach Split even when a tracker blocker or a failed page unload would have dropped a client-side call, so the profile reflects what actually happened.
One consent decision governs every destination
Split 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_checkoutgenerate_leadpagepurchasesearchsign_upview_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 Split documentation.
Frequently asked questions
Does Datafly Signal integrate with Split?
Yes. Datafly Signal delivers first-party events to Split server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Split expects. The integration is included in every deployment at no additional cost.
How is server-side Split tracking different from the Split tag?
The Split 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 Split from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Split?
The blueprint ships with mappings for add_to_cart, begin_checkout, generate_lead, page, purchase, search, sign_up, view_item. Any event in your schema can be mapped to Split through pipeline configuration without a code change.
Do I need to keep the Split tag on my site?
No. Signal delivers to Split from the server, so no client-side Split script is required on your site.
Other personalisation integrations
Ready to move Split server-side?
See how Datafly Signal delivers first-party events to Split from infrastructure you control, with hashed identity and consent enforcement built in.