Integrations / Marketing Automation
Sailthru (Marigold)
Server-side custom-event delivery to Marigold Engage by Sailthru via the Event API (POST https://api.sailthru.com/event). Submits named events keyed to a user profile (by email, Sailthru id, or sailthru_hid cookie) with event properties carried as Sailthru vars, so events can trigger Lifecycle Optimizer flows, Smart Strategies, and triggers. Sends the raw email as the profile key — Sailthru matches on real email, not a hashed value.
Datafly Signal delivers first-party events to Sailthru (Marigold) server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Sailthru (Marigold) expects.
Why route Sailthru (Marigold) through Datafly Signal
Profiles update from the server, not the browser
Events reach Sailthru (Marigold) 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
Sailthru (Marigold) 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_cartadd_to_wishlistbegin_checkoutpagepurchaserefundsearchsign_upview_cartview_itemFull field mappings, configuration fields, and troubleshooting are in the Sailthru (Marigold) documentation.
Frequently asked questions
Does Datafly Signal integrate with Sailthru (Marigold)?
Yes. Datafly Signal delivers first-party events to Sailthru (Marigold) server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Sailthru (Marigold) expects. The integration is included in every deployment at no additional cost.
How is server-side Sailthru (Marigold) tracking different from the Sailthru (Marigold) tag?
The Sailthru (Marigold) 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 Sailthru (Marigold) from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Sailthru (Marigold)?
The blueprint ships with mappings for add_to_cart, add_to_wishlist, begin_checkout, page, purchase, refund, search, sign_up, and more. Any event in your schema can be mapped to Sailthru (Marigold) through pipeline configuration without a code change.
Do I need to keep the Sailthru (Marigold) tag on my site?
No. Signal delivers to Sailthru (Marigold) from the server, so no client-side Sailthru (Marigold) script is required on your site.
Other marketing automation integrations
Ready to move Sailthru (Marigold) server-side?
See how Datafly Signal delivers first-party events to Sailthru (Marigold) from infrastructure you control, with hashed identity and consent enforcement built in.