Configure campaigns for Oracle Responsys¶

Oracle Responsys is an email marketing product that helps improve conversions, strengthen customer relationships, and dramatically lessen messaging fragmentation.

Configure Amperity to send CSV files to Oracle Responsys.

Get details¶

Review the following details before configuring credentials for Oracle Responsys and before configuring Amperity to send CSV files to Oracle Responsys.

Credential settings

Credentials for Oracle Responsys require a “username” and “passphrase”. Set the host name to “files.responsys.net” or “files.dc2.responsys.net”.

Required configuration settings

File format

Configure Amperity to send CSV files to Oracle Responsys.

Some file formats allow a custom delimiter. Choose the “Custom delimiter” file format, and then add a single character to represent the custom delimiter.

Remote folder

The remote folder to which Amperity sends data.

Use a forward slash–“/”–as the first character for this value. For example: “/folder”.

If the path to the remote folder has a space, use a backslash (\) character to escape that space. For example, a folder named “From ACME” should be entered as “From\ ACME”.

Note

All other Amperity file format settings for Oracle Responsys are optional.

Configure credentials¶

Configure credentials for Oracle Responsys before adding a destination.

An individual with access to Oracle Responsys should use SnapPass to securely share “username”, “hostname”, and “passphrase” details with the individual who configures Amperity.

To configure credentials for Oracle Responsys

From the Settings page, select the Credentials tab, and then click the Add credential button.

In the Credentials settings dialog box, do the following:

From the Plugin dropdown, select Oracle Responsys.

Assign the credential a name and description that ensures other users of Amperity can recognize when to use this destination.

The settings that are available for a credential vary by credential type. For the “oracle-responsys” credential type, configure settings, and then click Save.

Hostname

Required

Required. The host name for Oracle Responsys. For example: “files.responsys.net” or “files.dc2.responsys.net”.

Passphrase

Required

The passphrase associated with the username.

Username

Required

Required. A username with access to Oracle Responsys. This username must have permission to write data to the remote folder to which Amperity sends data.

Add destination¶

Use a sandbox to configure a destination for Oracle Responsys. Before promoting your changes, send a test audience, and then verify the results in Oracle Responsys. After verifying the end-to-end workflow, push the destination from the sandbox to production.

To add a destination for Oracle Responsys

	Open the Destinations page, select the New destinations button, and then select Campaign. To configure a campaign for Oracle Responsys, do one of the following: Click the row in which Oracle Responsys is located. Destinations list alphabetically and you can scroll up and down the list. Search for Oracle Responsys. Start typing “oracle”. The list filters to show only matching destinations. Select “Oracle Responsys”.
	Select the credential for Oracle Responsys from the Credential dropdown, and then click Continue. Tip If there are any issues with destination connectivity, an error message will display in the destination setup dialog. If the destination saves successfully, the connection is ready for use.
	In the “Destination settings” dialog box, assign the destination a name and description that ensures other users of Amperity can recognize when to use this destination. Configure business user access By default a destination is available to all users who have permission to view personally identifiable information (PII). Enable the Admin only checkbox to restrict access to only users assigned to the Datagrid Operator and Datagrid Administrator policies. Enable the PII setting checkbox to allow limited access to PII for this destination. Use the Restrict PII access policy option to prevent users from viewing data marked as PII anywhere in Amperity and from sending data to downstream workflows.
	Configure the following settings, and then click “Save”. Compression The compression format to apply to the file. May be one of “GZIP”, “None”, “TAR”, “TGZ”, or “ZIP”. Escape character The escape character to use in the file output. Applies to CSV, TSV, PSV, and custom delimiter file types. When an escape character is not specified and the quote mode is “None” files are sent with unescaped and unquoted data. When an escape character is not specified, you should select a non-“None” option as the quote mode. File format Required Configure Amperity to send CSV files to Oracle Responsys. Filename template A filename template defines the naming pattern for files that sent from Amperity. Specify the name of the file, and then use Jinja-style string formatting to append a date or timestamp to the filename. Header Enable to include header rows in output files. Line ending The line ending to use in file output. May be one of “LF” or “CRLF”. PGP public key The PGP public key that Amperity uses to encrypt files. Quote mode The quote mode to use within the file. May be one of “all fields”, “all non-NULL fields”, “fields with special characters only”, “all non-numeric fields” or “None”. Unescaped, unquoted files may occur when quote mode is “None” and an escape character is not specified. Remote folder Required The remote folder to which Amperity sends data. Use a forward slash–“/”–as the first character for this value. For example: “/folder”. If the path to the remote folder has a space, use a backslash (\) character to escape that space. For example, a folder named “From ACME” should be entered as “From\ ACME”. Success file Enable to send a “.DONE” file when Amperity has finished sending data. If a downstream sensor is listening for files sent from Amperity, configure that sensor to listen for the presence of the “.DONE” file. Split outputs Split delimiter-separated output–CSV, PSV, TSV, or files with custom delimiters–into multiple files to ensure downstream file limits are not exceeded. Choose “Rows” and set “Rows limit” to a value between “50000” and “10000000”. This is the maximum number of rows for split output files. Choose “Megabytes” and set “Megabytes limit” to a value between “1 MB” and “2000 MB”. This is the maximum file size. Additional configuration is required for filename templates. Set the value of “Split filename template” to “{{file_number}}.csv” to apply a unique seven digit left-padded integer to the filename. For example: “0000001.csv”, “0000002.csv”, and “0000003.csv”. Use the “Split file directory template” to name the directory into which split files are added. For example: if the value of “Split file directory template” is {{now\|format:’YYYY’}}.tgz and the value of “Split filename template” is “{{file_number}}.csv” Amperity will output a gzipped tarball named “2025.tgz” with subfiles named “0000001.csv”, “0000002.csv”, and “0000003.csv”. Use Zip64? Enable to apply Zip64 data compression to large files. Campaign file settings Under Campaign settings select one of the following: Send audience list as separate files This option sends a standalone file for each treatment group sending an audience to Oracle Responsys. Send audience lists as a single file This option consolidates all treatment groups into a single file before sending the audience to Oracle Responsys.
	After configuring this destination users may send campaigns to Oracle Responsys.