- Most stores already have the flows they need. The money is usually lost inside them: triggers that miss people, filters that let buyers through, messages stuck in Manual, and discounts sent to people who would have bought anyway.
- Start every audit by comparing trigger volume with flow recipients, then read revenue per recipient and placed order rate with attribution settings you understand. Opens are not a reliable signal.
- Fix structure first (triggers, filters, statuses, overlap), then timing and offers. Prove the biggest flows with a holdout before you call them profitable.
What is a Klaviyo flow audit, and why start there?
A Klaviyo flow audit is a structured review of every live automation in your account: what triggers it, who gets filtered out, what each message says, when it sends and whether it makes money. It is different from a redesign. You are not building new flows. You are finding the places where existing ones leak.
Flows are worth auditing first because they run every day without anyone looking at them. A weak campaign gets noticed next week. A broken abandoned cart email can quietly lose orders for a year.
For the core set of flows a store should run, see our guide to eCommerce email flows. This article asks a narrower question: are the flows you have working as designed?
Which numbers should you pull before touching any flow?
Pull a 90-day view of every live flow before you change anything. Rank flows by recipients and revenue, then audit from the top down.
| Metric | Where to find it | What it tells you | Watch out for |
|---|---|---|---|
| Trigger volume vs. recipients | Compare the trigger metric count with flow recipients | How many eligible people the flow actually reaches | Filters and Smart Sending skips explain some of the gap, not all of it |
| Revenue per recipient | Flow analytics | Earning power of each send | Inflated by generous attribution windows |
| Placed order rate | Flow analytics | Share of recipients who bought | Does not show margin or discount cost |
| Click rate | Flow analytics | Real engagement with content | Bot clicks can add noise |
| Unsubscribe and spam complaint rate | Flow analytics | Whether the flow is wearing out the list | High rates hurt email deliverability for everything else |
| Discount usage per flow | Coupon reports or order data | How much margin the flow gives away | Codes shared outside the flow |
Understand your attribution settings first
Klaviyo credits revenue to a message using a last-touch model by default. According to Klaviyo’s help center, new accounts default to 5 days for email opens and clicks, 5 days for SMS clicks and 12 hours for SMS deliveries. Older accounts may have different settings, so check yours under attribution settings.
Klaviyo notes that Apple Mail Privacy Protection opens can count toward attribution unless you exclude them, and it lets you remove bot clicks and Apple privacy opens. It also limits how often you can change these settings (up to 3 times in 30 days, per its help center). Decide once, write it down, and never compare flow revenue across periods with different settings.
Where do Klaviyo flows usually leak revenue?
The leaks fall into six groups. Work through them in order: structural problems make every other number meaningless.
1. Triggers that miss people or fire on the wrong event
Check what starts each flow. Klaviyo supports list, segment, metric, date property, price drop and low inventory triggers. Common problems:
- An abandoned checkout flow triggered by a metric that no longer fires after a theme or checkout change. Trigger volume drops and nobody notices.
- A welcome flow triggered by a list that only one of your sign-up forms feeds. Subscribers from other forms never get a welcome series.
- A browse flow built on Viewed Product with no check that the person is identifiable. Klaviyo can only email profiles it knows.
Klaviyo’s help center also says performance metrics such as Opened Email and Clicked Email cannot trigger flows, so a flow designed around “send when they open” never worked as intended.
2. Filters that let the wrong people through
Klaviyo checks metric-based trigger filters only when someone enters the flow. Profile filters are checked at entry and again before each action. If a profile fails a filter before an action, that action is skipped, but the person can continue to later steps.
That difference creates the most expensive leak we see: a recovery flow that keeps emailing someone who already bought. The “has not placed an order since starting this flow” condition belongs in a profile filter, so it is rechecked before every message. If it is missing, or it lives in a single split near the top of the flow that only checks once, buyers keep getting reminders. Also check for filters that are too strict, such as “has not been in this flow in the last 60 days” on an abandoned checkout flow, which blocks repeat customers from a perfectly valid reminder.
3. Messages stuck in Manual or Draft
Every message in a Klaviyo flow has its own status. Klaviyo’s help center explains that Live messages send automatically, Manual messages require review and are not sent automatically, and Draft messages are not set to send. One email left in Manual after a copy edit can silence the most valuable step in a flow. Open every flow and check each message status, not just the flow’s overall state.
4. Timing that ignores the buying cycle
Compare the delay before each message with when orders actually happen. A cross-sell that lands before the product arrives reads as pushy. A browse abandonment email sent three days later reaches someone who already bought elsewhere. For consumables, the reorder reminder should follow your real replenishment cycle, not a round number.
5. Overlap between flows
A single shopper can qualify for welcome, browse, cart and checkout flows in the same afternoon. Klaviyo’s Smart Sending skips a profile that received a message recently. Its help center gives default windows of 16 hours for email and 24 hours for SMS, and says messages marked as transactional are never skipped. Smart Sending prevents some pile-ups, but it decides by time, not by priority. Your checkout reminder can be skipped because a lower-value browse email went out first.
Map which flows can fire on the same person and decide the priority yourself: checkout over cart, cart over browse, browse over welcome follow-ups. Use profile filters to exit people from lower-priority flows when a higher-priority event happens.
6. Discounts that give away margin
A flow with a high placed order rate can still lose money if every message carries 15% off. Check which flows include a code in the first message, and whether full-price buyers are getting it. Our guide to abandoned cart emails without discounts shows how to hold the offer back until a later step, or only for shoppers who need it.
How do you know if a flow is actually incremental?
Attributed revenue tells you which orders a flow touched, not which orders it caused. Someone who abandoned a checkout and came back the next morning might have bought anyway. For your two or three biggest flows, run a holdout group: a random share of eligible people who enter the flow but receive nothing. In Klaviyo, a split with a random sample condition placed right under the trigger does this, with the holdout path ending without messages. Compare purchase rate and revenue per person between the two groups over the same window.
The difference is the flow’s true contribution. Multiply it by your contribution margin, subtract discount cost and sending cost, and you have the number that matters. Our guide to incrementality testing covers sample sizes and how long to run the test.
Worked example: auditing an abandoned checkout flow (illustrative numbers)
All numbers below are illustrative.
A store sees 4,000 Started Checkout events a month. Its three-email abandoned checkout flow shows 1,900 recipients. That gap is the first clue.
The audit finds three problems:
- A profile filter excludes anyone who has been in the flow in the last 90 days. Repeat customers, the most likely to come back, are blocked.
- Email 2 was set to Manual during a copy update and never switched back. Nobody has received it for four months.
- Email 1 includes a 15% code. Every recipient gets it, including people who would have finished the order anyway.
After the fixes (filter shortened to 7 days, Email 2 set to Live, code moved to Email 3), recipients rise to 3,100 a month. A 20% holdout over six weeks shows the flow’s real effect:
| Group | Placed order rate | Revenue per person | Avg. discount per order |
|---|---|---|---|
| Received the flow | 9.0% | $10.80 | $4.10 |
| Holdout (no messages) | 6.5% | $7.80 | $0.00 |
| Difference | 2.5 points | $3.00 |
At a 40% contribution margin, the extra $3.00 per person is worth $1.20 in margin. Across 3,100 recipients, that is roughly $3,700 a month before discount cost, far below the attributed revenue the dashboard showed. The next test is whether the Email 3 discount pays for itself.
Klaviyo flow audit checklist
- [ ] Export a 90-day list of live flows ranked by recipients and attributed revenue.
- [ ] Record your attribution windows and whether Apple privacy opens and bot clicks are excluded.
- [ ] Compare trigger volume with recipients for every flow and explain the gap.
- [ ] Confirm each trigger still fires after any theme, checkout or app change, and that every sign-up source feeds the welcome list.
- [ ] Confirm “has not placed an order” conditions are profile filters, and loosen filters that block repeat customers.
- [ ] Check the status of each message: Live, Manual or Draft.
- [ ] Compare delays with when orders actually happen.
- [ ] Map which flows can fire on the same person, set priorities and review Smart Sending per message.
- [ ] List which messages carry a discount and who receives it.
- [ ] Set up a holdout on your two or three largest flows.
- [ ] Report each flow on incremental margin, not attributed revenue alone.
FAQ
How often should we audit our Klaviyo flows?
Do a full audit once or twice a year, and a short check after any change to your theme, checkout, apps or sign-up forms. Those changes are the usual cause of silent trigger failures. A monthly check of trigger volume against recipients catches most problems early.
Should we judge flows on open rate?
No. Apple Mail Privacy Protection can register opens for emails nobody read, so open rate is unreliable for comparing flows or messages. Use click rate, placed order rate and revenue per recipient, and confirm the biggest flows with a holdout. You can check your own numbers with our revenue per subscriber calculator.
Is it better to fix flows or build new ones?
Fix first. A flow that reaches half the people it should, or emails buyers after they purchase, drags down anything you build next to it. Once triggers, filters, statuses and overlap are clean, new flows are easier to measure.