Integrations / CRM
Kustomer
Server-side identity + tracking-event delivery to Kustomer via /v1/tracking/identityEvent. Each Signal event identifies the customer (by email and external ID) and records a named tracking event on their Kustomer timeline, with event properties mapped into event.meta following Kustomer's Num/At key conventions.
Datafly Signal delivers first-party events to Kustomer server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Kustomer expects.
Why route Kustomer through Datafly Signal
Profiles update from the server, not the browser
Events reach Kustomer 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
Kustomer 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_checkoutloginpagepurchasesearchsign_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 Kustomer documentation.
Frequently asked questions
Does Datafly Signal integrate with Kustomer?
Yes. Datafly Signal delivers first-party events to Kustomer server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Kustomer expects. The integration is included in every deployment at no additional cost.
How is server-side Kustomer tracking different from the Kustomer tag?
The Kustomer 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 Kustomer from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Kustomer?
The blueprint ships with mappings for add_to_cart, begin_checkout, login, page, purchase, search, sign_up, view_item. Any event in your schema can be mapped to Kustomer through pipeline configuration without a code change.
Do I need to keep the Kustomer tag on my site?
No. Signal delivers to Kustomer from the server, so no client-side Kustomer script is required on your site.
Ready to move Kustomer server-side?
See how Datafly Signal delivers first-party events to Kustomer from infrastructure you control, with hashed identity and consent enforcement built in.