Integrations / Personalisation

Adobe Target

Server-side notifications to the Adobe Target Delivery API. Records page-view display notifications and order/conversion notifications (with revenue and purchased product IDs) against a configured mbox, keyed on the durable Target tntId. Unauthenticated REST POST scoped by clientCode.

Datafly Signal delivers first-party events to Adobe Target server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Adobe Target expects.

Why route Adobe Target through Datafly Signal

Profiles update from the server, not the browser

Events reach Adobe Target 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

Adobe Target 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

pagepurchase

Vertical 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 Adobe Target documentation.

Frequently asked questions

Does Datafly Signal integrate with Adobe Target?

Yes. Datafly Signal delivers first-party events to Adobe Target server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Adobe Target expects. The integration is included in every deployment at no additional cost.

How is server-side Adobe Target tracking different from the Adobe Target tag?

The Adobe Target 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 Target from your server, so delivery does not depend on browser conditions.

Which events can Signal send to Adobe Target?

The blueprint ships with mappings for page, purchase. Any event in your schema can be mapped to Adobe Target through pipeline configuration without a code change.

Do I need to keep the Adobe Target tag on my site?

No. Signal delivers to Adobe Target from the server, so no client-side Adobe Target script is required on your site.

Ready to move Adobe Target server-side?

See how Datafly Signal delivers first-party events to Adobe Target from infrastructure you control, with hashed identity and consent enforcement built in.