Lifecycle marketers
Track opens, clicks and list growth across every send.
Review email campaigns, newsletters and dynamic segment counts, with audience attribute updates from Datapipe.
Start free Connect Customer.io
Updated November 2026
| Campaign | Messages sent | Deliveries |
|---|---|---|
| Onboarding Sequence | 860 | 1,240 |
| Retargeting | 410 | 640 |
| Brand search | 155 | 210 |
Track opens, clicks and list growth across every send.
See whether the newsletter is growing without logging in.
Send each client a monthly email performance report.
Read active campaigns, broadcast newsletters and segment sizes using your Customer.io App API credentials.
Changes stay off until you allow them. Allowed changes apply to Customer.io right away, and history keeps the values before and after.
Message metrics remain cumulative counters from the provider.
Refresh sent, open and click counters for automated messaging journeys.
Limit: Keep unique message performance figures within their own native reporting period.
A teammate updates a person's first name or email attribute, and Customer.io updates the profile.
Limit: History keeps the exact before and after attributes.
See the problem in your report, then make the fix in Datapipe instead of opening Customer.io, finding the record and retyping it.
Teammates and AI tools you allow can make changes without getting edit access to Customer.io.
Changes stay off until you allow them. Every change is recorded with who made it and the values before and after.
TodayLog in to Customer.io, navigate to People, search user ID, click Attributes, edit attribute value, and save.
With DatapipeIdentify newly signed enterprise accounts in your product usage report and update plan_tier to enterprise_pilot.
TodayOpen Customer.io profile, search email, update first name and corrected email address.
With DatapipeSpot misformatted subscriber records in your campaign deliverability report and correct the details from Datapipe.
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_.
Supported fields: Email address, First name, Last name.
TodayLog in to Customer.io, open People search, find user ID, navigate to settings, click Delete Person, and confirm permanently.
With DatapipeReview the privacy compliance queue in your user audit report and delete the profile with a verified confirmation token. Deletes can be set to need approval first.
TodaySearch test account in Customer.io workspace and manually trigger profile deletion.
With DatapipeDelete the test profile from your QA audit list in Datapipe. History records who deleted it and when.
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_.
Supported fields: Confirm deletion.
| Field | Before | After |
|---|---|---|
| plan_tier | trial_expired | enterprise_pilot |
Source changes are managed on the Changes page in Datapipe. Approval is optional: set it for risky changes, for every change, or for one person. AI tools such as ChatGPT can never widen their own access. Who can turn this on?
Provider permissions still apply, and automations in Customer.io may react to changes.
Only fields supported by an allowed action can be changed; for some actions the owner, an admin or a project manager also picks the individual writable fields.
An API key or token from your Customer.io account.
Read access for reports. The 2 change actions need edit access in Customer.io and stay off until the owner, an admin or a project manager allows them.
Anything your connected account cannot see in Customer.io.
Campaign delivery performance, broadcast newsletters, and dynamic segment counts from your Customer.io workspace.
Reporting reads campaigns and newsletters. Optional person profile attribute updates and profile deletion are off until allowed for this data source, and every change is recorded in history. Journeys and automated triggers cannot be altered.
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.
29 report fields across 3 datasets.
Hover or tap a field to see what it means. Custom fields from your own account appear after you connect.
No fields match. Try another search or choose All.
Claude or ChatGPT can read the same numbers. You ask in a normal sentence, and the answer stays with your report.
AI tools can also make allowed Customer.io changes. They can never widen their own access.
Which automated email workflows in Customer.io had high bounce rates or unsubscribes this week?
The day-7 retention campaign had a 2.1% bounce rate on unverified signups, while activation emails reached 68% open rates.
Active and stopped campaigns with messages sent, deliveries, opens, clicks, unsubscribes and bounces within the report dates (UTC).
Use this template →Newsletter broadcasts sent during the selected UTC dates, with total sends, deliveries, opens, clicks, unsubscribes and bounces since each send.
Use this template →Segment inventory and current member counts, not filtered by report dates.
Use this template →Create a project and choose Customer.io in Data sources.
Pick where it goes. This one sends the numbers to Google Drive.
Pick where it goes. Choose campaigns, newsletters or segments and a destination.
Sample range Oct 1–Oct 29. Each row is one campaign.
| Campaign | Messages sent | Deliveries | Opens | Clicks | Segment name | Type | Member count |
|---|---|---|---|---|---|---|---|
| Onboarding Sequence | 860 | 1,240 | 860 | 860 | 1,240 | 1,240 | 1,240 |
| Retargeting | 410 | 640 | 410 | 410 | 640 | 640 | 640 |
| Brand search | 155 | 210 | 155 | 155 | 210 | 210 | 210 |
Sample numbers, so you can see the shape. Your report uses your accounts.
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.
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.
No. Name a project, add a data source, then choose a report and destination.
OAuth means you sign in with the service and grant access, without pasting an API key. Datapipe works with multiple partners to provide that sign-in. Some partners already provide it. Some integrations are API-only at present, so you paste a key or token. OAuth is coming soon for some. Some partners do not provide OAuth at all. The setup steps on each integration page say how that source connects. Signing in is only how the connection is made. It is not permission to change records. Where a source supports changes, those writes stay off until the workspace owner turns specific actions on and approves each one. We do not promise OAuth on every source, and we do not share dates.
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.
No. Teammates make allowed changes in Datapipe, and Datapipe applies them through the connected Customer.io account. Nobody else gets a Customer.io login from this.
Yes, if that change is allowed for them. They work through Datapipe the same way a teammate does, within the same allowed changes and fields, and every change is recorded in the Changes history. AI tools can switch changes off, but they can never widen their own access. Asking for more waits for a person.
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.
Datapipe sends each change once and records the result in the Changes history. If it cannot confirm that Customer.io received it, the request is marked Uncertain and is never retried automatically, so you can check Customer.io first.
Yes. Datapipe reads the reports on this page and can make 2 kinds of change: update person attributes; delete person profile. Each one stays off until the owner, an admin or a project manager allows it for this data source. Allowed changes apply right away and are recorded in the Changes history. Provider permissions still apply.
This page lists 29 report fields across 3 datasets. You pick the columns when you build the report.
Campaign delivery performance, broadcast newsletters, and dynamic segment counts from your Customer.io workspace. Account permissions and the records available from the provider determine which rows can be read.
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.
Yes. The same numbers can go to a sheet, a chart, a warehouse, or an assistant.
Build the report first, then add Customer.io when you are ready.