Integrations / Marketing Automation
Cordial
Server-side delivery of first-party behavioural events to Cordial as contact activities via the v2 REST API. Maps Signal events to Cordial's standard actions (browse, cart, order, search) plus snake_case custom actions, keyed on contact email with timestamps as ISO 8601 (ats). Powers cross-channel journeys, browse/cart-abandonment, and audience segmentation.
Datafly Signal delivers first-party events to Cordial server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Cordial expects.
Why route Cordial through Datafly Signal
Profiles update from the server, not the browser
Events reach Cordial 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
Cordial 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_upsubscription_startedview_itemVertical presets
Retail, B2B / SaaS. 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 Cordial documentation.
Frequently asked questions
Does Datafly Signal integrate with Cordial?
Yes. Datafly Signal delivers first-party events to Cordial server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Cordial expects. The integration is included in every deployment at no additional cost.
How is server-side Cordial tracking different from the Cordial tag?
The Cordial 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 Cordial from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Cordial?
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 Cordial through pipeline configuration without a code change.
Do I need to keep the Cordial tag on my site?
No. Signal delivers to Cordial from the server, so no client-side Cordial script is required on your site.
Other marketing automation integrations
Ready to move Cordial server-side?
See how Datafly Signal delivers first-party events to Cordial from infrastructure you control, with hashed identity and consent enforcement built in.