ESP - Responsys



Make sure to read the article Email

Input data

Customer Data Platform (CDP) will pull:

  • Your full master contact list with the latest main subscription status
  • Send/open/click/bounce/subscription/unsubscription events
    • Daily: yes
    • Historical load: Responsys only sends the last 14 days of events. Hence, the email event history will be built mostly based on the daily loads. This means that machine learning models relying on email engagement can only be turned on after two or three months of email pull in order to have enough history.

Output data

CDP pushes audience and content into Responsys supplemental tables. You can choose what field the supplemental tables will contain. You can access the supplemental tables in the CDP folder in the Responsys UI.


CDP can push to different supplemental tables. For instance, you Store Locator campaign can be pushed to the AgilOne_Audience supplemental table while all dispatches of the abandoned cart campaign can go to the AgilOne_AbandonedCart supplemental table (you can use the Exection_ID field to identify today’s audience). Supplemental tables where data from CDP Actions will be pushed need to be pre-configured by the CDP services or support team.



  • Provide CDP with a Responsys admin account

  • Provide access to the Responsys File Server and the corresponding SSH private key

    (do not use a password-protected private key).

  • Provide CDP with an API user and the endpoint URL

  • Ensure that no existing Connector Job is scheduled to extract the key Responsys Events Sent / Clicked / Opened / Opted-In / Launch State.


The CDP Implementation Consultant will create a daily Connect Job to extract daily the updated subscribers and the email activity. Responsys only allows the export of a specific event type once. Therefore, if a Connect job has already been set up to export that type of feed, it will appear greyed out in the Responsys UI when we set up the export job and CDP will not be able to pull it.