LiveRamp Export Integration

Copy

• Copy for LLM

  Copy page as Markdown for LLMs
• View as Markdown

  Open this page as Markdown
• Open in ChatGPT

  Get insights from ChatGPT
• Open in Claude

  Get insights from Claude
• Connect to Cursor

  Install MCP server on Cursor
• Connect to VS Code

  Install MCP server on VS Code

Treasure Data can publish user segments into LiveRamp, and syndicate user segments into various DSP, DMP, Data Providers.

LiveRamp is an identity resolution platform with services include data on-boarding, and the transfer of offline data online for marketing purposes. LiveRamp allows you to anonymize Personally Identifiable Information (PII) and unify customer data from various sources.

Enhance the run of your data-driven marketing campaigns by using data that is gathered and housed in Treasure Data with LiveRamp to both anonymize your user segment data and increase the reach of your advertising campaigns, with more accurate targeting.

To participate in the release, contact us for more information.

Anonymize and Enhance Your Treasure Data Segments with LiveRamp

LiveRamp offers ID unification and activation to multiple marketing and advertising applications. You can use Treasure Data with LiveRamp to do the following before exporting out to LiveRamp activation partners:

• Anonymize private identity information (PII) data using LiveRamp IdentityLink
• Enhance segment profiles with additional 3rd party data further refining customer profile segments

Treasure Data also offers direct activation to six LiveRamp partners.

Treasure Data to LiveRamp

To upload an ID list with PII info in a segment to LiveRamp, you can upload the PII data to Treasure Data and LiveRamp. Then, you can use Treasure Data to create a target segment on Treasure Data. When this segment is exported to LiveRamp, it uses the UserID to update the profile with the segment behaviors and attributes and anonymizes it using IdentityLink.

You can send job results and user segment data directly from Treasure Data to LiveRamp SFTP server. Export data in csv format with gz extension.

Cookie Syncing

Cookie syncing between your website, Treasure Data and LiveRamp is available through LiveRamp’s support of a pixel tag. Customers can add a snippet to send to LiveRamp through their pixel tag. It should be formatted as td_xxx_id (using client_id or ssc_id or global_id). Additionally, customers need to send a cookie to TD via the JavaScript SDK. You can make a segment based on td cookies and then export the list to LiveRamp for cookie syncing.

Prerequisites

• Basic knowledge of Treasure Data, including the toolbelt.
• A LiveRamp SFTP credential.

Use the TD Console to Create your Connection

You can use the Treasure Data Console to configure your connection.

Create a Connection

1. Navigate to Integrations Hub > Catalog. Search and select LiveRamp.

   

2. The following dialog opens.

   

3. Edit the required credentials:  Host: The host information of the LiveRamp SFTP Server (default files.liveramp.com) Port: Select port 22 or 8442 User: Username to connect to LiveRamp SFTP Server. Password: Password to connect to LiveRamp SFTP Server if you don't use SSH key. SFTP with SSH Key: Checkbox to use SSH key to connect to SFTP Server. SSH Key: The content of the private key. Passphrase: The passphrase of the SSH key. Note: The content of the private key must be in RSA format. For example:

   Content of private key file before formatting:```-----BEGIN RSA PRIVATE KEY-----line1line2line3-----END RSA PRIVATE KEY-----4. Select **Continue** and provide a name for your connection.
   
   ![](/images/int/liveramp-export-integration/image-20200128-000632.png)

4. Select Done.

Specify Output in Your LiveRamp Connector

1. Open TD Console.

2. Navigate to the Data Workbench > Queries.

3. Select New Query.

4. Select the database for which you would like to export data.

5. Type your query into the query editor.

6. You need to define the column mapping in the query the same as recommended headers in LiveRamp

7. Select Export Results located at top of your query editor.

   

8. The Choose Integration dialog opens.  Select an existing LiveRamp connection. If you do not have an Integration already set up, see "Creating a New Connection During Data Export".

   

9. Specify the export details. Configure the connection by specifying the parameters.

   

10. Select Done

Configure the Connection by Specifying the Parameters

Type the connection name in the search box to filter and select your connection.

After you select your LiveRamp connection, the Configuration or Export Results dialog pane appears:

Specify parameters. The parameters are as follows:

• File Name: Name the file without extension.
• Add timestamp to the file name: if checked, the date of job runs (in UTC) will be used to append to the end of the filename.
• **Audience Name:**the folder where the file is uploaded to. If leave it empty, the file is uploaded to the “/uploads” folder (replacing any spaces with underscores). The audience convention is  [CustomerName]_[ListName]_[Additional Detail]. If an audience named "TreasureData_DistAPITesting_Test", the file is uploaded to "/uploads/treasuredata_distapitesting_test".
• Encrypt File Before Upload: If checked, the file will be encrypted before uploading to the server.
• Retry Limit: When an error occurs due to a LiveRamp SFTP server error or network error, the number of retries attempted before aborting the upload (default 7)
• Connection timeout in seconds: the amount of time allotted for connecting to the Liveramp SFTP Server (default: 600)

(Optional) Schedule Query Export Jobs

You can use Scheduled Jobs with Result Export to periodically write the output result to a target destination that you specify.

Treasure Data's scheduler feature supports periodic query execution to achieve high availability.

When two specifications provide conflicting schedule specifications, the specification requesting to execute more often is followed while the other schedule specification is ignored.

For example, if the cron schedule is '0 0 1 * 1', then the 'day of month' specification and 'day of week' are discordant because the former specification requires it to run every first day of each month at midnight (00:00), while the latter specification requires it to run every Monday at midnight (00:00). The latter specification is followed.

Scheduling your Job Using TD Console

1. Navigate to Data Workbench > Queries

2. Create a new query or select an existing query.

3. Next to Schedule, select None.

4. In the drop-down, select one of the following schedule options:

   Drop-down Value	Description
   Custom cron...	Review Custom cron... details.
   @daily (midnight)	Run once a day at midnight (00:00 am) in the specified time zone.
   @hourly (:00)	Run every hour at 00 minutes.
   None	No schedule.

Custom cron... Details

 *    *    *    *    *
 -    -    -    -    -
 |    |    |    |    |
 |    |    |    |    +----- day of week (0 - 6) (Sunday=0)
 |    |    |    +---------- month (1 - 12)
 |    |    +--------------- day of month (1 - 31)
 |    +-------------------- hour (0 - 23)
 +------------------------- min (0 - 59)

The following named entries can be used:

• Day of Week: sun, mon, tue, wed, thu, fri, sat.
• Month: jan, feb, mar, apr, may, jun, jul, aug, sep, oct, nov, dec.

A single space is required between each field. The values for each field can be composed of:

1. (Optional) You can delay the start time of a query by enabling the Delay execution.

Execute the Query

Save the query with a name and run, or just run the query. Upon successful completion of the query, the query result is automatically exported to the specified destination.

(Optional) You can delay the start time of a query by enabling the Delay execution.

Activate a Segment in Audience Studio

You can also send segment data to the target platform by creating an activation in the Audience Studio.

1. Navigate to Audience Studio.
2. Select a parent segment.
3. Open the target segment, right-mouse click, and then select Create Activation.
4. In the Details panel, enter an Activation name and configure the activation according to the previous section on Configuration Parameters.
5. Customize the activation output in the Output Mapping panel.

• Attribute Columns
  • Select Export All Columns to export all columns without making any changes.
  • Select + Add Columns to add specific columns for the export. The Output Column Name pre-populates with the same Source column name. You can update the Output Column Name. Continue to select + Add Columnsto add new columns for your activation output.
• String Builder
  • + Add string to create strings for export. Select from the following values:
    • String: Choose any value; use text to create a custom value.
    • Timestamp: The date and time of the export.
    • Segment Id: The segment ID number.
    • Segment Name: The segment name.
    • Audience Id: The parent segment number.

6. Set a Schedule.

• Select the values to define your schedule and optionally include email notifications.

7. Select Create.

Optionally Configure Export Results in Workflow

Within Treasure Workflow, you can specify the use of this data connector to output data.

timezone: UTC
_export:
   td:
      database: sample_datasets
   +td-result-into-liveramp:
      td>: queries/sample.sql
      result_connection: your_connection_name
      result_settings:
         file_name: file_name
         include_date: true
         audience_name: audience_name
         encrypt_file_before_upload: false
         retry_limit: 3
         timeout: 600

Selecthere for more information on using data connectors in the workflow to export data.

Confirm Segment Was Created in LiveRamp

It is important to create a workflow element that confirms that the segment was created in LiveRamp before activating out to a partner.

Use the CLI to create your connection

Install Treasure Data Toolbelt

Install the Treasure Data Toolbelt.

• User Name and Password Authentication

{
   "type": "liveramp",
   "host":"IP or host of SFTP server",
   "port": "The open port",
   "username":"login user",
   "password":"<password of user>",
   "connect_with_ssh_key": "false",
   "file_name": "the name of file",
   "audience_name": "the audience name",
   "encrypt_file_before_upload" : "true or false"
}

• Authentication using SSH Key (Public/Private Key Pair)

{
  "type": "liveramp",
  "host": "IP or host of SFTP server",
  "port": "The open port",
  "username": "login user",
  "connect_with_ssh_key": "true",
  "ssh_key": "the content of private key file",
  "passphrase": "the passphrase of the private key",
  "file_name": "the name of file",
  "audience_name": "the audience name",
  "encrypt_file_before_upload": "true or false"
}

For On-demand Jobs

Add the LiveRamp result output destination by using the

• For on-demand jobs, just add the --result option to the td query command

$ td query \
    -d mydb \
    -w 'SELECT id, name FROM source_table' \
    --type presto \
    --result '{"type":"liveramp","host":"files.liveramp.com","port":22,"username":"owner","password":"********","connect_with_ssh_key":false,"file_name":"customer_list","include_date":true,"audience_name":"audience_name","retry_limit":3,"timeout":600}'

$ td query \
    -d mydb \
    -w 'SELECT id, name FROM source_table' \
    --type presto \
    --result '{"type":"liveramp","host":"files.liveramp.com","port":22,"username":"owner","connect_with_ssh_key":true,"ssh_key":"content of ssh key","passphrase":"passphrase","file_name":"customer_list","include_date":true,"audience_name":"audience_name","retry_limit":3,"timeout":600}'

For Scheduled Jobs

Add the LiveRamp result output destination by using the

• r/--result option for the td sched:create command:

$ td sched:create every_3_days "0 0 */3 * *" \
    -d mydb \
    -w 'SELECT id, name FROM source_table' \
    --type presto \
    -r '{"type":"liveramp","host":"files.liveramp.com","port":22,"username":"owner","password":"********","file_name":"customer_list","include_date":true,"audience_name":"audience_name","retry_limit":3,"timeout":600}'

References

• API Overview: Liveramp API Document
• Liveramp Connection:  Liveramp Connection