Oracle Responsys setup for Data Activation

The Data Activation connector for Oracle Responsys enables you to combine the power of customer data management with Responsys's advanced campaign orchestration capabilities. This integration ensures highly personalized and consistent messaging across channels, driving engagement and conversions.

Here's how this connector enhances your marketing efforts:

• Unified customer profiles: Use enriched first-party data to create detailed, actionable customer profiles in Oracle Responsys, enabling precise audience segmentation.

• Hyper-personalized campaigns: Use real-time data to tailor email, SMS, and push notification campaigns based on customer preferences, behaviors, and lifecycle stages.

• Streamlined multichannel marketing: Deliver seamless and coordinated messaging across multiple channels by syncing data streams with Oracle Responsys's powerful orchestration tools.

• Automated data updates: Keep your campaigns agile and relevant by ensuring that customer data flows dynamically between systems without manual intervention.

• Improved campaign ROI: Target high-value segments and optimize retargeting efforts, maximizing engagement and driving higher returns from your marketing campaigns.

• Cross-channel consistency: Align messaging and experiences across all touchpoints, ensuring a unified customer journey that strengthens brand loyalty.

Destination connector overview

Before you begin

Before configuring the Oracle Responsys connector, the following requirements must be met:

• An active Oracle Responsys account

• The server the account is hosted on (needed for determining the authentication endpoint, see Oracle Responsys REST API documentation)

• A Profile list with recipients configured on the Oracle Responsys account that you want to send emails to

• A Custom Event configured on the Oracle Responsys account to be triggered by the connector

Instructions

Step 1: Configure destination

1. On the Data Activation platform, select Connectors in the left-side navigation bar.

2. Select Server to Server and click New Connector.

3. Select Oracle Responsys and fill in the following details:

   • Name: Display name of the partner Server to server integration, used throughout the Data Activation system

   • Username: Username of the account to log in with

   • Password: Password of the account to log in with

   • Authentication endpoint: URL of the authentication endpoint on the server that hosts the account

   • Profile list: Name of the profile list that the recipients of the events are part of

   • Identifier type: Choose one of three identifiers to identify the recipient of the custom event (see below)

Identifier types:

• Oracle Responsys Recipient ID (RIID) (partner number 27): A unique identifier specific to Oracle Responsys

• Hashed Email (partner number 7001): The SHA256 hashed email of the recipient

• CRM ID (partner number 2001): A custom identifier that you have given the recipient

Step 2: Add the destination connector to an Audience or Journey

Adding the Oracle Responsys connector to an audience or journey only requires one additional setting:

• Custom Event name: This name must be the same as the name of the custom event defined in Oracle Responsys platform, used as a trigger in the personalized workflows

Once a profile has been added to an audience or journey and a custom variable is present, it's sent to Oracle Responsys as a property of the Custom Event with that exact name. Two extra properties are always sent:

• profileId: Data Activation profile identifier

• callType: One of ADD, UPDATE, REMOVE signifying the segmenting operation that occurred

Connector limitations and known issues

The Oracle Responsys API runs in a multi-tenant environment with shared resources across users. Responsys monitors how many API requests are submitted from each account and throttles requests from an account if it endangers the level of service to other clients.

The API infrastructure strictly enforces limits to API requests. When the internal capacity limit for the account is reached, API requests fail with error code INTERNAL_CAPACITY_LIMIT_EXCEEDED in the response. This is visible in the error statistics for the connector in the Data Activation.

For more information, see the Oracle Responsys throttling documentation.

Error handling

For the Oracle Responsys connector, we report the actual Oracle Responsys-specific error codes.

Error documentation can be found in the Oracle Responsys error handling documentation.