Responsys is a third-party email execution engine used by RPI to deliver interaction emails.
The following channel-specific fields are shown for Responsys email channels:
•Re-subscribe contacts: as per Salesforce Marketing Cloud email channel.
•Recipient email: as per Salesforce Marketing Cloud email channel.
•Service Credentials section, containing the following:
o API service URL: this mandatory text field represents the URL used to connect to the Responsys service. It can be a maximum of 1000 characters in length, and defaults to the value 'https://login2.responsys.net/'.
o Username: this mandatory text field can be a maximum of 100 characters in length.
o Password: this password-masked mandatory field can be a maximum of 100 characters in length.
•FTP Credentials section, containing the following:
o FTP server host address: this mandatory text field can be a maximum of 1000 characters in length.
o SSH2 key: this mandatory text field represents the Private key file used to authenticate to the Responsys file server using public key cryptography. You can browse for a private key file using the Windows file system dialog. Having done so, you can clear the selected file.
o SFTP username: this mandatory text field can be a maximum of 100 characters in length.
o SFTP password: this password-masked mandatory field can be a maximum of 100 characters in length.
•Campaign Options section, containing the following:
o Exported event path: this mandatory text field represents the directory in the Responsys file server where contact event data are to be exported. It can be a maximum of 1000 characters in length.
o Profile list: this mandatory text field represents name of the profile list to associate with Responsys campaigns. It can be a maximum of 100 characters in length.
o Root folder: this mandatory text field represents the name of the root folder used to upload email content. It can be a maximum of 1000 characters in length.
o Link table: this mandatory text field represents the name of the link table located in the same folder as the profile list. It can be a maximum of 100 characters in length.
•Suppressions section, containing the following:
o Auto-suppress: as per Salesforce Marketing Cloud email channel.
o Custom suppression table: as per Salesforce Marketing Cloud email channel.
o Suppression table name: as per Salesforce Marketing Cloud email channel.
•Launch Options section, containing the following:
o Progress report email: this optional text field represents the email address to which the Responsys campaign launch status will be emailed. It can be a maximum of 1000 characters in length.
o Progress chunk: this dropdown field allows you to define the limit of messages sent per hour when a Responsys campaign is launched. It exposes the following values:
§ 10K (the default)
§ 50K
§ 100K
§ 500K
§ 1M
•Miscellaneous section, containing the following:
o Remove default text footer: as per Salesforce Marketing Cloud email channel.
The following properties are exposed at the Advanced tab:
•Import via file: as per Salesforce Marketing Cloud email channel.
•Import table suffix: as per Salesforce Marketing Cloud email channel.
•Import FTP location: as per Salesforce Marketing Cloud email channel.
•Enable trace: this checkbox is unchecked by default. When checked, on email execution, information messages containing Responsys trace HTTP request and reply details are written to the server log.
Note the following message, which is displayed when the property is checked:
•API call max. re-try: this integer property defaults to 10, and accepts a range of values from 5 to 60. It represents the number of retry attempts to be undertaken if a call to the provider's API fails.
•Move hashtags to end of URL: as per Salesforce Marketing Cloud email channel.
Note that Web Adapters are supported at the channel.
A Validate channels job is created and executed on saving a new Responsys email channel, or on saving following a change to an existing Responsys email channel's Recipient email field. Full details are as per the Salesforce Marketing Cloud email channel documentation.