Source connector

Customer.io connector

Customer.io integration for databases, warehouses and BI tools

Messaging automation based on product and behavioral data. Datrise captures Customer.io entities such as profiles, segments, campaigns, deliveries, and conversion events, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Customer.io App API v1 authenticates with API key, and Customer.io caps calls at 10 requests per second on most App API endpoints; transactional messages share a soft 3,000 requests per 3 seconds limit and API-triggered broadcasts are capped at 1 request every 10 seconds.

Of the 5 objects, 3 sync as upserts keyed on the primary key and 2 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `customer_io_profiles`) with a schema derived from the Customer.io API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Customer.io pipeline page, and join the waitlist to get the Customer.io connector (Marketing) with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Customer.io data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
profiles	customer_io_profiles	Upsert by primary key, incremental on updated-at
segments	customer_io_segments	Upsert by primary key, incremental on updated-at
campaigns	customer_io_campaigns	Upsert by primary key, incremental on updated-at
deliveries	customer_io_deliveries	Append-only, incremental by timestamp
conversion events	customer_io_conversion_events	Append-only, incremental by timestamp

Customer.io API: setup facts for the connector

Verified against the vendor documentation on 2026-09-03. Unknown values are left blank rather than guessed.

API	Customer.io App API v1
Authentication	API key — An App API Key sent as a Bearer token in the `Authorization` header; the Track and Pipelines APIs use separate credentials and separate limits.
Pagination	cursor — List endpoints take a `limit` and return a `next` cursor in the response `meta` object, which is sent back as `start` on the following request.
Rate limit	10 requests per second on most App API endpoints; transactional messages share a soft 3,000 requests per 3 seconds limit and API-triggered broadcasts are capped at 1 request every 10 seconds
Incremental cursor	Not published
Webhooks	Yes — Reporting Webhooks
Bulk export	Yes — Exports API (exportPeopleData / exportDeliveriesData, asynchronous)
Deletes detectable	Not published

Official API reference

What bites when replicating Customer.io

Exports are asynchronous: `exportPeopleData` returns export metadata only, and the file has to be pulled later through `downloadExport`, so a connector must poll for completion rather than stream results.
The 10 requests/second cap covers almost every App API endpoint and returns a `Retry-After` header on 429, but API-triggered broadcasts allow only 1 request every 10 seconds — a hundred times tighter than the rest of the API.
There is no updated-at filter on people, so catching an attribute change that no Reporting Webhook covers means re-running `exportPeopleData` over the whole audience.
The App API Key is a different credential from the Track and Pipelines API keys and carries its own limits, so a Track key sent as a Bearer token to `/v1/exports` fails authentication rather than rate-limiting.

Compare this against every other documented API

Popular destinations for Customer.io

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Customer.io connector FAQ

What Customer.io data does the connector extract?: 5 objects: profiles, segments, campaigns, deliveries and conversion events. Each lands in its own table with types preserved; history-style objects (2: deliveries and conversion events) load as append-only streams.
Is the Customer.io integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Customer.io data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Customer.io → destination pair has its own page with the object-to-table mapping.

Related Marketing sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Customer.io pipeline with guided onboarding

Join the waitlist to get priority access for Customer.io integrations with guided setup, schema-aware mapping, and production-grade incremental sync.