Oracle Responsys

Datafly Signal delivers events to Oracle Responsys Marketing Cloud server-to-server using the Trigger Custom Event REST API (v1.3). Each Signal event triggers a named Responsys custom event for the matched profile-list member, which then runs your Responsys Program logic (for example, entering the contact into a welcome or abandoned-cart journey).

Prerequisites

Before configuring Oracle Responsys in Signal you need:

• A Responsys account with REST API access enabled.
• A Custom Event defined in Responsys (Data > Events). For near-real-time messaging, the event must be of type Real-time.
• A Profile List that already contains the contacts you want to enact, with a match key (email address recommended).
• Responsys API credentials (username + password) to obtain an auth token.

Step 1: Find your API endpoint

1. In Responsys, go to Account > Global settings > Account configuration.
2. Copy the value of the WS End Point field. For Global Routing accounts this looks like https://ACCOUNTTOKEN-api.responsys.ocs.oraclecloud.com.

This is your account-specific REST base URL. It is also returned as endPoint in the authentication response.

Step 2: Create the custom event

1. Go to Data > Events and create (or note the name of) the custom event you want Signal to trigger.
2. Attach that event as the entry trigger of the Program / campaign you want enacted.

Step 3: Obtain an auth token

Responsys uses a two-stage authentication flow. Authenticate with your username and password to receive a token (valid for 2 hours):

curl -X POST "https://login.rsys9.net/rest/api/v1.3/auth/token" \
  -H "Content-Type: application/x-www-form-urlencoded" \
  -d "user_name=YOUR_USERNAME&password=YOUR_PASSWORD&auth_type=password"

The response returns the token and your endpoint:

{
  "authToken": "abc123...",
  "issuedAt": 1645123456789,
  "endPoint": "https://ACCOUNTTOKEN-api.responsys.ocs.oraclecloud.com"
}

Configure in Signal

Configuration Fields

Management UI Setup

1. Go to Integrations > Add Integration > Oracle Responsys.
2. Choose the Default preset.
3. Enter your api_endpoint, auth_token, event_name, folder_name, and list_name.
4. Select the consent category that maps to marketing (typically marketing).
5. Click Save.

API Endpoint

POST {api_endpoint}/rest/api/v1.3/events/{event_name}
Authorization: {auth_token}
Content-Type: application/json

The auth token is sent as the literal value of the Authorization header — there is no Bearer prefix.

Identity Signals

Responsys matches the incoming recipient against an existing member of the configured profile list. It uses the first non-null of these keys, in order:

How to send user data

Call datafly.identify() when a user logs in, registers, or submits a form so the email trait is available to match against your profile list:

datafly.identify("user-123", {
  email: "jane.doe@example.com"
});

Event Mapping

Default preset

Every event triggers the same configured event_name; event-specific context is passed as Responsys optionalData name/value pairs. All other events are dropped (defaults.action: drop).

Example: Order Completed

Datafly.js call:

datafly.identify("user-123", { email: "jane.doe@example.com" });
 
datafly.track("Order Completed", {
  order_id: "ORD-001",
  revenue: 129.99,
  currency: "USD"
});

Responsys payload sent by Signal (POST {api_endpoint}/rest/api/v1.3/events/{event_name}):

{
  "recipientData": [
    {
      "recipient": {
        "emailAddress": "jane.doe@example.com",
        "customerId": "user-123",
        "listName": {
          "folderName": "WS_REST_SAMPLE",
          "objectName": "CONTACTS_LIST"
        },
        "emailFormat": "HTML_FORMAT"
      },
      "optionalData": [
        { "name": "ORDER_ID", "value": "ORD-001" },
        { "name": "ORDER_TOTAL", "value": "129.99" },
        { "name": "CURRENCY", "value": "USD" },
        { "name": "MARKETING_CONSENT", "value": "I" },
        { "name": "ANONYMOUS_ID", "value": "a1b2c3d4..." }
      ]
    }
  ]
}

Consent

Signal maps the canonical marketing consent state to a Responsys opt flag in optionalData:

Map this field to your profile list’s opt-in/opt-out column so Responsys respects the contact’s marketing preference.

Testing Your Integration

datafly.identify("test-user", { email: "test@example.com" });
datafly.track("Order Completed", { order_id: "TEST-1", revenue: 1, currency: "USD" });

Troubleshooting