Campaigns
Read each campaign’s type and start date, with messages sent, deliveries, opens, clicks, unsubscribes and bounces for the dates you pick.
Customer.io connector · Messaging reports
Bring Customer.io campaigns, newsletters and segment sizes into your reports and AI assistants. Then update a person’s email or name, or delete a person, from Datapipe, with access your team controls.
Start free See what you can change
Updated November 2026
| Campaign | Deliveries | Clicks |
|---|---|---|
| Trial onboarding | 4,812 | 611 |
| Win-back | 1,904 | 148 |
| Feature announcement | 7,230 | 902 |
One Customer.io workspace is the data source, in the US or EU region.
Read each campaign’s type and start date, with messages sent, deliveries, opens, clicks, unsubscribes and bounces for the dates you pick.
See each newsletter’s send time, recipients, deliveries, opens, clicks, unsubscribes and bounces.
List segments with type, state and member count.
A private key carries its region, so EU workspaces connect the same way.
3 reporting datasets, each with its own fields. Pick one in the app, then choose your columns.
Active and stopped campaigns with messages sent, deliveries, opens, clicks, unsubscribes and bounces within the report dates (UTC).
Newsletter broadcasts sent during the selected UTC dates, with total sends, deliveries, opens, clicks, unsubscribes and bounces since each send.
Segment inventory and current member counts, not filtered by report dates. Type, calculation state and member counts.
Change an existing person’s email, first name or last name. Datapipe looks them up first and never creates a new person; their segments and history are kept.
Permanently delete a person’s profile, which stops their automated messages. It can’t be undone.
Allow the changes your team needs for this data source. Teammates and AI assistants use that access; they cannot grant themselves more.
Allowed changes apply right away unless you require approval. Set approval for risky changes, every change or a specific person. Changes history records who made each update and its result.
Changes the email, first name or last name of one existing person in Customer.io. Datapipe looks the person up first and never creates a new one. Their segments, campaigns and history are kept, and campaigns that watch these attributes can react. Needs a Customer.io private key that starts with sk_.
Permanently deletes one existing person and their profile data from Customer.io, which stops their automated messages. It can't be undone. Needs a Customer.io private key that starts with sk_.
| Field | Before | After |
|---|---|---|
| plan_tier | trial_expired | enterprise_pilot |
29 report fields across 3 datasets.
Search the available fields. Hover or tap a field to see what it means.
No fields match. Try another search or choose All.
Use Datapipe’s MCP access as your Customer.io AI integration. Ask how campaigns and newsletters performed, then make an allowed change and check it in Changes history.
Example
Which campaigns had the best click rate last month, and how big are our main segments?
Divide clicks by deliveries for each campaign last month, then list segments by member count. Correct a person’s email, if that change is allowed for you.
A Customer.io private key that starts with sk_. An older App API key works for reports only.
Changes need a private key. Deleting a person is permanent.
Create your free account, then choose Customer.io in Data sources.
Create a private key under Account Settings, then API Credentials, and paste it. Add your product analytics if you want usage beside messages.
Choose a report and destination, or allow person changes. Set approvals for deletes or anything you want reviewed first.
Add both to the same project. Each keeps its own report, so you can check them side by side or ask ChatGPT or Claude a question that needs both.
Datapipe reads campaigns and newsletters with sends, deliveries, opens, clicks, unsubscribes and bounces, and segments with their member counts.
A private key that starts with sk_, created under Account Settings, then API Credentials. An older App API key still works for reports, but it can’t make changes.
Yes, when the change is allowed for you in Datapipe. You can update a person’s email or name and delete people. You can require approval before a change applies.
Yes. A private key includes its region, so EU workspaces work without extra setup.
Free to start. Paid plans add more data sources and refresh faster.
Free and Starter refresh once a day. Pro refreshes every hour. Agency refreshes every 15 minutes on the first 50 data sources.
The workspace owner, workspace admins and project managers. Changes start off. They choose which changes are allowed for each data source and who can make them: project operators and managers, selected teammates, and the AI tools those people connect. They can change this at any time.
Yes, if you want. For each data source, approval can cover risky changes only (deleting, sending, publishing, refunds and price changes) or every change. You can also switch it on for one person, such as an intern. Those changes wait on the Changes page until the owner, an admin or a project manager approves them. Nobody but the owner approves their own change.
One for each Customer.io account you add to a project. Adding the same account to another project counts again. Reports and destinations do not use extra data sources.
Start free, add Customer.io and choose how your team reports on and updates people.