This is one of the most common situations we walk into: a Klaviyo account with all the right flows built, decent open rates, no obvious red flags, and revenue that’s quietly flatlined anyway. Nothing looks broken. Something still is.
Why does the dashboard look fine? Because open rates, click rates, even total email revenue at a glance can all look reasonable while revenue per recipient, the number that actually matters, has been declining for months. Almost nobody checks that number directly, because everything around it looks healthy enough that nobody thinks to dig deeper.
Where does the list problem hide? Accounts running a year or more often carry a large chunk of subscribers who haven’t engaged in 90-plus days, sometimes far longer. That segment doesn’t show up as a problem in your overall stats. It just drags down your averages and your sender reputation while looking like normal list size.
What about the flows themselves? An account can have all five core flows technically live and firing while the content inside them, discount codes, product recommendations, timing, has gone stale relative to what the brand and its customers look like today. The flow still runs. It’s just running on assumptions that were accurate a year or two ago.
And segmentation? Many accounts still send the same message to every subscriber regardless of purchase history, engagement, or how they found the brand. That’s invisible in a dashboard showing only aggregate numbers. It only becomes visible once you segment your reporting the same way you should be segmenting your sends.
None of this surfaces from a glance at your Klaviyo homepage. It surfaces from opening each flow individually, checking revenue per recipient over time, checking engagement percentages, and checking whether your segmentation still matches your actual customer base. Looking fine and performing well are not always the same account.
Want More Breakdowns Like This?
Every week, Inbox Insider breaks down one real Klaviyo account, what is working, what is leaking revenue, and exactly how to fix it.
