Customer.io

Customer.io is a powerful automation platform for email and marketing designed to help businesses engage with their customers in a personalized and targeted manner. It provides a user-friendly interface and a range of tools to create and send behavior-based, triggered, and segmented email campaigns.

Features

Feature nameSupported
Bulk uploadTrue
Operation modesTrueUpsert

Supported tables:

  • customer (upsert)
  • event (insert)
  • segment (insert)

πŸ”§ Setup Guide - Reverse ETL

Customer.io reverse ETL allows you to sync data on a schedule from your Weld App automatically into Klayvio.

Prerequisites

To connect your Customer.io account to Weld, you need:

  • A site ID
  • An API key
  • An app API key

You can find your API keys by navigating to Account Settings > API Credentials.

Step 1 - Destination

  1. In the Reverse ETL section, select + Add Reverse ETL Sync
  2. Select the Customer.io connector by clicking Use existing connection from the drop down menu or else click + Add new connection to authorize the connector.

Step 2 - Target Details

The customer.io connection does not have additional configuration - This will be skipped.

Step 3 - Map Data

  1. Select the source data model that you would like to sync to Customer.io. This can be a table or a view from your data warehouse.

  2. Select the destination object you would like to sync to. You can choose between customer, event, or segment. (Note: Some objects might require additional configuration that will be prompted during the setup process.)

  3. You will be presented with several options to configure your sync, which we will go through in the next steps.

SQL Model tips for Customer.io rETL

Customers:
Your SQL model should have one row per customer.
Requires a Primary key, either Email, ID, or CIO_ID

Event:
Your SQL model can have multiple rows per customer.
You must have a column containing the Event Name and Identifier.

Sync Mode

Choose how you want to sync data from your source model to the destination object. Depending on the destination object, you might have only one or multiple of the following options available:

  • Upsert: Updates existing records and inserts new ones.
  • Insert: Inserts new records only.

Choose Identifier

If you are syncing to the customer object, you will need to select the identifier property. This is the unique identifier that Customer.io uses to match records. Choose the column from your source model that corresponds to the identifier property in Customer.io.

Field Mapping

Map the fields from your source model to the fields in Customer.io. You can map the fields manually or use the auto-mapping feature to match fields based on their names. Ensure that the fields you map correspond to the properties in Customer.io.

Step 4 - Schedule sync

After you finished the steps above, click on Next to proceed to the scheduling step. Here you can choose how often you would like the sync to run:

  • Independent: The sync will run on its own schedule, independent of other syncs.
  • Orchestration: The sync will be part of an orchestration workflow, allowing you to run it in conjunction with other tasks.

Step 5 - Finalise and Run

After you have configured the sync, click on Start Sync to finalize the setup. The sync will perform the initial run immediately.

Was this page helpful?