Integrations / Marketing Automation
Adobe Journey Optimizer
Stream first-party XDM ExperienceEvents to Adobe Journey Optimizer through the Adobe Experience Platform Edge Network Server API (collect endpoint). Maps Signal events to standard XDM eventTypes (web.webpagedetails.pageViews, commerce.*), emits hashed-email + ECID identities in identityMap, and carries Web Details, Commerce Details, and productListItems so AJO journeys and Real-Time Customer Profile receive complete events.
Datafly Signal delivers first-party events to Adobe Journey Optimizer server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Adobe Journey Optimizer expects.
Why route Adobe Journey Optimizer through Datafly Signal
Profiles update from the server, not the browser
Events reach Adobe Journey Optimizer even when a tracker blocker or a failed page unload would have dropped a client-side call, so the profile reflects what actually happened.
Email hashed before it leaves your infrastructure
Signal normalises (trim and lowercase) and applies SHA-256 inside your own deployment, so Adobe Journey Optimizer receives match keys rather than raw personal data.
Delivery is batched, rate-limited, and retried
Signal buffers to Kafka, respects the Adobe Journey Optimizer rate limit, and retries on 429 or transient failure rather than dropping the event.
One consent decision governs every destination
Adobe Journey Optimizer 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
add_to_cartadd_to_wishlistbegin_checkoutpagepurchaseremove_from_cartsearchview_itemview_item_listVertical presets
Retail / E-commerce. 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 Journey Optimizer documentation.
Frequently asked questions
Does Datafly Signal integrate with Adobe Journey Optimizer?
Yes. Datafly Signal delivers first-party events to Adobe Journey Optimizer server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Adobe Journey Optimizer expects. The integration is included in every deployment at no additional cost.
How is server-side Adobe Journey Optimizer tracking different from the Adobe Journey Optimizer tag?
The Adobe Journey Optimizer 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 Journey Optimizer from your server, so delivery does not depend on browser conditions.
What personal data is sent to Adobe Journey Optimizer?
Email are normalised and SHA-256 hashed inside your own deployment before delivery, so Adobe Journey Optimizer receives match keys rather than raw personal data. Which fields are sent is configured per pipeline.
Which events can Signal send to Adobe Journey Optimizer?
The blueprint ships with mappings for add_to_cart, add_to_wishlist, begin_checkout, page, purchase, remove_from_cart, search, view_item, and more. Any event in your schema can be mapped to Adobe Journey Optimizer through pipeline configuration without a code change.
Do I need to keep the Adobe Journey Optimizer tag on my site?
No. Signal delivers to Adobe Journey Optimizer from the server, so no client-side Adobe Journey Optimizer script is required on your site.
Other marketing automation integrations
Ready to move Adobe Journey Optimizer server-side?
See how Datafly Signal delivers first-party events to Adobe Journey Optimizer from infrastructure you control, with hashed identity and consent enforcement built in.