Integrations / Advertising
Epsilon
Server-side event delivery to the Epsilon (Conversant / Dotomi) Event API. Forwards page browsing and e-commerce conversion events as DTM-tag query parameters to fp.dotomi.com, with SHA-256 hashed-email matching, IP/User-Agent signals, first-party cookie matching, and TCF/GPP consent strings.
Datafly Signal delivers first-party events to Epsilon server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Epsilon expects.
Why route Epsilon through Datafly Signal
Conversions survive ad blockers and tracking prevention
A browser tag served from an advertising domain is blocked outright for part of your traffic, and Safari's ITP shortens the cookies it can set. Signal sends the event from your own server, so the conversions Epsilon optimises against are not filtered by the browser.
Email hashed before it leaves your infrastructure
Signal normalises (trim and lowercase) and applies SHA-256 inside your own deployment, so Epsilon receives match keys rather than raw personal data.
Client IP and user agent are preserved
Server-to-server delivery normally loses both, which weakens matching. Signal forwards the genuine visitor values as request headers so Epsilon attributes the event to the right session.
One consent decision governs every destination
Epsilon 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
pagepurchaseview_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 Epsilon documentation.
Frequently asked questions
Does Datafly Signal integrate with Epsilon?
Yes. Datafly Signal delivers first-party events to Epsilon server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Epsilon expects. The integration is included in every deployment at no additional cost.
How is server-side Epsilon tracking different from the Epsilon tag?
The Epsilon 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 Epsilon from your server, so delivery does not depend on browser conditions.
What personal data is sent to Epsilon?
Email are normalised and SHA-256 hashed inside your own deployment before delivery, so Epsilon receives match keys rather than raw personal data. Which fields are sent is configured per pipeline.
Which events can Signal send to Epsilon?
The blueprint ships with mappings for page, purchase, view_item. Any event in your schema can be mapped to Epsilon through pipeline configuration without a code change.
Do I need to keep the Epsilon tag on my site?
No. Server-side delivery is designed to replace the tag. Most teams run both briefly during migration, using shared event IDs so Epsilon deduplicates, then remove the tag once server-side volume matches.
Other advertising integrations
Ready to move Epsilon server-side?
See how Datafly Signal delivers first-party events to Epsilon from infrastructure you control, with hashed identity and consent enforcement built in.