Configure destination for LiveRamp¶

Note

This topic contains information about configuring a destination that sends query results to LiveRamp using orchestrations. To configure a destination that sends audiences to LiveRamp using campaigns see this topic .

LiveRamp allows clients to combine customer data from various online and offline sources, centering around the use of web cookies that allow websites to remember visitors.

You can associate records in Amperity to an audience in LiveRamp by sending a combination of identifier data and query data. LiveRamp uses:

Identifier data to match records to other identifiers in the LiveRamp Identity Graph.
Segment data to group records into segments based on certain attributes for downstream targeting, measurement, and personalization.

LiveRamp requires an audience ID. This may be a client customer ID from another application, it may be the LiveRamp audience ID itself (from LiveRamp data that was imported to Amperity), or it may be the Amperity ID.

Amperity can be configured to send CSV files to LiveRamp.

Get details¶

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

Credential settings

Credentials for LiveRamp require a “username” and “passphrase”. Set the hostname to “sftp.liveramp.com”.

Required configuration settings

File format

Configure Amperity to send CSV files to LiveRamp.

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

Header

Enable to include header rows in output files.

Important

LiveRamp requires a header row to be present in CSV, TSV, and PSV files.

Remote folder

The remote folder to which Amperity will send data.

A “/” (forward slash) must be used as the first character for this value. For example: “/folder”. For example: “/folder”.

If the path to the remote folder contains 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 LiveRamp are optional.

LiveRamp file prefer`file limitations <https://docs.liveramp.com/connect/en/liveramp-data-restrictions.html>`__ |ext_link|ences

Sending data to LiveRamp should follow recommendations for uploading data .

Review LiveRamp file limitations .

LiveRamp supports the following file formats :

CSV
PSV
TSV

Important

Be sure to enable the Include header row in output files option for the Amperity destination.

LiveRamp prefers GPG encryption and GZip compression.

Configure credentials¶

Configure credentials for LiveRamp before adding a destination.

An individual with access to LiveRamp should use SnapPass to securely share “username”, “hostname”, and “passphrase” details with the individual who will configure Amperity.

To configure credentials for LiveRamp

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 LiveRamp.

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 are determined by the credential type. For the “liveramp” credential type, configure settings, and then click Save.

Hostname

Required

Required. The hostname for LiveRamp. For example: “sftp.liveramp.com”.

Passphrase

Required

The passphrase that is associated with the username.

Username

Required

Required. A username with access to LiveRamp. This username must be allowed to write data to the remote folder to which Amperity will send data.

Add destination¶

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

To add a destination for LiveRamp

	Open the Destinations page, and then click the Add destination button. To configure a destination for LiveRamp, do one of the following: Click the row in which LiveRamp is located. Destinations are listed alphabetically and you can scroll up and down the list. Search for LiveRamp. Start typing “live”. The list will filter to show only matching destinations. Select “LiveRamp”.
	Select the credential for LiveRamp from the Credential dropdown, and then click Continue. Tip Click the “Test connection” link on the “Configure destination” page to verify that Amperity can connect to LiveRamp.
	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 users with limited access to PII access to this destination. Restricted PII access is enabled when the Restrict PII access policy option that prevents users who are assigned to that option from viewing data that is marked as PII anywhere in Amperity and from sending that data to any downstream workflow.
	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 may be 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 LiveRamp. Filename template A filename template defines the naming pattern for files that are 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. Important LiveRamp requires a header row to be present in CSV, TSV, and PSV 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 will use 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 set to “None” and an escape character is not specified. Remote folder Required The remote folder to which Amperity will send data. A “/” (forward slash) must be used as the first character for this value. For example: “/folder”. For example: “/folder”. If the path to the remote folder contains 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. Use Zip64? Enable to apply Zip64 data compression to very large files.
	After this destination is configured: Use orchestrations to send query results Use orchestrations and campaigns to send audiences Use orchestrations and campaigns to send offline events