LiveRamp Activation Partners Integration
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 allows you to export data for ID resolution, anonymization, and data enhancement to LiveRamp. Treasure Data can now trigger LiveRamp activations with six activation partners.

After the segment has been created in Treasure Data and exported to LiveRamp, you have the option of exporting to six LiveRamp activation partners directly from Treasure Data. You can create a workflow in Treasure Data that will sync data in LiveRamp to other services in the TD Workflow UI. The connector requires a segment id you want to activate on LiveRamp side. These partner platforms include:

Beeswax
Twitter
Snapchat
Google Display & Video 360 (DV360)
Facebook (US) Direct On-boarding
Facebook (US) Managed On-boarding

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

Prerequisites

Basic knowledge of Treasure Data, including the TD Toolbelt
A LiveRamp API Key
Destination Account created in LiveRamp Connect UI

Using the TD Console to Create Your Connection

You can use Treasure Data Console to configure your connection.

Create a New Connection

Open the TD Console.
Navigate to Integrations Hub > Catalog.
Search and select LiveRamp or one of the LiveRamp Distribution Connector.
The New Authentication dialog appears. Provide the required credentials: API Key: LiveRamp API Key
Then select Continue and give your connection a name:
Select Done.

Specify Output in Your LiveRamp Distribution Connector

Open TD Console.
Navigate to the Data Workbench > Queries.
Select New Query.
Select the database for which you would like to export data.
Type your query into the query editor.
You need to define the column mapping in the query the same as recommended headers in LiveRamp
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

After you select your LiveRamp partner connection, the following dialog displays:

Enter the input parameters as follows:

Destination Account ID: Account ID of destination LiveRamp account. Can be found in LiveRamp Connect URL. Account ID can not be blank. Example with the URL https://connect.liveramp.com/distribution/accounts/1021066/segments, the destination account ID is 1021066.
Retry limit: When an error occurs due to a LiveRamp 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 API (default: 600)

Column Name for the Query

The LiveRamp data connector understands and interprets only the following columns and data types. You must modify alias column names to match with the following specified columns:

Column name	Type	Required	Description
segment_id	long	optional	if both segment_id and segment_name are specified, the segment_id will be used.
segment_name	string	optional
segment_value	string	optional

You must include either segment_id or segment_name/segment_value column in the Query otherwise your jobs will fail.

Example Queries to Populate LiveRamp

From Treasure Data query editor, run the following query with export results into a connection for LiveRamp Distribution

The following example query to distribute all segments to destination LiveRamp account by segment_id

SELECT
 column_id AS segment_id
FROM
 my_table;

Similar query by segment_name and segment_value

SELECT
 column_name AS segment_name,
 column_value AS segment_value
FROM
 my_table

(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

Navigate to Data Workbench > Queries
Create a new query or select an existing query.
Next to Schedule, select None.

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

Cron Value	Description
`0 * * * *`	Run once an hour.
`0 0 * * *`	Run once a day at midnight.
`0 0 1 * *`	Run once a month at midnight on the morning of the first day of the month.
""	Create a job that has no scheduled run time.

 *    *    *    *    *
 -    -    -    -    -
 |    |    |    |    |
 |    |    |    |    +----- 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:

Field Value	Example	Example Description
A single value, within the limits displayed above for each field.
A wildcard `'*'` to indicate no restriction based on the field.	`'0 0 1 * *'`	Configures the schedule to run at midnight (00:00) on the first day of each month.
A range `'2-5'`, indicating the range of accepted values for the field.	`'0 0 1-10 * *'`	Configures the schedule to run at midnight (00:00) on the first 10 days of each month.
A list of comma-separated values `'2,3,4,5'`, indicating the list of accepted values for the field.	`0 0 1,11,21 * *'`	Configures the schedule to run at midnight (00:00) every 1st, 11th, and 21st day of each month.
A periodicity indicator `'*/5'` to express how often based on the field's valid range of values a schedule is allowed to run.	`'30 /2 1 *'`	Configures the schedule to run on the 1st of every month, every 2 hours starting at 00:30. `'0 0 /5 *'` configures the schedule to run at midnight (00:00) every 5 days starting on the 5th of each month.
A comma-separated list of any of the above except the `''` wildcard is also supported `'2,/5,8-10'`.	`'0 0 5,/10,25 *'`	Configures the schedule to run at midnight (00:00) every 5th, 10th, 20th, and 25th day of each month.

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

Scheduled jobs that continuously fail due to configuration errors may be disabled on the system side after several notifications.

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

Navigate to Audience Studio.
Select a parent segment.
Open the target segment, right-mouse click, and then select Create Activation.
In the Details panel, enter an Activation name and configure the activation according to the previous section on Configuration Parameters.
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.

Set a Schedule.

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

Select Create.

If you need to create an activation for a batch journey, review Creating a Batch Journey Activation.

Optional: 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-distribution:
  td>: queries/sample.sql
  result_connection: your_connection_name
  result_settings:
    account_id: account_id
    retry_limit: 3
    timeout: 600

Read more information about using data connectors in the workflow to export data.

Use the CLI to Create Your Connection

Install ‘td’ command

Install the Treasure Data Toolbelt.

For On-demand Jobs

Add the LiveRamp result output destination by using the

r/--result option for the td query command:

td query -d mydb -w 'SELECT id as segment_id FROM source_table' --type presto -r '{"type":"liveramp_to_twitter_distribution", "api_key":"dummy_api_key", "account_id":123, "retry_limit":3, "timeout":600}'

The supported types:

liveramp_to_facebook_distribution
liveramp_to_twitter_distribution
liveramp_to_beeswax_distribution
liveramp_to_facebook_direct_onboarding_distribution
liveramp_to_google_display_video_distribution
liveramp_to_snapchat_distribution

For Scheduled Jobs