Integrations / Analytics
Adobe Identity Service
Cross-solution visitor identity syncing with Adobe Experience Cloud.
Datafly Signal delivers first-party events to Adobe Identity Service server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Adobe Identity Service expects.
Why route Adobe Identity Service through Datafly Signal
Your numbers stop depending on what the browser allows
Client-side analytics loses every visit where the tag is blocked or the page unloads early. Signal delivers from the server, so Adobe Identity Service receives the complete event stream.
Email and phone number hashed before it leaves your infrastructure
Signal normalises (trim and lowercase) and applies SHA-256 inside your own deployment, so Adobe Identity Service receives match keys rather than raw personal data.
One consent decision governs every destination
Adobe Identity Service 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 Adobe Identity Service documentation.
Frequently asked questions
Does Datafly Signal integrate with Adobe Identity Service?
Yes. Datafly Signal delivers first-party events to Adobe Identity Service server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Adobe Identity Service expects. The integration is included in every deployment at no additional cost.
How is server-side Adobe Identity Service tracking different from the Adobe Identity Service tag?
The Adobe Identity Service 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 Adobe Identity Service from your server, so delivery does not depend on browser conditions.
What personal data is sent to Adobe Identity Service?
Email and phone number are normalised and SHA-256 hashed inside your own deployment before delivery, so Adobe Identity Service receives match keys rather than raw personal data. Which fields are sent is configured per pipeline.
Which events can Signal send to Adobe Identity Service?
The blueprint ships with mappings for identify. Any event in your schema can be mapped to Adobe Identity Service through pipeline configuration without a code change.
Do I need to keep the Adobe Identity Service tag on my site?
No. Signal delivers to Adobe Identity Service from the server, so no client-side Adobe Identity Service script is required on your site.
Other analytics integrations
Ready to move Adobe Identity Service server-side?
See how Datafly Signal delivers first-party events to Adobe Identity Service from infrastructure you control, with hashed identity and consent enforcement built in.