Destinations
Customer.io
Customer.io is a platform that uses application data and rules to message users through email, web, and mobile push.
Introduction
Valmi.io presents the Customer.io connector, a powerful solution that enables efficient management of people objects while harnessing their invaluable data for targeted campaigns and personalized messaging. By seamlessly integrating this connector, you can elevate your customer engagement strategies to new heights, delivering exceptional results and fostering meaningful connections.Customer.io Configuration
To use customer.io API through Valmi.io, you must create a Site ID, Tracking API Key, and App API Key. Follow the below steps to generate these keys.- Navigate to “Account Settings of Customer.io. In the API Credentials, select Tracking API Key and create Tracking API Key and Site ID. Go to App API Key to create an app API key.
Creating a Customer.io Connection on valmi.io
Go to destinations on Valmi.io and create a new destination. Select Customer.io as the destination.
On the next page,
- Enter connection name, connection name can be anything that helps you to identify the connection.
- Enter the Site ID, Tracking API Key and App API Key details from Customer.io.
Setting up a Sync
1. Supported Destination Modes
Customer.io supports the following destination modes. Please refer to the Destination Sync Modes for more information on the different destination modes.| Customer.io Object | Upsert | Supported Identifiers |
|---|---|---|
| Person | ✅ | Email/ID |
2. Mapping Source Columns to Destination Fields
While creating a sync on valmi.io, you can select a source table and choose the previously created Stripe connection as the destination. Select one of the channels as the destination object. We have chosen theperson object for this example. The next screen lets the user map the source columns onto the fields of the Stripe object. The picture below shows that we have selected append destination sync mode. employee_id has been chosen as the primary key for the warehouse source.
The source field email has been mapped to the destination field email.
3. Verifying data loaded into Customer.io
Subsequently, once the synchronization process is complete with Customer.io, you will begin to observe the delivery statistics.
After successful synchronization, you can verify the user details on the people page of Customer.io. Below is one example of synchronization where user details are synced.
