Integrations / Advertising
LiveIntent
Server-to-server conversion delivery to the LiveIntent Conversions API. Maps Signal events to LiveIntent conversion signals keyed on the visitor's hashed email (MD5 + SHA-256), IP, and user agent, with purchase value for revenue attribution. Events are sent as a bare JSON array (up to 100 per request) with eventTime in epoch seconds.
Datafly Signal delivers first-party events to LiveIntent server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload LiveIntent expects.
Why route LiveIntent 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 LiveIntent 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 LiveIntent receives match keys rather than raw personal data.
Client IP and user agent are carried in the payload
Both are taken from the original visitor request rather than your server, which is what LiveIntent needs to attribute the event to the right session.
One consent decision governs every destination
LiveIntent 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 LiveIntent documentation.
Frequently asked questions
Does Datafly Signal integrate with LiveIntent?
Yes. Datafly Signal delivers first-party events to LiveIntent server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload LiveIntent expects. The integration is included in every deployment at no additional cost.
How is server-side LiveIntent tracking different from the LiveIntent tag?
The LiveIntent 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 LiveIntent from your server, so delivery does not depend on browser conditions.
What personal data is sent to LiveIntent?
Email are normalised and SHA-256 hashed inside your own deployment before delivery, so LiveIntent receives match keys rather than raw personal data. Which fields are sent is configured per pipeline.
Which events can Signal send to LiveIntent?
The blueprint ships with mappings for page, purchase, view_item. Any event in your schema can be mapped to LiveIntent through pipeline configuration without a code change.
Do I need to keep the LiveIntent 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 LiveIntent deduplicates, then remove the tag once server-side volume matches.
Other advertising integrations
Ready to move LiveIntent server-side?
See how Datafly Signal delivers first-party events to LiveIntent from infrastructure you control, with hashed identity and consent enforcement built in.