Which Klaviyo flow metrics actually tell you something

A flow's total revenue is the easiest number to report and the least useful one to act on. It moves with store traffic, list size and seasonality — none of which have anything to do with whether the flow itself is any good. A handful of other metrics survive those swings. Most reports lead with the wrong one.

Volume metrics vs efficiency metrics

Total attributed revenue is a volume metric: more recipients or more store traffic pushes it up even if the flow's content and timing haven't changed. If a client's ad spend doubles their site traffic this quarter, their welcome flow's total revenue will likely rise too — not because anyone improved the flow, but because more people entered it. Reporting that rise as a win for the flow itself is the kind of claim that doesn't survive a follow-up question.

Revenue per recipient is the one that travels

Divide attributed conversion value by recipients and you get a number that's comparable across periods regardless of list size, and comparable across flows of different sizes within the same account. Worked example: a welcome flow that made $9,800 from 4,200 recipients ($2.33 per recipient) and, the following quarter, $14,100 from 6,800 recipients ($2.07 per recipient) — total revenue went up 44%, but efficiency actually fell. Revenue per recipient catches that; total revenue alone would have reported it as unambiguous growth.

Placed order rate, conversion rate, and what Klaviyo means by each

Klaviyo's flow analytics report placed order rate (the share of recipients who completed a Placed Order event after receiving the message, within the attribution window) alongside conversion rate against whichever metric the flow's reporting is set to track. These aren't interchangeable: a flow's conversion rate can look strong against a lenient custom metric and unremarkable against Placed Order. Always check which metric a rate is measured against before comparing two flows' rates directly (Klaviyo's flow analytics documentation defines each).

Open rate after Apple Mail Privacy Protection

Open rate still appears on every flow report, and it's still worth glancing at for anomalies — a flow whose open rate suddenly drops to near zero usually means a technical problem, not a content problem. But since Apple Mail Privacy Protection began pre-fetching images for a large share of iOS Mail users, open rate has been artificially inflated across the industry and no longer reliably reflects genuine engagement. It's a diagnostic signal, not something to put in a client-facing case study.

Reading a flow-values report

Before drawing a conclusion from an aggregated flow report, check three things: sample size (a flow with 40 recipients in the period can swing wildly on one or two orders), seasonality (a holiday week inflates almost every ecommerce metric regardless of flow quality), and whether the flow's own configuration — trigger, delay, content — changed partway through the window being reported.

The minimum a metric needs before you show it to a client

Three conditions, all of which should hold before a number goes in a report: enough volume that one or two orders don't swing the result, a period comparable to whatever you're comparing it against, and a stable metric definition across both periods. A number that fails any of the three isn't wrong to mention — it just needs a caveat attached, not a headline.