Integrations / Marketing Automation
Adobe Campaign
Trigger Adobe Campaign Standard transactional messages (Message Center real-time events) server-to-server. Each Signal event becomes a transactional trigger keyed on the profile email; personalisation data (name, page, order, cart) is delivered under the ctx object for the Campaign message template (context.<field>). Auth via Adobe IMS OAuth Server-to-Server.
Datafly Signal delivers first-party events to Adobe Campaign server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Adobe Campaign expects.
Why route Adobe Campaign through Datafly Signal
Profiles update from the server, not the browser
Events reach Adobe Campaign even when a tracker blocker or a failed page unload would have dropped a client-side call, so the profile reflects what actually happened.
Token lifecycle is handled for you
Signal obtains and refreshes the OAuth credentials Adobe Campaign requires, so nothing expires quietly in the middle of a campaign.
One consent decision governs every destination
Adobe Campaign 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
pagepurchasesign_upVertical 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 Campaign documentation.
Frequently asked questions
Does Datafly Signal integrate with Adobe Campaign?
Yes. Datafly Signal delivers first-party events to Adobe Campaign server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Adobe Campaign expects. The integration is included in every deployment at no additional cost.
How is server-side Adobe Campaign tracking different from the Adobe Campaign tag?
The Adobe Campaign 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 Campaign from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Adobe Campaign?
The blueprint ships with mappings for page, purchase, sign_up. Any event in your schema can be mapped to Adobe Campaign through pipeline configuration without a code change.
Do I need to keep the Adobe Campaign tag on my site?
No. Signal delivers to Adobe Campaign from the server, so no client-side Adobe Campaign script is required on your site.
Other marketing automation integrations
Ready to move Adobe Campaign server-side?
See how Datafly Signal delivers first-party events to Adobe Campaign from infrastructure you control, with hashed identity and consent enforcement built in.