Nextroll 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

This TD export integration lets you create and upload audience data to NextRoll

Prerequisites

• Basic Knowledge of Treasure Data™
• Have Adroll account

Limitations

• The default quota is 100 API requests per service per day. If you think you need your limit increased, send a message to NextRoll support.
• Don't support create duplicate audience name (case insensitive) in the same audience type

Requirements

If you use authentication method PAT then you need

• NextRoll developer account to create an Application
• api_key from your account.​

Obtain the API key and Personal Access Token

• Create NextRoll Developer account or login if you had one https://developers.nextroll.com/accounts/login

• From your account chose Apps then click New App

• Fill your App Name then click request and fill Callback URL (Ex: https://127.0.0.1)

• After create success. From My Apps choose it and copy API Key

• Login into Adroll account https://app.adroll.com/

• Choose setting from left sidebar

• From setting page choose Personal Access Token and click New then store the token

Create a new Connection

On TD Console, you must create and configure the data connection before running your query. As part of the data connection, you provide authentication to access the integration following the below steps

1. Open TD Console
2. Navigate to Integrations Hub > Catalog
3. Search for and select NextRoll

4. Select Create Authentication, chose Authentication Method then provide your information

5. Select Continue, enter a name for the Authentication, and select Done.

Configure a Query Result for Export

The TD Console supports multiple ways to export data. Please follow the below steps to export data from the Data Workbench

1. Navigate to Data Workbench > Queries
2. Select New Query, and define your query
3. Select Export Results to configure the data exporting

1. Select an existing authentication, or create a new one following the above section
2. Configure the exporting parameters as described in the Configuration Parameters below, and select Done

Define your Query

Your query should include the required columns for the CRM or Custom audience type, other columns will be ignored. Required columns don't accept a null or empty value (else the record is considered invalid and skipped). Other audience type don't require data to create audience. So please use query "SELECT 1;" or "SELECT ... FROM .. limit 1;". Otherwise the error will be returned.

Data requirement:

• MD5 hashing: email. If not, they are hashed automatically by the connector

Configuration Parameters

[
  { "name": "attribute_name1", "values": ["v1", "v2"], "comparator": "in" },
  { "name": "attribute_name2", "values": ["v3", "v4"], "comparator": "not_in" },
  { "name": "attribute_name3", "values": [], "comparator": "" }
]

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

(Optional) Export Integration Using the workflow

Within Treasure Workflow, you can specify the use of a data connector to export data.

Learn more at Using Workflows to Export Data with the TD Toolbelt.

For CRM audience

_export:
  td:
    database: nextroll

+nextroll_export_task:
  td>: export.sql
  database: ${td.database}
  result_connection: new_created_nextroll
  result_settings:
    type: nextroll
    audience_type: crm
    advertiser_id: xxx
    audience_name: xxxx
    skip_crm_invalid_records: true

For Cross-channel Lookalike audience

_export:
  td:
    database: nextroll

+nextroll_export_task:
  td>: export.sql
  database: ${td.database}
  result_connection: new_created_nextroll
  result_settings:
    type: nextroll
    audience_type: crosschannel_lal
    advertiser_id: xxx
    audience_name: xxxx
    country: US
    include_country: true
    source_segment_eid: 'xxxxx'
    size: 5
    allow_international_seeds: false
    crosschannel_lal_duration: 10

For Custom audience

_export:
  td:
    database: nextroll

+nextroll_export_task:
  td>: export.sql
  database: ${td.database}
  result_connection: new_created_nextroll
  result_settings:
    type: nextroll
    audience_type: custom
    advertiser_id: xxx
    audience_name: xxxx
    custom_duration: 120
    skip_custom_invalid_records: true

For Composite audience

_export:
  td:
    database: nextroll

+nextroll_export_task:
  td>: export.sql
  database: ${td.database}
  result_connection: new_created_nextroll
  result_settings:
    type: nextroll
    audience_type: composite
    advertiser_id: xxx
    audience_name: xxxx
    components: "xxx,xxx,xxx......"
    is_composite_conversion: true
    composite_conversion_value: '0.1'
    composite_duration: 10

For Impression audience

_export:
  td:
    database: nextroll

+nextroll_export_task:
  td>: export.sql
  database: ${td.database}
  result_connection: new_created_nextroll
  result_settings:
    type: nextroll
    audience_type: impression
    advertiser_id: xxx
    audience_name: xxxx
    impression_value: 4
    impression_duration: 120

For User Attributes audience

_export:
  td:
    database: nextroll

+nextroll_export_task:
  td>: export.sql
  database: ${td.database}
  result_connection: new_created_nextroll
  result_settings:
    type: nextroll
    audience_type: user_attributes
    advertiser_id: xxx
    audience_name: xxxx
    attributes: |
    [
      {
         "name" : "attr_1",
         "values" : ["test_value_1", "test_value_2"],
         "comparator" :  "in"
      },
      {
         "name" : "attr_2",
         "values" : ["test_value_3", "test_value_4"],
         "comparator" :  "not_in"
      },
      {
         "name" : "attr_3",
         "values" : [],
         "comparator" :  ""
      }
    ]

(Optional) Export Integration Using the CLI

You can also use CLI (Toolbelt) to export results to NextRoll.

You need to specify the information for export to your Account using the --result option of the td query command. For more information about the td query command, refer to this article.

The format of the option is JSON, and the general structure is as follows.

For CRM Audience

{
  "type": "nextroll",
  "td_authentication_id":"xxxx",
  "audience_type": "crm",
  "advertiser_id": "xxx",
  "audience_name": "xxxx",
  "skip_crm_invalid_records": true
}

For Cross-channel Lookalike audience

{
  "type": "nextroll",
  "td_authentication_id": "xxx",
  "audience_type": "crosschannel_lal",
  "advertiser_id": "xxx",
  "audience_name": "xxxx",
  "country": "xx",
  "include_country": true,
  "source_segment_eid": "xxxxx",
  "size": 5,
  "allow_international_seeds": false,
  "crosschannel_lal_duration": 10
}

For Custom audience

{
  "type": "nextroll",
  "td_authentication_id": "xxx",
  "audience_type": "custom",
  "advertiser_id": "xxx",
  "audience_name": "xxxx",
  "custom_duration": 120,
  "skip_custom_invalid_records": true
}

For Composite audience

{
  "type": "nextroll",
  "td_authentication_id": "xxxx",
  "audience_type": "composite",
  "advertiser_id": "xxx",
  "audience_name": "xxxx",
  "components": "xxx,xxx,xxx......",
  "is_composite_conversion": true,
  "composite_conversion_value": "0.1",
  "composite_duration": 10
}

For Impression audience

{
  "type": "nextroll",
  "td_authentication_id": "xxxx",
  "audience_type": "impression",
  "advertiser_id": "xxx",
  "audience_name": "xxxx",
  "impression_value": 4,
  "impression_duration": 120
}

For User Attributes audience

{
  "type": "nextroll",
  "td_authentication_id": "xxx",
  "audience_type": "user_attributes",
  "advertiser_id": "xxx",
  "audience_name": "xxxx",
  "attributes": [
    {
      "name": "attr_1",
      "values": ["test_value_1", "test_value_2"],
      "comparator": "in"
    },
    {
      "name": "attr_2",
      "values": ["test_value_3", "test_value_4"],
      "comparator": "not_in"
    },
    {
      "name": "attr_3",
      "values": [],
      "comparator": ""
    }
  ]
}

Parameters

[
  { "name": "attribute_name1", "values": ["v1", "v2"], "comparator": "in" },
  { "name": "attribute_name2", "values": ["v3", "v4"], "comparator": "not_in" },
  { "name": "attribute_name3", "values": [], "comparator": "" }
]

Example for Usage

OAuth authentication

td query --result \
'{"type":"nextroll","td_authentication_id":"xxx","audience_type":"crm","advertiser_id":"xxx","audience_name":"xxx","skip_crm_invalid_records":true}' \
-d sample_datasets "select ........ from ........" -T presto

Others

• You can use Scheduled Job  with Result Export to periodically upload data to a target destination