Customer.io
Sync customer profiles and events to Customer.io for messaging automation. Keep your Customer.io people in sync with your warehouse data.
Prerequisites
- A Customer.io account
- Your Site ID and Track API key (found in Settings > API Credentials)
Authentication
Customer.io uses Site ID & Track API Key authentication.
- In Customer.io, go to Settings > API Credentials
- Copy your Site ID and Track API Key (not the App API key)
- Enter both values in Zeotap
Configuration
| Field | Type | Required | Description |
|---|---|---|---|
| Region | Select | Yes | Customer.io data center: US (track.customer.io) or EU (track-eu.customer.io). Default: US |
Target Settings
Customer.io does not have additional target settings. Data is sent to the Track API for people identification and event tracking.
Supported Operations
Sync Modes: Upsert, Insert
Audience Sync Modes: Add, Remove, Mirror, Upsert
Features
- Field Mapping: Yes
- Schema Introspection: No
Required Mapping Fields
| Field | Description |
|---|---|
| id | Person identifier |
Default Destination Fields
id, email, created_at, first_name, last_name, plan
Realtime syncs
A Customer.io destination can also receive a realtime sync from a realtime audience: one person at a time, within seconds of the event that changed their answer, rather than a list on a schedule. The same destination — region, Site ID and Track API key — serves both.
Customer.io segments filter on attributes, so a realtime sync sets one person attribute you name to true when the person joins and to false when they leave. Build the segment on that attribute being true. The person is the audience’s destination key, which Customer.io reads as their ID, email address or Customer.io ID according to your workspace’s settings. Leaving changes only that attribute and never deletes the person — unlike a scheduled sync that removes people, which deletes them from Customer.io. By default neither joining nor leaving creates a person Customer.io does not know, and People Customer.io does not know yet turns creation on for joins.
Some failures are silent. Customer.io answers success before it applies a change, and reports one it could not apply only in the workspace’s Activity Logs, as a failed attribute change. Such a change counts as sent. Settings and the full behaviour are under Realtime Syncs → Customer.io.
Troubleshooting
Site ID vs App API Key
Ensure you are using the Track API Key, not the App API Key. The Track API Key is used for server-side data ingestion.
Wrong region
Verify your Customer.io region. US and EU accounts have separate endpoints and data cannot cross regions.
Person not updating
Customer.io identifies people by the id field. Ensure your model includes a stable, unique identifier for each person.