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