# LiveRamp Activation Partners Integration 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](/int/liveramp-export-integration), 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](https://www.treasuredata.com/jp/contact_us) for more information. ## Prerequisites - Basic knowledge of Treasure Data, including the [TD Toolbelt](https://toolbelt.treasuredata.com/) - 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 1. Open the TD Console. 2. Navigate to Integrations Hub > Catalog. 3. Search and select LiveRamp or one of the LiveRamp Distribution Connector. ![](/assets/image-20200124-203224.7c10f94a9a82cf66041462505fa436dc787a13afdfa2999601c299c833c5fe16.a0fe23d6.png) 4. The New Authentication dialog appears. Provide the required credentials:  **API Key**: LiveRamp API Key ![](/assets/image-20200124-203337.b0a5a258b9792a03d2716e855a30da04196e9fd517237b1cc27bf60ac80b3f53.a0fe23d6.png) 5. Then select **Continue** and give your connection a name: ![](/assets/image-20200124-203432.3ba926597961b5ff6b99999712a62a3282a8f9f2a9164336054ebb28ec19e6e0.a0fe23d6.png) 6. Select **Done**. ### Specify Output in Your LiveRamp Distribution 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](https://liveramp.elevio.help/en/articles/92990) in LiveRamp 7. Select **Export** **Results** located at top of your query editor. ![](/assets/image-20200128-215417.5c09b9d850ec72daace4d79d70afad90df01e47916c97889f93cc1abf00d5036.a0fe23d6.png) 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](https://docs.treasuredata.com/articles/project-integrations/liveramp-export-integration#LiveRampExportIntegration-UsetheTDConsoletoCreateyourConnection). ![](/assets/image-20200128-214022.0451b6fa6b0dec3e969d3aa2a8b05c3ebcb49492dc5e5680246df3766d9f9392.a0fe23d6.png) 9. Specify the export details. Configure the connection by [specifying the parameters](http://docs.treasuredata.com/pages/viewpage.action?pageId=328994#LiveRampActivationPartnersIntegration(Beta)-ConfiguretheConnectionBySpecifyingtheParameters). ![](/assets/image-20200128-214226.2a31a4bc5b3182ebf6e15309fe1a684801cb571b728832f37dd7f104d61e7b5a.a0fe23d6.png) 10. Select **Done** ### Configure the Connection By Specifying the Parameters After you select your *LiveRamp* partner connection, the following dialog displays: ![](/assets/image-20200124-203553.f896f48c71d8e8cbd89958192a74495a62c1b91d7a2f9c79833ff83421cf24c6.a0fe23d6.png) 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](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** ```sql SELECT column_id AS segment_id FROM my_table; ``` Similar query by **segment_name** and **segment_value** ```sql 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 1. Navigate to **Data Workbench > Queries** 2. Create a new query or select an existing query. 3. Next to **Schedule**, select None. ![](/assets/image2021-1-15_17-28-51.f1b242f6ecc7666a0097fdf37edd1682786ec11ef80eff68c66f091bc405c371.0f87d8d4.png) 4. In the drop-down, select one of the following schedule options: ![](/assets/image2021-1-15_17-29-47.45289a1c99256f125f4d887e501e204ed61f02223fde0927af5f425a89ace0c0.0f87d8d4.png) | Drop-down Value | Description | | --- | --- | | Custom cron... | Review [Custom cron... details](#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 ![](/assets/image2021-1-15_17-30-23.0f94a8aa5f75ea03e3fec0c25b0640cd59ee48d1804a83701e5f2372deae466c.0f87d8d4.png) | **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. | 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. 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. 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. ![](/assets/ouput.b2c7f1d909c4f98ed10f5300df858a4b19f71a3b0834df952f5fb24018a5ea78.8ebdf569.png) - 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 Columns**to 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. 1. Set a **Schedule**. ![](/assets/snippet-output-connector-on-audience-studio-2024-08-28.a99525173709da1eb537f839019fa7876ffae95045154c8f2941b030022f792c.8ebdf569.png) - Select the values to define your schedule and optionally include email notifications. 1. Select **Create**. If you need to create an activation for a batch journey, review [Creating a Batch Journey Activation](/products/customer-data-platform/journey-orchestration/batch/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. ```yaml 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](http://docs.treasuredata.com/display/PD/About+Using+Workflows+to+Export+Data+with+TD+Toolbelt) 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](https://toolbelt.treasuredata.com/). ### For On-demand Jobs Add the LiveRamp result output destination by using the - r/--result option for the td query command: ```bash 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 Add the LiveRamp result output destination by using the - r/ --result option for the td sched:create command: ```bash td sched:create every_3_days "0 0 */3 * *"-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}' ```