Integrations / Marketing Automation
Omnisend
Server-side delivery of customer events to Omnisend's Customer Events API (POST /v5/events) to trigger email and SMS automation workflows. Maps identity-bearing Signal events (sign-ups, product views, cart, purchase) with email/phone contact identifiers and routes event detail into Omnisend custom-event properties. Omnisend requires a contact identifier on every event, so anonymous events are dropped.
Datafly Signal delivers first-party events to Omnisend server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Omnisend expects.
Why route Omnisend through Datafly Signal
Profiles update from the server, not the browser
Events reach Omnisend 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
Omnisend 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_checkoutpagepurchasesign_upview_itemVertical presets
Ecommerce. 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 Omnisend documentation.
Frequently asked questions
Does Datafly Signal integrate with Omnisend?
Yes. Datafly Signal delivers first-party events to Omnisend server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Omnisend expects. The integration is included in every deployment at no additional cost.
How is server-side Omnisend tracking different from the Omnisend tag?
The Omnisend 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 Omnisend from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Omnisend?
The blueprint ships with mappings for add_to_cart, begin_checkout, page, purchase, sign_up, view_item. Any event in your schema can be mapped to Omnisend through pipeline configuration without a code change.
Do I need to keep the Omnisend tag on my site?
No. Signal delivers to Omnisend from the server, so no client-side Omnisend script is required on your site.
Other marketing automation integrations
Ready to move Omnisend server-side?
See how Datafly Signal delivers first-party events to Omnisend from infrastructure you control, with hashed identity and consent enforcement built in.