Integrations / Identity Resolution
LiveRamp
Identity resolution and data connectivity for LiveRamp.
Datafly Signal delivers first-party events to LiveRamp server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload LiveRamp expects.
Why route LiveRamp through Datafly Signal
Delivery happens server-to-server
Signal sends events to LiveRamp from your own infrastructure rather than from the visitor's browser, so delivery does not depend on client-side conditions.
Email, phone number, first name and last name hashed before it leaves your infrastructure
Signal normalises (trim and lowercase) and applies SHA-256 inside your own deployment, so LiveRamp receives match keys rather than raw personal data.
Delivery is batched, rate-limited, and retried
Signal buffers to Kafka, respects the LiveRamp rate limit, and retries on 429 or transient failure rather than dropping the event.
One consent decision governs every destination
LiveRamp 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
identifyVertical presets
General. 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 LiveRamp documentation.
Frequently asked questions
Does Datafly Signal integrate with LiveRamp?
Yes. Datafly Signal delivers first-party events to LiveRamp server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload LiveRamp expects. The integration is included in every deployment at no additional cost.
How is server-side LiveRamp tracking different from the LiveRamp tag?
The LiveRamp 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 LiveRamp from your server, so delivery does not depend on browser conditions.
What personal data is sent to LiveRamp?
Email, phone number, first name and last name are normalised and SHA-256 hashed inside your own deployment before delivery, so LiveRamp receives match keys rather than raw personal data. Which fields are sent is configured per pipeline.
Which events can Signal send to LiveRamp?
The blueprint ships with mappings for identify. Any event in your schema can be mapped to LiveRamp through pipeline configuration without a code change.
Do I need to keep the LiveRamp tag on my site?
No. Signal delivers to LiveRamp from the server, so no client-side LiveRamp script is required on your site.
Ready to move LiveRamp server-side?
See how Datafly Signal delivers first-party events to LiveRamp from infrastructure you control, with hashed identity and consent enforcement built in.