Customer.io connector
Set up the Customer.io connector in Kaivo: authentication, configuration, the 3 BigQuery tables it syncs, and answers to common questions.
Customer.io connector pricing, tier and credits on kaivo.ioKaivo is a fully managed data platform that syncs your Customer.io data into a Google BigQuery warehouse and keeps it up to date automatically. There is no pipeline to build and no infrastructure to run, so you can spend your time analysing your marketing and sales data instead of moving it.
What is the Customer.io connector
Section titled “What is the Customer.io connector”Sync your Customer.io messaging data into BigQuery with Kaivo to measure campaigns and newsletters alongside your product data.
| Category | Marketing & Sales, Surveys & Email |
|---|---|
| Authentication | API key |
| Setup | Self-service |
Getting started with the Customer.io connector
Section titled “Getting started with the Customer.io connector”- Sign up for Kaivo and create a workspace.
- Connect your Customer.io account.
- Choose which tables to sync.
- Wait for the initial sync to finish.
- Query your data in BigQuery or your favourite AI or BI tool.
Authenticating Customer.io
Section titled “Authenticating Customer.io”Authenticate with your App API Key.
| Field | Description |
|---|---|
| App API Key |
Configuring the Customer.io connector
Section titled “Configuring the Customer.io connector”When you set up the connector, you provide:
| Field | Description |
|---|---|
| Region | |
| Select “EU” if your account is hosted in the EU region (api-eu.customer.io); otherwise leave as “US”. |
| | Start Date |
Any data before this date will not be fetched.
|
Tables and columns synced from Customer.io
Section titled “Tables and columns synced from Customer.io”Kaivo syncs 3 tables from Customer.io into a dedicated dataset in your BigQuery warehouse. Click any table to see its columns and types.
campaigns (19 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
type |
STRING |
|
active |
BOOL |
|
created |
INT64 |
|
created_by |
STRING |
|
date_attribute |
STRING |
|
deduplicate_id |
STRING |
|
event_name |
STRING |
|
first_started |
INT64 |
|
frequency |
STRING |
|
id |
INT64 |
|
name |
STRING |
|
start_hour |
INT64 |
|
start_minutes |
INT64 |
|
state |
STRING |
|
timezone |
STRING |
|
updated |
INT64 |
|
use_customer_timezone |
BOOL |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: campaigns__actions
Section titled “Subtable: campaigns__actions”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
type |
STRING |
|
id |
INT64 |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: campaigns__msg_templates
Section titled “Subtable: campaigns__msg_templates”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
type |
STRING |
|
id |
INT64 |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: campaigns__tags
Section titled “Subtable: campaigns__tags”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
value |
JSON |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: campaigns__trigger_segment_ids
Section titled “Subtable: campaigns__trigger_segment_ids”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
value |
JSON |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
campaigns_actions (29 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
type |
STRING |
|
bcc |
STRING |
|
body |
STRING |
|
campaign_id |
INT64 |
|
created |
INT64 |
|
deduplicate_id |
STRING |
|
editor |
STRING |
|
fake_bcc |
BOOL |
|
from |
STRING |
|
from_id |
STRING |
|
headers |
STRING |
|
id |
STRING |
|
language |
STRING |
|
layout |
STRING |
|
name |
STRING |
|
parent_action_id |
INT64 |
|
preheader_text |
STRING |
|
preprocessor |
STRING |
|
recipient |
STRING |
|
recipient_environment_id |
INT64 |
|
reply_to |
STRING |
|
reply_to_id |
STRING |
|
request_method |
STRING |
|
sending_state |
STRING |
|
subject |
STRING |
|
updated |
INT64 |
|
url |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
newsletters (8 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
type |
STRING |
|
created |
INT64 |
|
deduplicate_id |
STRING |
|
id |
INT64 |
|
name |
STRING |
|
updated |
INT64 |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: newsletters__content_ids
Section titled “Subtable: newsletters__content_ids”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
value |
JSON |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: newsletters__sent_at
Section titled “Subtable: newsletters__sent_at”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
value |
JSON |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: newsletters__tags
Section titled “Subtable: newsletters__tags”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
value |
JSON |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
How the Customer.io sync works
Section titled “How the Customer.io sync works”After the first load, Kaivo keeps your BigQuery warehouse up to date for you. Where Customer.io supports it, each sync pulls only new and changed records so it stays fast; otherwise it refreshes the whole table. Every record keeps its original ID, so you won’t get duplicate rows.
Frequently asked questions
Section titled “Frequently asked questions”How long does the initial sync take for Customer.io?
Section titled “How long does the initial sync take for Customer.io?”It depends on how much history is in your Customer.io account. Most initial syncs finish within minutes, while large accounts can take a few hours. After that, syncs only fetch new and changed records, so they’re much faster.
Can I sync only some tables or columns?
Section titled “Can I sync only some tables or columns?”Yes. You pick which tables to sync when you set up the connection and can change the selection later. Tables you don’t select are never copied to your warehouse.
What happens when Customer.io’s schema changes?
Section titled “What happens when Customer.io’s schema changes?”New fields are never added automatically. You choose which fields to sync, so data you haven’t selected (sensitive personal data, for example) never lands in your warehouse. When a new field appears, it becomes available for you to add. What happens to removed or renamed fields depends on a table’s sync mode: full-refresh tables always match what’s currently in Customer.io, so dropped fields disappear, while incremental tables keep their existing columns and history, so an old field stays and newly added fields fill in over time.
How do I handle GDPR or data deletion requests?
Section titled “How do I handle GDPR or data deletion requests?”Your data lives in your own Kaivo-managed BigQuery warehouse, so the most direct option is to delete or anonymise specific records right in BigQuery. If you delete data in Customer.io instead, full-refresh tables drop it on the next sync, while incremental tables keep it, so you would remove the row in BigQuery or ask us to run a full refresh. To remove everything, delete the Customer.io connector in Kaivo and all of its synced data is deleted with it.
Common use cases for Customer.io data
Section titled “Common use cases for Customer.io data”Campaign performance
Section titled “Campaign performance”Use campaigns and campaigns_actions to track sends and engagement over time.
Newsletter reporting
Section titled “Newsletter reporting”Use newsletters to compare broadcast performance.
Product context
Section titled “Product context”Join messaging data with your product data to connect messages to user actions.
Use Customer.io data in your AI and BI tools
Section titled “Use Customer.io data in your AI and BI tools”Once Customer.io data lands in your Kaivo-managed BigQuery warehouse, you can explore it with AI tools or any BI tool that connects to BigQuery. Here’s how the most common destinations work with Customer.io data.
Claude
Section titled “Claude”Use Kaivo’s MCP server to give Claude secure, workspace-scoped access to your data. Setup guide →
Power BI
Section titled “Power BI”Microsoft’s BI tool with a native BigQuery connector. Supports direct query and scheduled refresh. Setup guide →
Data Studio
Section titled “Data Studio”Free Google BI tool with native BigQuery support. One-click connection to your Kaivo warehouse; great for SMB teams on Google Workspace. Setup guide →
Tableau
Section titled “Tableau”The premium analytics standard, with native BigQuery integration. Setup guide →
Google Sheets
Section titled “Google Sheets”Use Connected Sheets to query BigQuery directly from a spreadsheet, with no SQL. Setup guide →
Connect via Power Query’s BigQuery connector. Setup guide →
Metabase
Section titled “Metabase”Open-source BI tool with strong BigQuery support. Setup guide →
See our pricing page for Customer.io connector pricing and plan details.
Related connectors
Section titled “Related connectors”- Google Ads: Sync Google Ads to BigQuery.
- Gmail: Sync Gmail to BigQuery.
- Custobar: Sync Custobar to BigQuery.
- Google Search Console: Sync Google Search Console to BigQuery.
- HubSpot: Sync HubSpot to BigQuery.
- Adform: Sync Adform to BigQuery.