Send data to LiveRamp

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.

This topic describes the steps that are required to send CSV, TSV, or PSV files to LiveRamp from Amperity:

1. Get details

2. Add destination

3. Add data template

Get details

LiveRamp requires the following configuration details:

	The username and passphrase.
	The remote folder to which Amperity will send data. Important A “/” (forward slash) must be used as the first character for this value. For example: /uploads/tenant-name.
	The LiveRamp public key to use for GPG encryption.
	LiveRamp requires a header row to be present in CSV, TSV, and PSV files.

File preferences

Sending data to LiveRamp should follow recommendations for uploading data.

File limitations

Review LiveRamp file limitations.

File formats

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.

GPG encryption

LiveRamp prefers GPG encryption and GZip compression.

Add destination

Configure Amperity to send CSV, TSV, or PSV files directly to LiveRamp.

To add a destination

	Open the Destinations tab to configure a destination for LiveRamp. Click the Add Destination button to open the Destination dialog box. Enter a name for the destination and provide a description. For example: “LiveRamp” and “This sends CSV, TSV, or PSV files to LiveRamp”. From the Plugin drop-down, start typing “liv” to filter the list, and then select LiveRamp.
	Credentials allow Amperity to connect to LiveRamp. The credential type is set automatically to liveramp. You may use an existing credential or you may add a new one. Select an existing credential from the Credential drop-down. – or – Select Create a new credential from the Credential drop-down. This opens the Credential dialog box. Enter the name for the credential, and then add a description. Select files.liveramp.com or sftp.liveramp.com from the HOSTNAME drop-down list. Enter the username and passphrase. When finished, click Save.
	Each destination has settings that define how Amperity will deliver data to LiveRamp. These settings are listed under the Settings section of the Destination dialog box. Complete the following SFTP Settings: The path to the Remote folder. Tip 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”. The File format. Select the file format – CSV, TSV, or PSV – from the drop-down list. Optional. The Escape character that is required by LiveRamp. Note If an escape character is not specified and quote mode is set to “None” this may result in unescaped, unquoted files. When an escape character is not specified, you should select a non-“None” option from the Quote Mode setting. Optional. The Compression format. “GZip”. Optional. The PGP public key that is used to encrypt files that are sent to LiveRamp. Optional. The Quote mode that should be used within the file. From the drop-down, select one of “all fields”, “all non-NULL fields”, “fields with special characters only”, “all non-numeric fields” or “None”. Note If the quote mode is set to “None” and the Escape Character setting is empty this may result in unescaped, unquoted files. When quote mode is not set to “None”, you should specify an escape character. Optional. Select Include success file upon completion to add a .DONE file that indicates when an orchestration has finished sending data. Tip If a downstream sensor is listening for files sent from Amperity, configure that sensor to listen for the presence of the .DONE file. Optional. Select Include header row in output files if headers should be included in the output. Optional. Select Row number to include a row number column in the output file. Applies to CSV, TSV, PSV, and custom delimiter file types. When enabled, you may specify the name of the row number column in the output file. Optional. Select Exclude Parquet extension from the directory name for managing how Apache Parquet files are added to directories.
	Business users are assigned to the Amp360 User and/or AmpIQ User policies. (Amp360 User allows access to queries and orchestrations and AmpIQ User allows access to segments and campaigns.) A business user cannot select a destination that is not visible to them. Business users – including users assigned to the DataGrid Operator policy – may have restricted access to PII. What is restricted access to PII? 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. You can make this destination visible to orchestrations and allow users with restricted access to PII to use this destination by enabling one (or both) of the following options: Note To allow business users to use this destination with campaigns, you must enable the Available to campaigns option within the data template. This allows users to send campaign results from Amperity to LiveRamp. The other two settings may be configured within the data template instead of the destination.
	Review all settings, and then click Save. Important You must configure a data template for this destination before you can send data to LiveRamp.

Add data template

A data template defines how columns in Amperity data structures are sent to downstream workflows. A data template is part of the configuration for sending query and segment results from Amperity to an external location.

About paid media campaigns

Amperity provides the right set of data to support your brand’s paid media advertising with LiveRamp.

1. Merged Customers vs. Unified Paid Media

   The Merged Customers table contains each of your customers’ best profiles.

   The Unified Paid Media table contains all your customer’s known profile data.

   Your brand will require additional data templates to use the Unified Paid Media table alongside the Merged Customers table to support paid media campaigns.

2. Enable dedicated data templates for each table.

   Use a consistent naming pattern to label data templates that use data from the Merged Customers table. For example: “Best profile”.

   Use a consistent naming pattern to label data templates that use data from the Unified Paid Media table. For example: “Full profile”.

3. After data templates are configured for both tables, use the default attributes component on the Campaigns page to configure which attributes will be associated with the destination, including the table from which those attributes will be pulled.

   The selected table will affect your brand’s downstream match rates and overall customer matches within your paid media campaigns. The decision behind which table to use depends on your brand’s downstream use case and the type and amount of customer profile data your brand wants to use to match customers.

   You brand should expect to see higher match rates when sending audiences from the Merged Customers table, but a higher number of matched customer profiles when sending audiences from the Unified Paid Media table. Use A/B testing to compare the results from each table, after which your brand can use the audience that works best for your campaigns.

To add a data template

	From the Destinations tab, open the menu for a destination that is configured for LiveRamp, and then select Add data template. This opens the Add Data Template dialog box. Enter the name of the data template and a description. For example: “LiveRamp” and “Send CSV, TSV, or PSV files to LiveRamp.”.
	Verify business user access to queries and orchestrations and access to segments and campaigns. A business user may also have restricted access to PII, which prevents them from viewing and sending customer profile data. If business user access was not configured as part of the destination, you may configure access from the data template. Important To allow business users to use this destination with campaigns, you must enable the Available to campaigns option. This allows users to send campaign results from Amperity to LiveRamp. If you enable this option, the data extension settings require using campaign name and group name template variables to associate the name of the data extension to your campaign.
	Verify all configuration settings. Note When the settings required by the SFTP site were are not configured as part of the destination, you must configure them as part of the data template before making this destination available to campaigns.
	Review all settings, and then click Save. After you have saved the data template, and depending on how you configured it, business users can send query results and/or send campaigns to LiveRamp.