Connect Klaviyo to Claude and ChatGPT
Klaviyo is an owned channel, not a paid one - you pay a flat monthly fee, not a cost per send. MerchantFlow treats it that way: revenue is the headline metric and spend is recorded as zero, so your blended ROAS is not quietly distorted by a channel that has no media cost.
What you can ask once it is connected
“How much revenue did Klaviyo report last month, and how does it sit against paid?”
Klaviyo reported A$14,200 of campaign revenue for the period. It carries no media spend, so it has no ROAS and is excluded from the blended figure; paid channels spent A$21,400 against A$68,900 of net revenue. The Klaviyo number is Klaviyo’s own attribution, so treat it as that platform’s claim rather than a measured share of the total.
Example answer, shown to illustrate the shape and level of detail. Your figures come from your own connected account.
What Klaviyo alone cannot tell you
Connecting an AI directly to Klaviyo is genuinely useful, and for some questions it is all you need. It stops being enough the moment the question involves money you spent somewhere else.
- How much revenue email and SMS actually drove, in the same view as paid
- Whether owned revenue is quietly inflating a blended ROAS that has no media cost behind it
- What the orders behind that revenue were worth after cost of goods
- Where Klaviyo and a paid channel are both claiming the same order
What MerchantFlow adds
- Campaign revenue read from Klaviyo’s own conversion metric, normally Placed Order, rather than inferred from opens or clicks
- Recipients recorded per campaign, since an email has no impressions to count
- Reported as platform_reported_revenue, labelled as Klaviyo’s own claim and kept separate from MerchantFlow attribution, so it is never mistaken for a measured figure
- Owned revenue shown beside paid channels but never added into ad spend or blended ROAS, because a flat subscription is not media cost
- Marked as an owned channel with no ROAS, rather than dividing by a spend of zero and returning a number that means nothing
Klaviyo reports its own attributed revenue, and every ad platform does the same, so these figures overlap and must never be added together. MerchantFlow does not currently model cohorts or lifetime value by acquisition channel, so a Klaviyo-only cohort is not something it can answer. Your Klaviyo subscription fee is not pulled in automatically - add it as a recurring operating expense so it reaches your profit figure. Revenue reporting depends on a conversion metric being resolved on connect; until it is, MerchantFlow reports nothing rather than guessing. One Klaviyo account per store.
How to connect it
- 01
Connect Klaviyo to MerchantFlow
Authorise Klaviyo from your MerchantFlow integrations page. We start pulling and normalising the data straight away.
- 02
Add MerchantFlow as a connector in Claude or ChatGPT
Approve read-only access from your AI client's connector settings. Nothing to install on your machine. Your dashboard shows the current steps for whichever client you use, because the clients move their menus often.
- 03
Ask in plain English
Your AI now reads the same figures as your dashboard, joined across every source you have connected.
Included on every paid plan, trials included. Starter reads 90 days of history, Pro reads 12 months, and Plus and Agency read your full history.
The tools your AI calls
These are the actual tools MerchantFlow exposes for Klaviyo questions. Every claim on this page maps to one of them.
get_channel_roasget_ad_performanceget_pnl_summaryCommon questions
Can it change anything in Klaviyo?
No. The connection is read-only and no write access exists to grant. Your AI can read figures and reason about them; it cannot create, edit, pause or delete anything.
Will the numbers match my dashboard?
Yes. Your AI calls the same calculations the MerchantFlow dashboard uses, so the same question over the same period returns the same figure in both places.
