Connect Klaviyo and ask Claude how your campaigns and flows are performing — opens, clicks, list growth — read alongside what those readers did on your site.
Klaviyo is built for people who want to segment. Most owners just want to know whether the last send was better or worse than usual, and whether it produced anything. That is a sentence to Claude, not a report build.
Opens, clicks and click-through rates per send, compared against your own baseline rather than a segment you have to define first.
How your subscriber list is actually moving, and what a given send did to it.
Read with GA4 so email gets judged on outcomes, not opens.
You talk to Claude. Claude steps out to datanephew when it needs your actual Klaviyo data.
Most Klaviyo MCP setups you'll find want you to clone a GitHub repo, install dependencies, manage credentials in a config file, and keep a local server running on your own machine. This one doesn't.
Paste a read-only Klaviyo API key once.
Add your personal connector URL in Claude's settings. That's the whole install — nothing runs on your machine, and there's nothing to keep alive or update.
Open a conversation and ask about your Klaviyo data the way you'd ask a person. Claude remembers what you looked at last time.
Your own numbers are free. Anything about data you don't own — competitors, keywords you're not ranking for yet, who links to whom — is Pro.
Yes, permanently — it reads your own campaign results.
A Klaviyo API key you paste in once. Give it read access only; datanephew never writes to Klaviyo.
No. The connector is read-only.
It reads your email performance across sends. For anything Klaviyo exposes as a campaign result, Claude can compare it against your own history.
Free, and it stays free. Takes about a minute to set up.
Get started free