Customer.io Export Integration

The Customer.io Export Connector lets you push Treasure Data CDP query results into Customer.io to keep profiles and segments in sync after each workflow run. Use it when you need to activate CDP-unified customer data — such as high-value segments or behavioral attributes — in your Customer.io campaigns without a manual export step. The connector supports profile upsert and remove operations via the Tracking V2 API, and can add or remove customers from segments with automatic segment creation.

• Profile Operations - Create, update, or remove customer profiles via Tracking V2 API.
• Segment Management - Add or remove customers from segments with automatic segment creation.
• Multiple Identifiers - Support for id, cio_id, and email as customer identifiers.
• Automatic Region Resolution - Dynamic endpoint discovery via Customer.io's Track Region API.
• Batch Processing - Efficient bulk operations with configurable error handling.

• Basic knowledge of Treasure AI
• Customer.io account with API access
• Valid Customer.io App API Key, Site ID, and API Key
• Authorized Treasure AI account access

• At least one identifier (cio_id, id, or email) must be present in each record
• Using email as identifier requires enabling email identification in Customer.io workspace settings
• The cio_relationships field is automatically excluded from attribute mapping
• Segments are automatically created if they don't exist when using segment operations
• Customer.io implements rate limiting; the connector handles retries with exponential backoff

If your security policy requires IP whitelisting, you must add Treasure Data's IP addresses to your allowlist to ensure a successful connection.

Please find the complete list of static IP addresses, organized by region, at the following document

In Treasure AI, you must create and configure the data connection, to be used during export, prior to running your query. As part of the data connection, you provide authentication to access Customer.io.

1. Open Treasure Console.

2. Navigate to Integrations Hub > Catalog.

3. Search for and select Customer.io. Select Create Authentication.

4. The following dialog opens. Edit the parameters. Select Continue.

5. Enter a name for your connection.
6. Choose to share the authentication with others or not.
7. Select Done.

In this step, you create or reuse a query. In the query, you configure the data connection.

1. Open the Treasure Console.
2. Navigate to Data Workbench > Queries.
3. Select the query that you plan to use to export data.
4. Select Export Results located at top of your query editor. The Choose Integration dialog opens.

You have two options when selecting a connection to use to export the results, using an existing connection or creating a new one.

1. Type the connection name in the search box to filter.
2. Select your connection.
3. The Export Results dialog opens.
4. Set the following parameters and select Done.

1. Select New Integration and select Customer.io from Type dropdown.
2. The Create Integration dialog opens.
3. Select the Catalog link to go to the Catalog page.
4. Complete the steps described previously in "Create a new connection".
5. Enter the required credentials for your new Customer.io connection.

The Customer.io export connector understands and interprets the following columns and data types. You must modify alias column names to match with the following specified columns.

The following table describes the columns available for Customer.io export integration:

Identifier Logic: The connector validates the presence of the identifier field specified by the id_type configuration parameter. Records must contain the required identifier field to be processed successfully.

-- Profile upsert with 'id' identifier
SELECT
  customer_id AS id,
  email_address AS email,
  first_name,
  last_name,
  signup_date,
  total_orders,
  lifetime_value
FROM customer_profiles
WHERE TD_TIME_RANGE(time, TD_DATE_TRUNC('day', TD_SCHEDULER_TIME() - 86400, 'UTC'), NULL)

-- Add customers to segment
SELECT
  customer_id AS id,
  email_address AS email,
  first_name,
  last_name
FROM high_value_segment
WHERE TD_TIME_RANGE(time, TD_DATE_TRUNC('day', TD_SCHEDULER_TIME() - 86400, 'UTC'), NULL)

-- Using Customer.io internal ID (cio_id)
SELECT
  cio_customer_id AS cio_id,
  first_name,
  last_name,
  plan_type
FROM customer_profiles

-- Using email as identifier
SELECT
  email,
  first_name,
  last_name,
  subscription_status
FROM customer_profiles

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.

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.

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