How to Audit Your Email Flows (The 125-Point Checklist)

A real email flow audit has six categories: Flow Architecture & Triggers, Content & Messaging, Segmentation & Personalization, Deliverability & Technical, Performance Metrics, and Testing & Optimization. Most brands only review one or two — usually content and basic metrics — and leave the highest-leverage issues completely untouched.

Here's what separates a real audit from a setup checklist: a setup checklist tells you whether flows exist. An audit tells you whether they're configured correctly, firing for the right people, and generating the revenue they should.

We run these audits for DTC brands every week. The same issues appear over and over — not because brands are careless, but because the highest-stakes errors are the ones you can't see. A cart abandonment flow with Smart Sending enabled doesn't announce itself as broken. It just quietly suppresses your highest-intent emails and you never know what you lost.

This is the 125-point framework we use. Six categories, severity tiers for every item, and benchmark thresholds so "check your open rate" means something specific instead of nothing at all.

What Does a Real Email Flow Audit Cover?

A real email flow audit covers six categories: Flow Architecture & Triggers, Content & Messaging, Segmentation & Personalization, Deliverability & Technical, Performance Metrics, and Testing & Optimization. Each category contains distinct checklist items with pass/fail criteria. The audit takes 3–5 hours to run thoroughly and produces a prioritized action list, not just a list of things to check.

Most published "audits" stop at content quality and surface metrics. They tell you to check your subject lines and review your open rates. That's the equivalent of a car inspection that only checks the paint job.

The categories that cost brands the most money are the ones nobody talks about: misconfigured trigger logic, flow filter errors, Smart Sending conflicts, and attribution window settings that make healthy flows look sick or broken flows look fine. These don't show up in your Klaviyo dashboard as warnings. They show up as missing revenue you have no way to account for.

Before you open a single flow in Klaviyo, understand the structure you're auditing against. Each category below has a defined scope, a set of checklist items, and — for metric-based items — a benchmark threshold that defines what passing actually looks like.

Where Are Most Email Flow Revenue Leaks Hiding?

Flow architecture errors are the highest-leverage audit findings because they're silent. A misconfigured trigger doesn't send you an error — it just prevents the flow from firing, or fires it for the wrong people. The most common critical findings in this category: trigger filters set as flow filters (or vice versa), Smart Sending enabled on high-priority flows, and back-in-stock flows firing for warehouse transfers rather than genuine restocks.

Flow filter is a condition evaluated continuously throughout the flow — if a subscriber no longer meets it, they exit. Trigger filter is a condition evaluated only at entry — it determines who gets in, but once someone is in, they stay regardless of what happens next.

Getting these backwards is one of the most common silent revenue leaks we find. A cart abandonment flow where the "placed order" condition is set as a flow filter instead of a trigger filter will eject customers mid-sequence the moment they buy — which sounds right, but causes timing conflicts that result in zero follow-up emails for a segment of buyers. Set it as a trigger filter and the flow re-evaluates correctly on exit.

Architecture Checklist — Critical Items

• Trigger logic: Is the trigger event the most specific available? ("Started Checkout" is more specific than "Added to Cart" for checkout abandonment — use it.)
• Filter placement: Are exit conditions ("Placed Order," "Unsubscribed") set as flow filters, not trigger filters?
• Smart Sending: Is Smart Sending disabled on all abandonment flows and the welcome flow? Smart Sending on a cart abandonment flow suppresses the email if the subscriber received anything in the last X hours — including a campaign send. This is one of the most common configuration errors we see.
• Frequency caps: Does each flow have an entry frequency cap? A cart abandonment flow with no cap will re-enroll the same person every time they abandon, regardless of whether they've been through the flow recently.
• Back-in-stock trigger: Is the BIS flow triggered specifically by customer-facing restock events, not inventory adjustments? In Shopify-Klaviyo integrations, warehouse transfers can fire inventory events that trigger BIS flows for contacts who never expressed interest in the product.
• Flow hierarchy: Are higher-priority flows suppressing lower-priority ones? A subscriber in Cart Abandonment should not simultaneously enter Browse Abandonment. Without suppression logic, you're competing with yourself.
• Exclusion lists: Are recent purchasers, unsubscribers, and hard-bounce profiles explicitly excluded from flow entry?

Work through every active flow in Klaviyo against this list before moving to content. A beautifully written cart abandonment email that never sends because Smart Sending is blocking it is worth exactly nothing.

Not sure if your flow architecture has silent errors? We run 125-point lifecycle audits for DTC brands every week — you'll get a scored breakdown of exactly where your program is leaking revenue. Get your free audit →

Does Your Flow Content Actually Convert?

Content audits have two failure modes: emails that are too generic to earn a click, and emails that are well-written but misaligned with where the subscriber is in their decision. The fix for the first is specificity. The fix for the second is mapping each email's purpose to its position in the flow — a cart abandonment Email 1 should remove friction, not tell your brand story.

Run through each email in each flow and ask one question: does this email do one thing well, or does it try to do three things at once?

Content Checklist — Critical and High-Priority Items

• Email 1 of every abandonment flow: Is the primary CTA a direct return path — a single link back to the cart, checkout, or product page? Not a "shop our collection" button. The specific product.
• Dynamic product blocks: Are the abandoned or viewed products rendering correctly with live inventory? Out-of-stock products showing in abandonment emails is a conversion killer and a list quality signal.
• Welcome flow offer delivery: Is the welcome offer in Email 1 prominent — above the fold, clearly readable, with an expiration? A buried or undated welcome offer loses urgency within 24 hours.
• Post-purchase flow: Is there any selling in the first two post-purchase emails? There shouldn't be. In our experience, the first two emails should focus on order confirmation and brand education — we typically recommend holding cross-sell until at least the second week post-purchase, once the customer has received their order and had time to form an impression of the brand.
• Subject line alignment: Does each email's body deliver what the subject line promised? Curiosity-gap subject lines that don't pay off train subscribers to stop opening.
• Preview text: Is every email's preview text manually set, or is it pulling "View this email in your browser" from the template header? This costs opens every single send.
• Mobile rendering: Are CTAs full-width and tap-friendly (minimum 44px height) on mobile? Are hero images under 200KB? Are font sizes 14px or above in body copy?

Is Your Segmentation Creating Revenue or Creating Noise?

Segmentation errors in flows fall into two types: flows firing for the wrong people (too broad), and flows never reaching the right people because entry conditions are too narrow. The most expensive version of the first type: a winback flow with no minimum purchase requirement that enrolls non-buyers who've never been "won" in the first place.

Segmentation is the practice of dividing your subscriber list into groups based on behavior, purchase history, or engagement level, then sending each group a different message or flow.

Segmentation Checklist Items

• Winback trigger: Does the winback flow require at least one historical purchase before entry? Winback flows that target all lapsed subscribers — including those who've never bought — send "we miss you" emails to people who were never customers. This inflates flow size and dilutes deliverability signals.
• VIP exclusion from discount flows: Are VIP customers (3+ orders, or top tier by revenue) excluded from discount-heavy sequences? Sending your best customers frequent discount codes trains them to wait for promotions instead of buying at full price.
• Browse abandonment minimum threshold: Is browse abandonment triggering on 2+ product views or 60+ seconds on a product page — not a single 5-second visit? Single-page bounces shouldn't enter a marketing flow.
• Dynamic content blocks: Are personalization variables (first name, product name, variant) tested for null states? A broken merge tag that renders as "Hi ," or shows the raw variable name is worse than no personalization at all.
• Engagement-based splits: Do long flows (6+ emails) include conditional splits that route non-openers to a shorter, higher-urgency path? A subscriber who hasn't opened emails 1–3 of your welcome flow needs a different email 4 than someone who opened all three.

Which Technical Audit Items Is Nobody Actually Checking?

Technical audit items don't show up as obvious failures. They show up as slow degradation — a deliverability score that drifts down quarter over quarter, open rates that slide 3–4 points and never recover, flows that "work" but underperform against benchmarks for no obvious reason. These items take 30 minutes to check and are almost never checked.

Technical Checklist — Critical Items

• Authentication stack: Are SPF, DKIM, and DMARC records properly configured on your sending subdomain? Google and Yahoo enforced these requirements for bulk senders in February 2024. Non-compliance means your emails are being throttled or sent to spam at two providers that represent the majority of most DTC lists. According to Google's official announcement, bulk senders must meet these authentication requirements or face delivery consequences.
• Klaviyo attribution window: What is your account's attribution window set to? The default is 5-day click / 5-day open. Many brands have this set to 30-day open — which inflates flow revenue reporting significantly by attributing purchases to emails that had no meaningful role in the conversion decision.
• Smart Sending review: (Repeat from architecture — this one is critical enough to check twice.) Check every flow. Smart Sending is enabled by default in Klaviyo. If you built a flow without explicitly disabling it, it may be blocking emails.
• Sunset flow: Does a sunset flow exist? A sunset flow is an automated sequence that identifies subscribers with no clicks in 90–120 days, attempts a final re-engagement, and suppresses non-responders. Without one, your list accumulates dead weight that drags down your sender reputation for everyone. This is the single most commonly missing flow in programs we audit.
• Shopify-Klaviyo integration events: Are custom events from Shopify ("Placed Order," "Fulfilled Order," "Cancelled Order") syncing correctly and firing flows at the right moments? Integration event misfires are common after Shopify app updates and are rarely caught without explicit monitoring.
• Suppression list integrity: Are hard bounces, unsubscribers, and manually suppressed profiles excluded from all flows? Klaviyo handles this automatically for compliant sends, but custom flow configurations can sometimes bypass global suppression — worth a manual check.

In our experience auditing DTC retention programs, the sunset flow is the most commonly missing element — and its absence creates a compounding deliverability problem that hurts every other flow and campaign in the program.

What Are Good Benchmarks for Email Flow Performance?

Flow benchmarks vary significantly by flow type. A welcome flow and a winback flow should not be held to the same open rate standard — they reach subscribers at completely different points in the relationship. The most useful benchmark framework defines a "passing" threshold for each flow type, so you know whether an underperforming number is a real problem or a category baseline.

Here are the benchmark ranges we use to evaluate flow performance, drawn from Blossom's DTC benchmark data across client programs. Use these as the pass/fail thresholds for your performance audit category.

Welcome Flow Benchmarks

• Open rate: results that vary by program (below performance that shifts with your audience is a deliverability flag, not just a content problem)
• Click rate: numbers that depend on your setup
• Conversion rate (subscriber to first purchase): performance that shifts with your audience
• Revenue per recipient (RPR): $3–8 according to Blossom's benchmark data

Cart Abandonment Flow Benchmarks

• Open rate: figures that differ across accounts
• Click rate: outcomes tied to your specific list
• Conversion rate: results that vary by program
• RPR: $5–15 according to Blossom's benchmark data

Browse Abandonment Flow Benchmarks

• Open rate: numbers that depend on your setup
• Click rate: performance that shifts with your audience
• Conversion rate: figures that differ across accounts
• RPR: $1–4 according to Blossom's benchmark data

Post-Purchase Flow Benchmarks

• Open rate: outcomes tied to your specific list
• Cross-sell click rate: results that vary by program
• Review submission rate: numbers that depend on your setup
• Repeat purchase rate (60-day): performance that shifts with your audience

Winback Flow Benchmarks

• Open rate: figures that differ across accounts (lower is expected — this is a cold audience)
• Re-engagement rate (any click): outcomes tied to your specific list
• Conversion rate: results that vary by program
• RPR: $2–6 according to Blossom's benchmark data

One critical note on open rates: since Apple launched Mail Privacy Protection, Apple Mail pre-fetches email content and inflates open rates for Apple Mail users. Open rate is now an unreliable absolute metric — use it directionally for comparison between sends, but build your engagement segments and sunset triggers around click-based activity, not opens. If a flow's open rate looks suspiciously high and click rate is flat, Apple MPP is likely distorting the picture. Litmus has documented how Apple MPP affects open rate measurement in detail.

Revenue per recipient (RPR) is the average revenue generated per email delivered in a flow, calculated by dividing total flow revenue by the number of emails sent. It's a more honest performance metric than conversion rate alone because it accounts for both conversion volume and order value. It's what we use as the primary scorecard metric across flows.

See how your flows stack up against these benchmarks. We'll run the full 125-point audit and show you exactly where your program is underperforming — and what the revenue impact is. Get your free audit →

How Often Should You Audit Your Email Flows?

Run a full flow audit quarterly and a lighter performance check monthly. Quarterly audits catch configuration drift — flows that were correctly set up but have broken over time due to platform updates, integration changes, or list growth. Monthly performance checks catch metric degradation before it becomes a revenue problem.

Three events should also trigger an immediate audit regardless of schedule:

1. A Shopify app update that touches your product catalog, customer data, or checkout flow — these frequently cause Klaviyo integration event misfires that you won't notice until you check.
2. Any ESP-side change: new sending domain, authentication update, or Klaviyo account configuration change.
3. A deliverability event: spam complaint spike, significant open rate drop, or a Gmail Postmaster Tools alert.

The update trigger is what most brands miss. A flow that passed your audit six months ago may have a broken trigger today because a Shopify update changed how the "Placed Order" event fires. Regular monthly checks are what catch these before they compound.

What Does a Mature Email Testing Program Look Like?

The testing audit category has one primary question: are you running tests that produce decisions, or running tests that produce data nobody acts on? The difference is a defined winner metric, a minimum runtime, and a documented process for locking winners and moving on. Most brands have the first two and skip the third.

Testing Checklist Items

• Active tests: Does each core flow (welcome, cart abandonment, post-purchase) have at least one active A/B test running?
• Winner metric: Is the winner metric RPR or placed order rate — not open rate? Open-rate-based test winners tell you which subject line gets clicked. RPR-based winners tell you which email makes money.
• Sample size: Do active tests have sufficient sample sizes before a winner is called? In our experience, calling a winner at 50 sends per variant produces false results — we typically recommend waiting for at least 500 sends per variant and a 30-day runtime before drawing conclusions.
• Winner implementation: Is there a documented process for locking winners as the new control? Tests that run, produce a winner, and are then ignored (leaving both variants running indefinitely) don't compound. They just collect data.
• Test isolation: Are tests changing one variable at a time? A test that changes subject line, send timing, and offer simultaneously tells you nothing actionable when one variant wins.
• Testing priority: Are you testing in the right order? Subject lines and send timing first (fastest to test, biggest open rate impact), then content format and offer type, then advanced personalization. Testing personalization before you've optimized timing is working on the wrong layer.

How Do You Triage Your Audit Findings?

A 125-point checklist without a triage system is a homework assignment. The output of a real audit is a prioritized list of 5–10 findings organized by severity, not a spreadsheet with 80 items checked and 45 flagged. Severity tiers: Critical (fix this week), High (fix this month), Optimization (queue for testing).

Here's how to assign severity:

1. Critical: Flow is not firing, firing for the wrong people, or actively suppressing emails that should send. Examples: Smart Sending on cart abandonment, broken trigger filter, no sunset flow causing deliverability degradation. These have immediate, measurable revenue impact. Fix within 7 days.
2. High: Flow exists and fires correctly, but performance is significantly below benchmark, or a structural gap (missing a core flow entirely) is leaving money on the table. Examples: welcome flow with no expiration on the offer, missing post-purchase cross-sell sequence, open rate below threshold. Fix within 30 days.
3. Optimization: Flow is performing within benchmark but has a testable improvement opportunity. Examples: subject line hasn't been A/B tested, SMS not integrated, dynamic product blocks not personalized. Queue for the testing calendar.

After your audit, you should have no more than 5 Critical items, no more than 10 High items, and a testing backlog for Optimization. If you have 40 things flagged with equal priority, you don't have an action plan — you have a list.

For most DTC brands doing a first-pass audit, the Critical tier looks like this: a missing or broken sunset flow, Smart Sending enabled on abandonment flows, a misconfigured attribution window inflating performance metrics, and a welcome flow with no offer expiration. Fix those four things and you've addressed the highest-leverage issues before touching anything else.

For more on fixing what the audit surfaces, see our guides on welcome flow setup and structure, cart abandonment flow architecture, and post-purchase flow architecture — each one covers the specific configuration and content decisions that move performance within that flow type.

Key Takeaways

• A real email flow audit has six categories. Most brands only review content and basic metrics — the highest-leverage items (trigger logic, segmentation errors, deliverability configuration) go unchecked.
• Every metric-based checklist item needs a threshold. "Check your open rate" is useless without knowing that a welcome flow below benchmark is a deliverability flag, not just a copywriting problem.
• Flow logic and trigger errors are silent revenue leaks. Smart Sending on cart abandonment, trigger filter vs. flow filter confusion, and broken Shopify integration events don't announce themselves — they just quietly prevent revenue from happening.
• Triage your findings by severity. Five critical fixes done this week will produce more revenue than 40 medium-priority items worked on simultaneously over three months.
• The sunset flow is always missing. Build it first if you don't have one — the deliverability protection it provides makes every other flow and campaign perform better.

Run through the checklist, assign severity, fix Critical items first. If you finish the audit and the action plan feels overwhelming, that's a good sign you found the real problems. The brands whose programs grow consistently are the ones who audit systematically, triage ruthlessly, and test everything they change.

If you want help running this process — or want someone who's done it 50+ times to run it for you — that's exactly what our free lifecycle audit is. Book a strategy call and we'll map out your next 90 days of retention revenue →

FAQ

How do you audit email flows in Klaviyo?

Open each active flow and work through six categories in order: trigger configuration, flow filter vs. trigger filter logic, Smart Sending settings, content alignment, segmentation accuracy, and performance against benchmark thresholds. Start with architecture before content — a perfectly written email in a broken flow is still broken.

What should I look for in an email flow audit?

The highest-leverage items to check are: Smart Sending enabled on abandonment flows, trigger filters misset as flow filters, missing sunset flow, attribution window configuration in Klaviyo settings, and RPR performance against benchmark ranges by flow type. These cause more revenue loss than weak copy and are caught far less often.

How often should you audit your email flows?

Run a full audit quarterly and a lighter performance check monthly. Trigger an immediate audit after any Shopify app update that touches customer data, after any ESP configuration change, or when you see a sudden drop in open rates, click rates, or deliverability metrics in Google Postmaster Tools.

What is a good open rate for Klaviyo flows?

Benchmark thresholds vary by flow type. Based on Blossom's benchmark data across DTC client programs, welcome flows tend to perform in the 50–65% open rate range, cart abandonment flows in the 40–55% range, and winback flows in the 20–35% range — lower is expected given the cold audience. Below 35% on a welcome flow is a deliverability signal, not just a content problem. Note that Apple Mail Privacy Protection inflates open rates for Apple Mail users — use click rate as your primary engagement signal for segmentation and sunset decisions.

What metrics should I track in an email flow audit?

Track RPR (revenue per recipient) as your primary metric — it accounts for both volume and order value. Supplement with placed order rate, click rate, and flow-level conversion rate. Open rate is useful directionally but unreliable as an absolute measure given Apple Mail Privacy Protection's impact on measurement. Also check your Klaviyo attribution window setting — the default 5-day open window may be significantly inflating or deflating reported performance depending on your account configuration.

Get tactics like this in your inbox every week. Subscribe to our newsletter →