Integrations / Personalisation
Talon.One
Server-side event delivery to the Talon.One Integration API (Track Event V2, POST /v2/events). Maps Signal events to Talon.One custom events with a required profileId (user_id, anonymous_id fallback) so the Rule Engine can drive promotions, coupons, loyalty, and referrals. Each custom event type and every attribute must be pre-declared in the Campaign Manager.
Datafly Signal delivers first-party events to Talon.One server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Talon.One expects.
Why route Talon.One through Datafly Signal
Profiles update from the server, not the browser
Events reach Talon.One 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
Talon.One 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_checkoutloginpagepurchaserefundsign_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 Talon.One documentation.
Frequently asked questions
Does Datafly Signal integrate with Talon.One?
Yes. Datafly Signal delivers first-party events to Talon.One server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Talon.One expects. The integration is included in every deployment at no additional cost.
How is server-side Talon.One tracking different from the Talon.One tag?
The Talon.One 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 Talon.One from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Talon.One?
The blueprint ships with mappings for add_to_cart, begin_checkout, login, page, purchase, refund, sign_up, view_item. Any event in your schema can be mapped to Talon.One through pipeline configuration without a code change.
Do I need to keep the Talon.One tag on my site?
No. Signal delivers to Talon.One from the server, so no client-side Talon.One script is required on your site.
Other personalisation integrations
Ready to move Talon.One server-side?
See how Datafly Signal delivers first-party events to Talon.One from infrastructure you control, with hashed identity and consent enforcement built in.