Adobe Campaign

Datafly Signal triggers Adobe Campaign Standard transactional messages server-to-server using the Message Center real-time event (transactional messaging) REST API. Each Signal event becomes a transactional trigger that Adobe Campaign uses to send a personalised message (email, SMS, or push) to a known profile.

Prerequisites

Before configuring Adobe Campaign in Signal, you need:

• An Adobe Campaign Standard instance with transactional messaging enabled.
• A published transactional event in Campaign (this generates the event ID).
• An Adobe Developer Console project with an OAuth Server-to-Server credential that has access to the Adobe Campaign API.
• Your Adobe IMS Organization ID.

Step 1: Create and publish a transactional event

1. In Adobe Campaign, go to Marketing activities and create a transactional message event (Message Center).
2. Configure the event payload fields and the message template. Template variables reference your context data as <%= context.<field> %> — for example <%= context.firstName %> or <%= context.orderId %>.
3. Publish the event. Unpublished events return 404 from the API.
4. Open the event and note the event ID (for example EVTcartAbandonment) and the transactional API name shown in the API preview (for example mcSubscriptions).

Step 2: Create an OAuth Server-to-Server credential

1. Go to the Adobe Developer Console and create (or open) a project.
2. Add the Adobe Campaign API to the project.
3. When prompted for the credential type, choose OAuth Server-to-Server.
4. After creation, the credential page shows your Client ID (API Key), Client Secret, and the scopes assigned to the credential. Note all three.

Step 3: Find your Organization ID

Your IMS Organization ID looks like ABC123DEF456@AdobeOrg. You can find it in the Adobe Developer Console project overview, or in the Adobe Admin Console under your organisation settings.

Configuration

Signal needs the following values to deliver events to Adobe Campaign:

Configure in Signal

API Endpoint

Signal delivers each event as a POST to the Campaign Standard transactional event endpoint:

POST https://mc.adobe.io/{organization}/campaign/{transactional_api}/{event_id}

All three path segments come from your integration configuration. Authentication uses an Adobe IMS bearer token (minted automatically by Signal from your OAuth Server-to-Server credential) plus the X-Api-Key header:

Authorization: Bearer <access_token>
X-Api-Key: <client_id>
Content-Type: application/json;charset=utf-8

Signal obtains the bearer token from the Adobe IMS token endpoint (https://ims-na1.adobelogin.com/ims/token/v3) using the client_credentials grant and caches it until it expires (tokens are valid for roughly 24 hours).

Identity Signals

Adobe Campaign transactional messages target a known profile, identified by email at the payload root. The email address is taken from the visitor’s identity traits ($traits.email).

Event Mapping

The default blueprint sends the profile email at the root and all personalisation fields under ctx. Your Campaign message template references these as context.<field>.

Example: Order Completed

A Datafly.js call like this:

datafly.track('Order Completed', {
  order_id: 'ORD-1042',
  revenue: 125.00,
  currency: 'GBP',
  coupon: 'WELCOME10'
});

with the visitor’s email identified as jack@example.com, produces this request body to Adobe Campaign:

{
  "email": "jack@example.com",
  "ctx": {
    "firstName": "Jack",
    "userId": "user-77",
    "orderId": "ORD-1042",
    "orderAmount": 125.00,
    "currency": "GBP",
    "coupon": "WELCOME10",
    "marketingConsent": "true",
    "eventTimestamp": "2026-06-06T10:15:30Z"
  }
}

Adobe Campaign responds with a primary key and status:

{
  "PKey": "@xyz...",
  "status": "pending",
  "href": "mc.adobe.io/.../EVTcartAbandonment/@xyz..."
}

Default event map

All events also carry the global fields: email (root), firstName, lastName, userId, anonymousId, eventTimestamp, and marketingConsent. Events not in the map are dropped.

Consent

Marketing consent is forwarded as ctx.marketingConsent (true / false), derived from Signal’s canonical marketing consent category. Your Campaign workflow or message template can use this value to gate optional content. Because these are transactional messages tied to a specific profile action, they are typically sent regardless of marketing consent — confirm your own legal basis before relying on the consent flag to suppress sends.

Testing

1. In the Signal management UI, open the Event Debugger for the pipeline with Adobe Campaign attached.
2. Send a test Order Completed event with a known email address.
3. Confirm the delivery shows a 200/201 response with "status": "pending" and a PKey.
4. In Adobe Campaign, open the transactional event and check the delivery logs for the message.

Troubleshooting