by Trivas.aiScreenshot the Klaviyo dashboard, drop the revenue number into your monthly report, move on. That's how most brands handle email flow reporting, and it's also how most brands end up overstating what their flows actually do. If you're trying to figure out how to measure the revenue impact of email flows in ecommerce, the ESP dashboard is a starting point, not an answer.
That big revenue number in Klaviyo or Mailchimp comes from an attribution window the platform sets, not one you chose. Klaviyo's default is 5 days for clicks and 1 day for views. Anyone who opens an abandoned cart email and buys something four days later, for any reason, gets counted as flow revenue. Doesn't matter if the email actually drove the purchase.
Then there's double counting. A customer clicks your abandoned cart email, doesn't buy, sees a retargeting ad on Instagram the next day, and converts. Meta claims that sale. Klaviyo claims that sale. Your finance team looks at both reports and thinks revenue is higher than it really is, because the same order got credited twice in two different systems that don't talk to each other.
None of this makes flows worthless. It just means the platform's number answers a narrower question than people think it does. The real question, the one this post is built around, is how do you isolate what a flow actually caused versus what it merely touched. Those are two very different numbers, and mixing them up leads to bad decisions about which flows to keep, cut, or rebuild.
Total flow revenue is the least useful metric in this list, mostly because it rewards volume. A welcome flow that hits 500 people a month will never look as impressive as an abandoned cart flow that hits 5,000. Compare them on raw revenue and you'll draw the wrong conclusion every time.
Here's what actually tells you something:
That last one matters more than people give it credit for. If email 4 in a sequence is generating meaningfully less revenue per send than emails 1 through 3, that's your answer on whether to add a fifth email or cut the sequence down.
Last-click attribution gives credit to whatever link someone clicked right before buying. It's the default in most ESPs because it's simple, but it systematically underweights flows that sit earlier in the journey, like a welcome series that builds trust three weeks before someone actually buys.
First-click does the opposite: overweights the very first touch, which can make a single welcome email look like it drove a $200 order that really came down to five other touchpoints along the way. Linear attribution splits credit evenly across every touch, which is more balanced but harder to explain to a founder who wants one number per flow.
There's no perfect model. What matters more is picking one and using it everywhere, your ESP, GA4, your data warehouse, and not switching mid-year. If you swap from last-click to linear in July, your abandoned cart flow will look like it dropped 20% in August. It didn't drop. You just started measuring it differently, and now you're comparing two different rulers and calling it a trend.
Klaviyo will tell you a flow generated $40,000 last month. Shopify might say $34,000 came from those exact order IDs. That gap is real, and it's usually refunds, cancellations, or test orders that never got cleaned out of the ESP's count.
Export your flow-tagged orders and match order IDs against your actual Shopify data. This is tedious the first time and fast every time after, once you've got the process set up.
UTM discipline makes this reconciliation possible in the first place. Every flow email should carry utm_source=klaviyo, utm_medium=email, and utm_campaign= with the specific flow name. Without that, GA4 and Shopify analytics can't independently confirm what the ESP is telling you, and you're stuck trusting one source with no way to check its work.
One thing to flag before it causes a false alarm: ESPs report revenue at the moment of click, Shopify reports it at order completion. A 24-48 hour lag between the two is completely normal. If you're reconciling data daily and the numbers don't match on day one, that's not a discrepancy, that's just timing. Give it two days before you go looking for a bug.
Attributed revenue tells you how much revenue touched a flow. It doesn't tell you how much revenue only exists because that flow ran. For that, you need a holdout group.
The setup is simple. Exclude 5-10% of eligible customers from a specific flow for 30-60 days. Everyone else gets the flow as normal. At the end of the window, compare purchase rates between the two groups.
Say the holdout group converts at 8% and the flow group converts at 14%. The incremental lift is roughly 6 percentage points, not the full 14%. That 8% baseline would have converted anyway, flow or no flow. The 6-point gap is the actual, causal contribution of the flow, and it's almost always smaller than what the attributed revenue number implies.
Run this once a year per major flow (welcome, abandoned cart, post-purchase) and you'll have a much more honest picture of what's driving orders versus what's just getting credit for orders that were happening regardless.
Flow revenue sits in Klaviyo. Ad revenue sits in Meta and Google. Order data sits in Shopify. Keep them siloed and you can't calculate blended CAC, you can't see true channel contribution, and you're stuck stitching together three CSV exports every time someone asks a simple question.
Pulling all three into one warehouse changes what you can actually see. This is the gap Trivas's BI reporting is built to close: flow revenue, paid revenue, and organic revenue on the same timeline, not three separate tabs you're manually cross-referencing at month end.
It's also where teams catch something they'd otherwise miss: a flow that looks great in isolation but is actually cannibalizing campaign revenue. If your post-purchase flow is quietly discounting the same customers your promotional campaigns are targeting, attributed revenue in Klaviyo won't show you that conflict. A blended view will.
A few patterns show up over and over when brands audit their own flow reporting:
Attributed revenue tells you what a flow touched. A holdout test tells you what it caused. You need both, because they answer different questions: one is useful for weekly optimization, the other is useful for deciding whether a flow deserves to exist at all.
Getting there manually, exporting from Klaviyo or Mailchimp, cross-checking Shopify, pulling ad platform data separately, works, but it's slow and easy to get wrong. A reconciled view across Klaviyo, Shopify, and your ad platforms turns a multi-hour reporting task into something you can check in minutes.
If you're a marketing lead trying to make the case for which flows deserve more investment, that kind of view is worth building sooner rather than later. Explore how Trivas connects flow, ad, and order data for marketing leaders, or just start a trial and see what your flow revenue actually looks like once it's reconciled against real order data.
explore more insights
3 min read
3 min read
3 min read
.d53b12e5.png&w=3840&q=75 "Trivas.ai")