How to audit your Klaviyo account with Claude (Klaviyo MCP guide)

Most Klaviyo audits take a strategist three to four hours of exporting reports, clicking through flows and building a slide deck. Since Klaviyo opened its MCP server to Claude in May 2026, the same groundwork takes minutes. The catch: a generic "audit my account" prompt gives you a generic answer.

This guide covers how to connect Claude to Klaviyo, the audit we run on every new account, and the prompts that turn raw data into a prioritized fix list.

What the Klaviyo MCP server actually is

MCP (Model Context Protocol) is a standard way for AI assistants to talk to other software. The Klaviyo MCP server is a secure bridge between Claude and your Klaviyo account, built on top of Klaviyo's own APIs.

Once connected, Claude can:

• Read campaign and flow reports, segments, list growth and deliverability data
• Analyze performance across any time window you specify
• Create draft campaigns and email templates (if you allow write access)

It only acts within the permissions you grant during authorization. You can also connect it in read-only mode, which is how we recommend starting.

How to connect Claude to Klaviyo (5 minutes)

You need a paid Claude plan (Pro, Max, Team or Enterprise) and an Owner, Admin or Manager role on the Klaviyo account.

1. In Claude, open Customize > Connectors
2. Click + Add, then Add custom connector
3. Name it clearly, for example "Klaviyo - Brand Name"
4. Paste the connector URL: https://mcp.klaviyo.com/mcp?company=brand-name
5. Add &read-only=true at the end of the URL for your first sessions
6. Make sure you are logged into the right Klaviyo account, click Connect, review the permissions and click Allow
7. In a new chat, enable the connector from the + > Connectors menu

On Team or Enterprise plans, an admin adds the connector once for the organization and each person authorizes it with their own Klaviyo login.

Agency tip: create one connector and one Claude project per client account, and only enable that client's connector in a chat. It removes the risk of pulling the wrong account's numbers into a report.

The 6-part audit we run on every new account

A useful audit answers one question: where is revenue leaking, and what is it worth to fix? We run these six checks in order.

1. Flow coverage

Start with the inventory. Ask Claude to list every live flow with its trigger, number of messages, channels and last edit date.

What to look for:

• Missing core flows (welcome, abandoned checkout, browse abandonment, post-purchase, winback)
• Flows in draft or manual status that everyone assumed were live
• Flows not edited in 12+ months while the catalog, pricing or brand changed

2. Flow architecture

This is where most of the money hides. Pull the full structure of each flow: triggers, splits, delays and filters.

What to look for:

• No buyer / non-buyer split. Your welcome flow sends a first-order discount to people who already bought.
• Mistimed delays. An abandoned checkout email arriving 24 hours later instead of 1 to 4 hours.
• Overlapping flows. A customer in browse abandonment, abandoned cart and a campaign on the same day.
• Stale builds left over from an app or tool you stopped using.

3. Revenue per recipient by flow

Open rates got noisy after Apple Mail Privacy Protection, so rank flows by revenue per recipient (RPR) and placed order rate instead.

For context, Klaviyo's 2026 benchmarks across 183,000+ brands show flows generate nearly 41% of email revenue from just 5.3% of sends, with revenue per recipient nearly 18x higher than campaigns. If your flows sit well below that share, the gap is your opportunity.

4. Campaign performance patterns

Ask Claude to analyze the last 90 days of campaigns by weekday, send hour, segment and subject line style. Compare click rate and RPR, not opens.

Two questions worth asking explicitly:

• Does a second send in the same day add revenue or cannibalize the first?
• Which segments get the most sends but produce the least revenue?

5. Deliverability trend

A healthy average can hide a problem. Pull every send from the last 90 days in date order and track bounce rate, spam complaint rate and unsubscribe rate over time.

A rising trend across routine campaigns is the warning sign. A spike on a single winback send to old addresses is expected.

6. List health

Separate members added, removed and net change by month for your main list and engaged segments. Net growth can hide heavy churn, where new signups only replace the people leaving.

The prompts that make the difference

Claude does not know your benchmarks, your margins or what "good" means for your brand. Give it a framework and it becomes a sharp analyst. Skip that and you get generic advice.

Flow architecture audit

Using the Klaviyo connector for [Brand], pull the full structure of
every live flow: trigger, filters, splits, delays and channels.
For each flow, flag:
1. Missing buyer / non-buyer splits
2. Delays outside these ranges: abandoned checkout 1-4h,
   browse abandonment 2-24h, first welcome email sent immediately
3. Overlap with other flows on the same trigger window
4. Last edit date older than 12 months
Return a table: flow, issue, severity (high/medium/low), fix.

Revenue leak estimate

For the last 90 days, rank all live flows by revenue per recipient
and placed order rate. Compare each against the account average.
For the 3 weakest flows with meaningful volume, estimate the monthly
revenue gained if they reached the account average RPR.
Show your calculation.

Deliverability trend

Pull every campaign sent in the last 90 days, in date order, with
delivery, bounce, spam complaint and unsubscribe rates. Tell me
whether any metric is trending up across routine sends, excluding
winback and re-engagement sends.

Asking Claude to show its calculation matters. It lets you check the numbers before they go in front of a client or a founder.

What AI does not replace

The MCP server makes the analysis fast. It does not make the decisions. A few rules we hold to:

• Read-only first. Explore with read-only=true, then enable write access when you know exactly what you want built.
• A human approves everything customer-facing. Klaviyo itself recommends treating AI output as a strong first draft.
• Some actions stay in Klaviyo. Campaigns with A/B tests or Smart Send Time cannot be sent through the MCP server, and sent messages cannot be recalled.
• Strategy is still the job. Claude will tell you the welcome flow underperforms. Deciding the offer, the story and the brand voice is still on you.

Turn the audit into a repeatable system

Once the prompts work, save them as a Claude skill or project instructions so every audit runs the same way. That is how we audit accounts in minutes instead of days, and why every client gets the same depth of review.

If you want the full audit done for you, with the fixes built and shipped, that is exactly what our Flow Booster covers.