Responsys
Overview
Responsys, also known as Oracle Responsys, is a platform to manage interactions with your customers across email, mobile, social, display, and the web.
Integrating Lytics with Responsys allows you to import users and their activity data to build behavioral audiences and gain Insights in Lytics. You can then export Lytics audiences back to Responsys to refine your targeting and deliver personalized messaging.
Responsys has the following job type(s):
Authorization
If you haven't already done so, you will need to set up a Responsys account before you begin the process described below. If you are new to creating authorizations in Lytics, see the Authorizations Dashboard documentation for more information.
- Select Responsys from the the list of providers.
- Select the method for authorization. Note that different methods may support different job types. Responsys supports the following authorization methods:
Responsys Interact
Responsys Interact you will need the following credentials, username, password and endpoint URI .
- In the Label text box, enter a name for the authorization
- (optional) In the Description text box, enter a description for this authorization
- In the Username text box, enter your Username credential.
- In the Password password box, enter your Password credential.
- In the Endpoint URI text box, enter Endpoint URI should look like either, login2.responsys.net, login.rsys8.net, or AccountToken-api.responsys.ocs.oraclecloud.com.
Responsys SFTP Server
Responsys SFTP Server you will need the following credentials.
- In the Label text box, enter a name for the authorization
- (optional) In the Description text box, enter a description for this authorization
- In the Host text box, enter your Host credential.
- In the Port numeric field, enter your Port credential.
- In the Username text box, enter your Username credential.
- In the Private Key text box, enter your Private Key credential.
- (optional) In the Folder text box, enter Folder path to place files.
Responsys SFTP Server with PGP
Responsys SFTP Server with PGP you will need the following credentials.
- In the Label text box, enter a name for the authorization
- (optional) In the Description text box, enter a description for this authorization
- In the Host text box, enter your Host credential.
- In the Port numeric field, enter your Port credential.
- In the Username text box, enter your Username credential.
- In the SFTP Private Key text box, enter your SFTP Private Key credential.
- (optional) In the Folder text box, enter Folder path to place files.
- In the PGP Private Key text box, enter your PGP Private Key credential.
- In the PGP Private Key Passphrase text box, enter your PGP Private Key Passphrase credential.
Responsys: Export Audience
Authorization
Export Audience supports the following authorization types:
Integration Details
- Implementation Type: Server-side
- Implementation Technique: REST API
- Frequency: Real-time
- Resulting data:User profiles
Steps/Pattern:
This integration utilizes the Oracle Response Marketing Cloud APIs to send user data. Once the export is started the job will:
- Scan the Lytics audience and hash the selected user identifiers, i.e. email or Responsys ID, etc and create a batch of IDs
- Every 200 users or 10 minutes, whichever is first, the batch is sent to Responsys.
- The export will run continuously. As users enter or exit the Lytics audience, they will be added to a queue.
Fields
By default, Lytics exports the following fields to Responsys [REPLACE ME](note which fields are configurable):
Lytics User Field | Description | Responsys Field | Type |
---|---|---|---|
Email Address | string | ||
Configuration
Follow these steps to set up and configure an export job for Responsys in the Lytics platform. If you are new to creating jobs in Lytics, see the Jobs Dashboard documentation for more information.
- Select Responsys from the list of providers.
- Select the export job type from the list.
- Select the Authorization you would like to use or create a new one.
- Enter a Label to identify this job you are creating in Lytics.
- (Optional) Enter a Description for further context on your job.
- From the Source Audience input, select the Lytics audience to export to Resonsys.
- From the List input, select the list in Responsys that you'd like to export data to.
- From the ID Mappings input, map the Lytics user field to a Responsys Identifier field. At least one identifier must be mapped.
- From the Match Column 1 input, select the Responsys identifier to be used as the main identifier. This identifier must be mapped above.
- From the Match Column 2 input, optionally select a Responsys identifier to be used as a secondary identifier. If selected, the identifier must be mapped above.
- (optional) From the Additional Fields input, select up to 29 user fields to export to Lytics_User_Fields extension table.
- (optional) From the Fields Table input, select a fields extension table to write to. If none is selected, a new extension table LyticsUser_Fields{Job ID} will be created. Note the field names must match the Lytics field names.
- (optional) From the Export Audience Memberships input, select select up to 29 Lytics Audience names to export to Lytics_Segments extension table.
- Click the Complete button to start the job.
Responsys: Import Activity Data
Authorization
Import Activity Data supports the following authorization types:
Integration Details
- Implementation Type:Server-side
- Implementation Technique: REST API
- Frequency:Batch
- Resulting data: User profiles
Steps/Pattern:
- Request a single event for download.
- Ingest the data from the JSON files into the stream.
Fields
The following fields are included in the default mapping of the responsys_events
stream:
Source Field | Lytics User Field | Description | Type |
---|---|---|---|
campaign_id | rs_campaign_id | Responsys Campaign ID | string |
count(event) | email_bounce_ct | Email Bounced | int |
count(event) | email_click_ct | Email Clicked | int |
count(event) | email_complaint_ct | Email Complaint | int |
count(event) | email_open_ct | Email Opened | int |
count(event) | email_opt_in_ct | Email Opted-In | int |
count(event) | email_opt_out_ct | Email Opted-Out | int |
count(event) | email_sent_ct | Email Sent | int |
count(event) | sms_bounce_ct | SMS Failed | int |
count(event) | sms_open_ct | SMS Delivered | int |
count(event) | sms_opt_in_ct | SMS Opted-In | int |
count(event) | sms_opt_out_ct | SMS Opted-Out | int |
count(event) | sms_sent_ct | SMS Sent | int |
email(email) | email unique id | string | |
emaildomain(email) | email_domain | Email Domain | string |
map("email", epochms()) | last_channel_activities | Last Activity By Channel | map[string]time |
max(epochms()) | email_last_bounce_ts | Last Email Bounced | date |
max(epochms()) | email_last_click_ts | Email Last click | date |
max(epochms()) | email_last_complaint_ts | Last Email Complaint | date |
max(epochms()) | email_last_open_ts | Email Last open | date |
max(epochms()) | email_last_opt_in_ts | Last Email Opted-In | date |
max(epochms()) | email_last_opt_out_ts | Last Email Opted-Out | date |
max(epochms()) | email_last_sent_ts | Last Email Sent | date |
max(epochms()) | last_active_ts | Last Active | date |
max(epochms()) | sms_last_bounce_ts | Last SMS Failed | date |
max(epochms()) | sms_last_open_ts | Last SMS Delivered | date |
max(epochms()) | sms_last_opt_in_ts | Last SMS Opted-In | date |
max(epochms()) | sms_last_opt_out_ts | Last SMS Opted-Out | date |
max(epochms()) | sms_last_sent_ts | Last SMS Sent | date |
min(epochms()) | email_first_bounce_ts | First Email Bounced | date |
min(epochms()) | email_first_click_ts | Email First click | date |
min(epochms()) | email_first_complaint_ts | First Email Complaint | date |
min(epochms()) | email_first_open_ts | First Email Opened | date |
min(epochms()) | email_first_opt_in_ts | First Email Opted-In | date |
min(epochms()) | email_first_opt_out_ts | First Email Opted-Out | date |
min(epochms()) | email_first_sent_ts | First Email Sent | date |
min(epochms()) | sms_first_bounce_ts | First SMS Failed | date |
min(epochms()) | sms_first_open_ts | First SMS Delivered | date |
min(epochms()) | sms_first_opt_in_ts | First SMS Opted-In | date |
min(epochms()) | sms_first_opt_out_ts | First SMS Opted-Out | date |
min(epochms()) | sms_first_sent_ts | First SMS Sent | date |
mobile_number | phone | Phone Number | string |
riid | rs_user_id unique id | Responsys Id | string |
set("email") | channels | All Channels Used | []string |
set(list_id) | rs_list_id | Responsys List ID | []string |
set(offer_category) | rs_categories | Responsys Offer Categories | []string |
set(offer_name) | rs_offers | Responsys Offer Names | []string |
set(offer_url) | email_urls | Email Urls | []string |
set(segment_info) | rs_segments | Responsys Segments | []string |
valuect(hash(urlmain(offer_url))) | hashedurls | Hashed Urls Visited | map[string]intsum |
valuect(hourofday()) | hourly | Events By Hour | map[string]intsum |
valuect(hourofweek()) | hour_of_week | Hour of Week Events | map[string]intsum |
valuect(monthofyear()) | month_of_year | Month of Year Events | map[string]intsum |
Configuration
Follow these steps to set up and configure an import job for Responsys in the Lytics platform. If you are new to creating jobs in Lytics, see the Jobs Dashboard documentation for more information.
- Select Responsys from the list of providers.
- Select the import job type from the list.
- Select the Authorization you would like to use or create a new one.
- Enter a Label to identify this job you are creating in Lytics.
- (Optional) Enter a Description for further context on your job.
- Complete the configuration steps for your job.
- From the Folder input, select .
- From the Account Ids input, select account Ids are detected from the files in the folder.
- (optional) In the Custom Delimiter text box, enter designate a custom delimiter for your file. Default delimiter is ",". A recommended custom delimiter is "|" (pipe).
- Click the Start job button to start the job.
Responsys: Export Audiences to Campaign
Authorization
Export Audiences to Campaign supports the following authorization types:
Integration Details
- Implementation Type: Server-side
- Implementation Technique: REST API
- Frequency: Real-time
- Resulting data: User profiles
Steps/Pattern:
- Request a single event for download.
- Ingest the data from the JSON files into the stream...
Fields
By default, Lytics exports the following fields to Responsys.
Lytics User Field | Description | Responsys Field | Type |
---|---|---|---|
Email Address | string | ||
Configuration
Follow these steps to set up and configure an export job for Responsys in the Lytics platform. If you are new to creating jobs in Lytics, see the Jobs Dashboard documentation for more information.
- Select Responsys from the list of providers.
- Select the export job type from the list.
- Select the Authorization you would like to use or create a new one.
- Enter a Label to identify this job you are creating in Lytics.
- (Optional) Enter a Description for further context on your job.
- Select the audience to export.
- Complete the configuration steps for your job.
- From the Email Field input, select select the email field that you want to export to Responsys.
- From the Campaign input, select the Campaign in Responsys that you'd like to export data to trigger emails
- (optional) Select the Back Fill checkbox, to send users that are already members of the audience selected.
- (optional) From the Additional Fields input, select select up to 29 user fields to export to Lytics_User_Fields extension table.
- Click the Complete button to start the job.
Updated 5 days ago