Does Klaviyo show me which flows sell which products?

Not as a built-in report. Klaviyo's Conversion report shows revenue per flow, and order attribution shows revenue per order, but the cross-cut — flow × product — isn't a default view. You'd typically export both and pivot. Ask AI Data Connector exposes this join directly and ties it to your Shopify product catalogue.

Are my flows or my campaigns earning more revenue?

That depends on your audience mix and the question depends on cross-cutting both. Ask AI exposes flow-level and campaign-level revenue, opens, clicks and revenue-per-send side by side, including a 'top flows' and 'top campaigns' view so you can rank like-for-like without rebuilding the comparison in a spreadsheet.

Can I see which Klaviyo flow drives my highest-value customers?

Yes — Ask AI maps Klaviyo's order attribution back to your Shopify customers, so you can ask 'which flow brings in the highest repeat-purchase rate' or 'do welcome-flow customers spend more than browse-abandonment customers' without exporting both data sets.

What about Klaviyo SMS — does it work the same way?

Yes. SMS campaigns and flows show up alongside email in the same campaign and flow tables, so you can ask 'split revenue between SMS and email this quarter' or 'which SMS flow has the highest revenue per recipient' as one query rather than switching between two reports.

Get Klaviyo Flow ROI & Per-Product Attribution into Claude

Q: Does Klaviyo have an MCP server for Claude?

Klaviyo has a comprehensive API but no ready-made MCP server. Ask AI Data Connector connects Klaviyo to Claude (and ChatGPT, Gemini, Perplexity) through a single OAuth connection, so you can ask flow, campaign and list questions in plain English with no code.

Klaviyo is the email and SMS engine for a lot of Shopify stores, and its dashboards are decent. The frustration starts when you try to ask anything that crosses two dashboards. "Which flow drives my best products?" — flow report says revenue, product report says revenue, neither one combines them. "How much of my Q1 revenue was email vs. SMS, broken down by flow?" — same problem. Plus the inevitable Klaviyo answer: export to CSV and pivot.

This post is about closing that gap by wiring Klaviyo into Claude — so the cross-cuts become a single question rather than a spreadsheet.

The problem with Klaviyo's API on its own

Klaviyo has one of the more complete APIs in e-commerce SaaS — so the gap here isn't access, it's usability:

There's no turnkey MCP server. Klaviyo exposes a comprehensive API but doesn't ship a ready-made MCP integration for Claude. You'd be building and hosting the connector yourself.
Cross-cutting reports don't exist out of the box. Flow × product, campaign × segment, SMS-vs-email-by-flow, flow performance vs. broader Shopify cohorts — Klaviyo gives you the building blocks, but the assembly is on you.
Klaviyo's order attribution lives separately from your Shopify catalogue. You can see which orders Klaviyo attributes to which flow or campaign, but joining that to "which products were in those orders" is a manual job every time.

So even teams comfortable with the Klaviyo API spend their time stitching reports together rather than answering the question.

What Ask AI pulls in that the raw API doesn't

Ask AI Data Connector syncs the parts of Klaviyo that drive decisions and exposes them to Claude (and ChatGPT, Gemini, Perplexity) through a single connection:

Flow performance

Revenue, recipients, opens, clicks, click-to-open and revenue-per-send for every flow
A "top flows" view that ranks like-for-like — useful for the "which flow is actually working" question that requires three reports inside Klaviyo

Campaign performance

The same metrics for one-off campaigns, joined to the same revenue source as flows
A "top campaigns" view so flows and campaigns can be compared head-to-head without rebuilding the comparison

Per-product attribution

Klaviyo's order attribution joined to your Shopify product catalogue
So "which flow sold this product last quarter" and "which products lean on email vs. show up organically" become single queries

List growth and signup trends

Signup-source breakdowns and list growth over time, so audience-mix changes are visible rather than buried

SMS and email side by side

SMS flows and campaigns live in the same tables, so channel splits don't require switching reports

Why "Klaviyo in Claude" is different from "Klaviyo in a dashboard"

Here's what becomes easy that's hard inside Klaviyo itself.

A few questions Claude can answer once Klaviyo + Shopify are connected:

"Which flow drove the most revenue for my top three products this quarter?"
"Are my campaigns or my flows generating more revenue per recipient over the last 90 days?"
"Welcome-flow customers vs. browse-abandonment customers — which segment has the higher repeat-purchase rate?"
"Which SMS flow has the highest revenue per send, and how does it compare to the email version?"
"List growth is up 15% — is revenue per subscriber holding steady, or are we attracting lower-intent signups?"

These are cross-cuts no single Klaviyo screen answers cleanly — and questions the raw API won't answer without a lot of glue code.

A note on predictive metrics

Klaviyo's UI surfaces a couple of predictive metrics — predicted CLV and expected date of next order — that get used a lot in segmentation. Worth being straight about this: Ask AI doesn't currently sync Klaviyo's per-profile predictive scores. What it does sync is the underlying revenue, frequency and recency data the predictions are built from, joined to your Shopify customers — so questions about high-LTV cohorts, repeat-purchase rates and dormancy are answerable directly from the raw signals rather than via Klaviyo's modelled score.

How to connect Klaviyo

Setup takes a couple of minutes:

Sign up or log in to your Ask AI Data Connector dashboard
Go to Data Sources and find Klaviyo
Paste your Klaviyo private API key (generated in Klaviyo under Settings → API Keys)
Click Sync now — we'll pull your flows, campaigns, lists and product attribution
Go to API Keys, generate a key, and connect it to Claude

That's it. Klaviyo is now queryable in plain English, joined to the rest of your Shopify stack.

The bottom line

Klaviyo has the data. The gap is the assembly: no turnkey Claude integration, no cross-cut reports, and a catalogue join you do by hand every time. Ask AI fills that gap — and once flow performance, campaign performance and product attribution are all in one place, the questions you actually want to ask become single conversations.