Lifecycle marketers
Track opens, clicks and conversions across every campaign and flow.
Read & reportControlled changes
See your Klaviyo numbers in ChatGPT.
Compare message results and flow trends with explicit conversion metrics. Changes you can allow for teammates and AI tools: profile details and custom properties, list membership, email suppression, draft campaign subjects, send times and sends, tags and flow status. Allowed changes apply right away and are recorded in history.
- Campaign and flow results in a sheet that refreshes itself
- Compare sends month over month without exporting
- Ask an AI assistant which emails worked, using live Klaviyo data
ChatGPTUpdated November 2026
| Recipients | Delivered | Unique clicks |
|---|---|---|
| 1,240 | 1,240 | 860 |
| 640 | 640 | 410 |
| 210 | 210 | 155 |
- SetupPaste a key or token
- Reads182 report fields across 10 datasets
- Changes10 change actions
- RefreshDaily to every 15 minutes
Who uses Datapipe with Klaviyo
Founders
See which emails bring in revenue without logging in to Klaviyo.
Agencies
Send each client a monthly email performance report.
What you can do with Klaviyo
Read and report
Read expanded campaign and flow message performance, native flow time series and current inventories for campaigns, flows, actions, messages and metric definitions.
- Klaviyo emails
- Campaign message performance
- Flow message performance
- Flow performance over time
- and 6 more
Controlled changes
- Update profile name, organization or job title
- Set a custom property on a profile
- Add a profile to a list or remove them
- Suppress or unsuppress a profile's email
- Edit a draft campaign's subject and sender
- Add or remove a campaign tag
- Set a draft campaign's send time
- Send a draft campaign
- Add or remove a flow tag
- Set a flow live, manual or draft
Changes stay off until you allow them. Allowed changes apply to Klaviyo right away, and history keeps the values before and after.
Full read details
Account currency and time zone stay visible; rates retain fractions and attribution follows Klaviyo settings.
Examples for your team
Track a flow over time
Choose a conversion metric and compare hourly, daily, weekly or monthly flow message results.
- Scheduled refresh
- Latest Klaviyo data
- Updated report
Limit: Native bucket boundaries, interval limits and provider quotas stay attached to the report.
Choose the right conversion metric
Find the metric ID and its integration before building a performance report.
- Scheduled refresh
- Latest Klaviyo data
- Updated report
Limit: Keep similarly named conversion events separate and retain account currency beside reported amounts.
Review a campaign's reported results
Bring email clicks and provider-reported revenue into the campaign recap.
- Scheduled refresh
- Latest Klaviyo data
- Updated report
Limit: Keep the provider's attribution definitions attached to the interpretation.
Switch a finished flow live
ChatGPT turns a finished draft flow live, if you've allowed that change.
- Allowed
- Applied
- Recorded
Limit: Klaviyo starts sending it, and the status change is recorded in history.
Fix things in Klaviyo without opening it
Spot it, fix it
See the problem in your report, then make the fix in Datapipe instead of opening Klaviyo, finding the record and retyping it.
More people can help
Teammates and AI tools you allow can make changes without getting edit access to Klaviyo.
You decide what can change
Changes stay off until you allow them. Every change is recorded with who made it and the values before and after.
Jobs you can stop doing by hand in Klaviyo
Update profile name, organization or job title
Match organization names to your CRM
TodayLook up a customer in your CRM, then open their Klaviyo profile and retype the organization by hand.
With DatapipeChatGPT reads your CRM data source in the same project and sets the organization for each profile. History keeps each before and after.
Update job titles after a promotion
TodayHear a customer changed roles, search for their profile and edit the title field.
With DatapipeJordan updates the job title on the existing profile from Datapipe. Email, phone and consent stay unchanged.
Fix name capitalization from signup forms
TodayFind profiles saved as "avery CHEN" and retype first and last names one at a time.
With DatapipeFix the names on each profile you find. Lists and subscription consent stay unchanged.
Exactly what this can change
Updates an existing profile's basic details. Klaviyo flows may react. Email, phone, identifiers, subscription consent, lists and campaign sending are unchanged.
Supported fields: First name, Last name, Organization, Job title.
Set a custom property on a profile
Record each customer's plan tier
TodayLook up the plan in your billing tool, open the Klaviyo profile and type a Plan property by hand.
With DatapipeChatGPT compares your billing data source with the profile and sets the Plan value. Each change is recorded with the before and after values.
Fix a misspelled preferred store
TodayFind profiles where Preferred store reads "Brooklin" and retype it one by one.
With DatapipeA teammate corrects the property value on each profile. Other properties stay unchanged.
Exactly what this can change
Sets one text custom property on one existing profile, adding it to that profile if it's missing. Other properties, email, phone, consent and lists are unchanged. Flows and segments that use the property may react.
Supported fields: Custom property name, Value.
Add a profile to a list or remove them
Add a new wholesale buyer to the VIP list
TodaySearch the profile in Klaviyo, open Lists and add it to VIP by hand.
With DatapipeJordan adds the profile to the VIP list from Datapipe. The notice warns that list flows may start.
Take a customer off a promo list after a complaint
TodayFind the profile and remove it from the Spring promo list in Klaviyo.
With DatapipeRemove the profile from that list. Their consent stays as it was.
Exactly what this can change
Adds one profile to one list or removes them from it. Adding someone to a list doesn't subscribe them, but flows that start when someone joins the list can send them email. Removing them doesn't unsubscribe them.
Supported fields: List ID, Change.
Suppress or unsuppress a profile's email
Stop email to a customer who asked by phone
TodayWrite down the request, open Klaviyo later and suppress the profile by hand.
With DatapipeA teammate suppresses the profile right after the call, and marketing email to them stops.
Lift a suppression added by mistake
TodayAsk around to find out who suppressed the profile, then unsuppress it in Klaviyo.
With DatapipeUnsuppress the profile from Datapipe. Datapipe shows the current suppression reasons first, and only a manual one can be lifted.
Exactly what this can change
Suppressing stops Klaviyo sending marketing email to this profile, whatever their consent. Unsuppressing lifts only a suppression added by hand: bounces, spam complaints and unsubscribes stay, and email reaches them again only if they're subscribed. SMS and consent records are unchanged.
Supported fields: Change.
Edit a draft campaign's subject and sender
Tighten a draft subject line before review
TodayCopy the subject into a doc, collect edits, then paste the final line into the Klaviyo campaign.
With DatapipeChatGPT reads last month's campaign results and writes a sharper subject and preview text. History keeps the old wording, and nothing is sent.
Fix the sender name on a client's draft
TodayNotice the From name still shows the agency and edit it in the campaign builder.
With DatapipeSet the client's sender name and reply-to address on the draft. History records the before and after.
Exactly what this can change
Changes the subject, preview text, sender name, sender email or reply-to address of one draft email campaign. Nothing is sent. Use a sender email Klaviyo can send from. Content, audiences and send time are unchanged.
Supported fields: Subject, Preview text, Sender name, Sender email, Reply-to email.
Add or remove a campaign tag
Tag campaigns by season for reporting
TodayOpen each holiday campaign in Klaviyo and add the Holiday tag one at a time.
With DatapipeA teammate adds the Holiday tag to each campaign in the campaign report.
Remove an outdated client tag
TodayFind campaigns still tagged with an old client name and untag them by hand.
With DatapipeRemove the old tag from each campaign. Nothing is sent, and every change is recorded in history.
Exactly what this can change
Adds or removes one existing tag on one campaign. Tags only organize campaigns in Klaviyo, so nothing is sent. New tags are not created.
Supported fields: Tag, Change.
Set a draft campaign's send time
Pick Tuesday morning for the newsletter
TodayOpen the draft, set the send time and remember to queue it later.
With DatapipeSet the send time on the draft. The draft keeps that time until someone sends it.
Move a send time after a launch slips
TodayOpen the draft and change its send time by hand.
With DatapipeJordan sets the new time on the draft from Datapipe.
Exactly what this can change
Sets the time one draft campaign will send, at least 15 minutes from now. The campaign stays a draft and isn't queued until a Send a draft campaign change is applied; it then sends at this time.
Supported fields: Send at (UTC).
Send a draft campaign
Send a finished draft from your phone
TodayWait until you're at a desk to open Klaviyo and click Send.
With DatapipeSend the finished draft from Datapipe on your phone. Datapipe shows its send time first. If sends need approval, it waits on the Changes page.
Queue a scheduled announcement
TodayOpen the draft at the right moment and schedule it in Klaviyo.
With DatapipeSend it once the send time is set, and Klaviyo sends at that time.
Exactly what this can change
Queues one draft campaign to send to its audiences. If a send time is set, Klaviyo sends at that time; otherwise it starts sending now. Email that has gone out can't be recalled.
Supported fields: Send.
Add or remove a flow tag
Label flows by client or brand
TodayOpen each flow and add the client tag by hand so the team can filter.
With DatapipeA teammate adds the client tag to each flow in the flow report, and the flows keep running.
Retire a tag after a rebrand
TodayFind flows with the old brand tag and untag them one by one.
With DatapipeRemove the old tag from each flow. Every change is recorded in history.
Exactly what this can change
Adds or removes one existing tag on one flow. Tags only organize flows in Klaviyo, so the flow keeps running as before. New tags are not created.
Supported fields: Tag, Change.
Set a flow live, manual or draft
Pause a welcome flow during a site outage
TodayFind the flow and switch it to Manual so new signups don't get broken links.
With DatapipeSet the flow to Manual, and Klaviyo holds its messages until it goes live again.
Turn a reviewed flow live
TodayWait for the reviewer, then open the flow and set it live yourself.
With DatapipeSet the flow to Live once it is reviewed. The notice explains that it starts sending.
Exactly what this can change
Changes one flow's status for every message in it. Live starts sending email or SMS to everyone who triggers the flow. Manual holds messages without sending them. Draft stops the flow.
Supported fields: Status.
Set a flow live, manual or draftFlow · Winter welcome series · made by ChatGPT for Jordan Blake
| Field | Before | After |
|---|---|---|
| Status | Draft | Live |
You control who can change what
- A change is allowed for this data source
- A teammate or AI tool makes it
- It applies right away, or waits for approval if you set that
- Recorded with the values before and after
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 rules and limits
Provider permissions still apply, and automations in Klaviyo 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.
Before you connect
What you need
An API key or token from your Klaviyo account.
Read and write
Read access for reports. The 10 change actions need edit access in Klaviyo and stay off until the owner, an admin or a project manager allows them.
Limits and exclusions
Rates stay fractions and unique counts cannot be added across rows or buckets. Campaign time series, raw events and typed profile columns are not included.
Full details and limits
Nine new reports join the original campaign report. Performance follows send dates in your Klaviyo account time zone and its attribution settings; current inventories ignore report dates. Rates stay fractions and unique counts cannot be added across rows or buckets. Hourly flow reporting supports up to seven days and daily up to sixty days. Reporting requests have strict per-minute and daily quotas; permissions and history limits apply. Text message spend is in US dollars, while conversion amounts follow account currency. Existing data sources may need renewed read access for flows. Campaign time series, raw events and typed profile columns are not included. Optional profile corrections remain separate: they stay off until the action is allowed for this data source, and every change is recorded in history.
Reports you can build
10 reporting datasets, each with its own fields. Pick one in the app, then choose your columns.
- Klaviyo emails
- Campaign message performance
- Flow message performance
- Flow performance over time
- Flows inventory
- Actions for a flow
- Messages for a flow action
- Metrics inventory
- Campaign inventory
- Account reporting settings
What each dataset reports
- Klaviyo emails
Sends, clicks, and revenue.
- Campaign message performance
Native send-date performance in the Klaviyo account time zone, using one explicitly selected conversion metric. Rates stay fractions; unique counts are not additive across rows or time buckets. Conversion value follows account currency; text message spend is USD. Tracking, attribution settings, privacy automation and provider history affect results. Text credit/spend/ROI can be null for contracted plans and older history. Reporting endpoints allow only two requests per minute and 225 per day each; scheduled reports share provider quotas. Campaign and message IDs always define the grain. Additional selected grouping fields split results further. Campaign names and setup are available in Campaign inventory; no campaign-series endpoint is simulated.
- Flow message performance
Native send-date performance in the Klaviyo account time zone, using one explicitly selected conversion metric. Rates stay fractions; unique counts are not additive across rows or time buckets. Conversion value follows account currency; text message spend is USD. Tracking, attribution settings, privacy automation and provider history affect results. Text credit/spend/ROI can be null for contracted plans and older history. Reporting endpoints allow only two requests per minute and 225 per day each; scheduled reports share provider quotas. Flow and message IDs always define the grain. Additional selected grouping fields split results further. This read does not trigger, pause or edit a flow.
- Flow performance over time
Native send-date performance in the Klaviyo account time zone, using one explicitly selected conversion metric. Rates stay fractions; unique counts are not additive across rows or time buckets. Conversion value follows account currency; text message spend is USD. Tracking, attribution settings, privacy automation and provider history affect results. Text credit/spend/ROI can be null for contracted plans and older history. Reporting endpoints allow only two requests per minute and 225 per day each; scheduled reports share provider quotas. One row per returned native timestamp and message grouping. Choose hourly (up to 7 days), daily (up to 60 days), weekly or monthly; default daily. Native bucket timestamps retain provider offsets, including boundary buckets; no daily campaign totals are invented.
- Flows inventory
Current accessible inventory, independent of report dates; it does not reconstruct past account state. Requires the corresponding account read permission. Read flow IDs, names, status, archival state and trigger type. Flow definitions and execution changes are not included.
- Actions for a flow
Current accessible inventory, independent of report dates; it does not reconstruct past account state. Requires the corresponding account read permission. Choose one existing flow ID. Read action type, status and name from the current encoded definition; absent fields stay null. This does not execute an action or expose its full configuration.
- Messages for a flow action
Current accessible inventory, independent of report dates; it does not reconstruct past account state. Requires the corresponding account read permission. Choose one existing flow action ID. Names, channel, subject and preview describe current messages; message bodies, recipient data and template contents are excluded. This does not send a message.
- Metrics inventory
Current accessible inventory, independent of report dates; it does not reconstruct past account state. Requires the corresponding account read permission. Choose the conversion metric by ID rather than guessing from its name. Integration metadata distinguishes similarly named metrics; this dataset lists definitions, not metric aggregates or raw events.
- Campaign inventory
Current accessible inventory, independent of report dates; it does not reconstruct past account state. Requires the corresponding account read permission. Uses the current campaign definition for names, builder and archival state. Metadata is not a send log or campaign performance time series.
- Account reporting settings
Current accessible inventory, independent of report dates; it does not reconstruct past account state. Requires the corresponding account read permission. Read the account's currency, time zone, locale and test-account flag. Public API keys and account contact details are excluded. Provider test accounts still use Klaviyo production infrastructure.
Metrics and dimensions
182 report fields across 10 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.
Send Klaviyo data anywhere
Google SheetsA sheet that refreshes every morning.
Data StudioCharts that read the same numbers.
BigQueryA warehouse table for the same columns.
ClickHousePush rows into ClickHouse over HTTPS with an API key.
AWS S3Write report files to your S3 bucket with IAM access keys.
Amazon RedshiftLoad rows into Redshift via the Data API with IAM keys.
FireboltPush rows into Firebolt over HTTPS with a Service Account.
PostgreSQLWrite report rows into PostgreSQL with database credentials.
MySQLWrite report rows into MySQL with database credentials.
SnowflakePush rows into Snowflake over HTTPS with a PAT token.
Databricks SQLLoad rows into Databricks SQL with a Personal Access Token.
Cloudflare R2Write report files to your R2 bucket with access keys.
Excel / CSVA Drive file you can open in Excel.
ClaudeAsk Claude about these numbers in a sentence.ChatGPTAsk ChatGPT about these numbers in a sentence.
APIRead the same rows from your own tool.Don't see yours? Use CSV or APIDownload the rows, or read them from your own tool.Ask AI about your data
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 Klaviyo changes. They can never widen their own access.
Which automated email sequences in Klaviyo had the highest unsubscribe rates last month?
The customer re-engagement sequence had an above-average 1.8% unsubscribe rate alongside a 42% open rate.
Better than exporting by hand
- It refreshes on its own, so nobody pastes in a new export.
- Each campaign can be its own row.
- Spend sits next to results, so a costly campaign is obvious.
- The same numbers can be split by who they came from.
- You can keep a row per day instead of one lump sum.
- Orders and sales stay in the report, ready each morning.
What can you do with this data?
Explore all use cases →Start from a goal
Campaign message performance
Native send-date performance in the Klaviyo account time zone, using one explicitly selected conversion metric.
Use this template →Flow message performance
Native send-date performance in the Klaviyo account time zone, using one explicitly selected conversion metric.
Use this template →Flow performance over time
Native send-date performance in the Klaviyo account time zone, using one explicitly selected conversion metric.
Use this template →Flows inventory
Current accessible inventory, independent of report dates; it does not reconstruct past account state.
Use this template →How it works
Connect Klaviyo from Data sources and allow the read access your reports need.
Pick where it goes. This one sends the numbers to ChatGPT.
Choose a report and conversion metric, then refresh on a schedule.
Sample report
| Recipients | Delivered | Unique clicks | Conversions | Fractional rates | Attributed value | Native time buckets | Flow and message IDs |
|---|---|---|---|---|---|---|---|
| 1,240 | 1,240 | 860 | 1,240 | 1,240 | 1,240 | 1,240 | 1,240 |
| 640 | 640 | 410 | 640 | 640 | 640 | 640 | 640 |
| 210 | 210 | 155 | 210 | 210 | 210 | 210 | 210 |
Sample numbers, so you can see the shape. Your report uses your accounts.
Works well with Klaviyo
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.
Klaviyo + Shopify“Did orders rise in the days after each send?”See Shopify →
Klaviyo + Google Analytics“Did site visits rise after each email went out?”See Google Analytics →
Klaviyo + Stripe“Does the revenue credited to email line up with the payments you collected?”See Stripe →
Klaviyo + HubSpot“Did the last campaign move any deals forward?”See HubSpot →Questions
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 Klaviyo account. Nobody else gets a Klaviyo 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 Klaviyo received it, the request is marked Uncertain and is never retried automatically, so you can check Klaviyo first.
Yes. Datapipe reads the reports on this page and can make 10 kinds of change: update profile name, organization or job title; set a custom property on a profile; add a profile to a list or remove them; suppress or unsuppress a profile's email; edit a draft campaign's subject and sender; add or remove a campaign tag; set a draft campaign's send time; send a draft campaign; add or remove a flow tag; set a flow live, manual or draft. 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 182 report fields across 10 datasets. You pick the columns when you build the report.
Available rows depend on the connected account, selected report type, its date rules and provider limits. Current-inventory reports show current records rather than earlier historical states.
One for each Klaviyo 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.
Try Klaviyo with sample data first
Build the report first, then add Klaviyo when you are ready.