Integrations / Marketing Automation
Dotdigital
Server-side delivery of Signal events to Dotdigital as transactional (insight) data records attached to a contact via the v2 transactional-data API. Each event becomes a record keyed by message id, identified by the contact's email, with the event name and properties stored under the json object for use in Dotdigital programs, automations and segments.
Datafly Signal delivers first-party events to Dotdigital server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Dotdigital expects.
Why route Dotdigital through Datafly Signal
Profiles update from the server, not the browser
Events reach Dotdigital 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
Dotdigital 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_checkoutpagepurchasesearchsign_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 Dotdigital documentation.
Frequently asked questions
Does Datafly Signal integrate with Dotdigital?
Yes. Datafly Signal delivers first-party events to Dotdigital server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Dotdigital expects. The integration is included in every deployment at no additional cost.
How is server-side Dotdigital tracking different from the Dotdigital tag?
The Dotdigital 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 Dotdigital from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Dotdigital?
The blueprint ships with mappings for add_to_cart, begin_checkout, page, purchase, search, sign_up, view_item. Any event in your schema can be mapped to Dotdigital through pipeline configuration without a code change.
Do I need to keep the Dotdigital tag on my site?
No. Signal delivers to Dotdigital from the server, so no client-side Dotdigital script is required on your site.
Other marketing automation integrations
Ready to move Dotdigital server-side?
See how Datafly Signal delivers first-party events to Dotdigital from infrastructure you control, with hashed identity and consent enforcement built in.