How to fix Klaviyo attribution with Triple Whale (and when to trust which number)
Klaviyo and Triple Whale report different revenue. Here's how to reconcile these klaviyo integrations, align attribution windows, and use the right number.

You've seen this before. Klaviyo says email drove $48,000 last month. Triple Whale says $22,000. Someone needs a number for the channel report and nobody agrees on which one to use.
This is the attribution problem that most klaviyo integrations create quietly. Both tools are measuring real things. Neither is lying. They're just measuring different things with different rules, and few teams take the time to configure them to work together properly.
This guide walks through the fix: understanding why the numbers diverge, how to configure the integration correctly, how to align attribution windows, and how to decide which number belongs in which report. No single configuration will make both tools report identical numbers, but you can get them close enough to be useful, and know exactly what the remaining gap means.
Step 1: understand what each tool is actually measuring
Before changing any settings, get clear on what's happening under the hood.
Klaviyo attributes revenue using a time-window model. The default is 5 days for clicks, 1 day for opens. When someone clicks an email and buys within that window, Klaviyo claims the order. This applies to every campaign and every flow, running continuously in the background.
Triple Whale uses pixel-based attribution. It was built primarily for paid media teams who need a cross-channel view. It pulls in Klaviyo send, open, and click data from the integration, then reconciles email-assisted revenue against what its own pixel tracked. Its default model is last-touch click, which is much tighter than Klaviyo's default.
The result is two numbers that answer two different questions. Klaviyo asks: 'did this person buy within X days of clicking my email?' Triple Whale asks: 'given everything the pixel saw across all channels, what should get credit for this purchase?'
A pattern that comes up often: brands running heavy win-back flows will see Klaviyo attribution spike whenever paid spend drops. Organic traffic picks up, lapsed customers return, Klaviyo claims the revenue. Triple Whale, watching the paid ecosystem, shows low email contribution. Both numbers are technically accurate. They're not comparable.
That distinction matters before you touch a single setting. Understanding the measurement difference is what tells you which setting to change and why.
Step 2: set up klaviyo integrations in Triple Whale correctly
In Triple Whale, go to Settings > Integrations > Klaviyo. You'll need your Klaviyo API key (the public key is enough for read access). Triple Whale uses this to pull campaign-level and flow-level send data.
What the integration actually syncs:
- Campaign names and send dates
- Aggregate open and click rates
- Revenue data as reported by Klaviyo, which is what Klaviyo claims, not what Triple Whale independently verifies
It does NOT sync individual contact-level purchase records. Triple Whale uses its own pixel to track actual orders, then maps those against Klaviyo activity through email address matching.
A few things that break this matching in practice.
If your Shopify store has customers with multiple email addresses (loyalty programs, referral apps, or headless checkout flows where guest emails differ), the matching fails silently. You'll see a gap in Triple Whale's email revenue that doesn't exist in Klaviyo. That's a data quality problem, not a bug in either tool.
If you've disabled Klaviyo's open tracking, Triple Whale won't have open data. That's fine. But make sure Klaviyo's attribution model is set to click-only before comparing numbers. Open-assisted attribution on Klaviyo's side with no open data on Triple Whale's side creates a guaranteed mismatch that no amount of window-aligning will fix.
Klaviyo's attribution documentation explains exactly how orders get assigned when a contact qualifies under multiple flows or campaigns simultaneously. Worth reading if you're seeing unusual overlap between campaigns.
A clean integration setup removes most of the structural causes of disagreement between the two tools.
Step 3: align attribution windows
This is where most teams get burned, and it's the most fixable problem of the bunch.
Klaviyo defaults to 5-day click / 1-day open. Triple Whale defaults to 1-day click, last-touch. These aren't the same model. Comparing reports without accounting for this is comparing apples to a different fruit entirely.
You have two realistic options.
Option A: tighten Klaviyo to match Triple Whale
Go to Settings > Attribution in Klaviyo and change to 1-day click only. Your reported revenue will drop noticeably. That's the point. You want a number that can sit next to Triple Whale's in the same report.
Option B: extend Triple Whale's email window to match Klaviyo
In Triple Whale's channel settings, change the email click window to 5 days. This inflates Triple Whale's email number but makes it closer to what Klaviyo reports. Some teams prefer this because it keeps Klaviyo's historical data intact.
I'd recommend Option A. The 5-day window is generous. Someone who clicked an email on Monday and bought on Friday didn't necessarily buy because of the email. Tighter windows reduce false positives and give you cleaner data for incrementality analysis. When you're trying to decide whether to invest more in email or shift budget elsewhere, artificially inflated numbers work against you.
One practical warning: changing Klaviyo's attribution window mid-period makes historical comparisons unreliable. Make the change at the start of a month and document the exact date. Your before/after numbers will look like different programs even if nothing else changed.
Matching windows is the single most impactful configuration change for closing the gap between the two tools.
Step 4: build a reconciliation baseline
After aligning windows, you'll still see differences. Some gap is expected and normal. Run this exercise once to understand what's driving it.
Export from Klaviyo: Revenue by campaign and flow from Analytics > Overview. Use a 30-day window.
Export from Triple Whale: Channel breakdown showing email revenue from the Summary view. Same 30-day window.
Calculate the ratio: Klaviyo number divided by Triple Whale number. For most brands, this lands between 1.5x and 3x in Klaviyo's favor. That range is normal given the structural differences in how the tools attribute.
If the ratio is above 3x, something structural is wrong. Either the Klaviyo pixel isn't firing on order confirmation pages, attribution windows are still misaligned, or you have the email address matching issue described earlier. Start with pixel verification before changing anything else.
If the ratio is below 1.5x, your setup is probably in good shape. But check whether Triple Whale is double-counting email in its 'blended' view before declaring victory.
One more check worth doing: compare individual campaigns in both tools, not just totals. If one campaign shows a 5x difference while others sit at 1.8x, that's meaningful information. It usually means the campaign went to a high-intent segment (past purchasers, loyalty customers) that was already planning to buy. Klaviyo claims the revenue. Triple Whale, seeing minimal paid signal, discounts it. This isn't a configuration error. It's data about incrementality, and it's worth knowing.
This baseline ratio is what you'll reference every month to distinguish normal variation from real problems.
Step 5: decide which number goes in which report
This is the part most attribution guides skip, and it's where bad decisions actually happen.
Use Klaviyo's number when you're evaluating internal email performance. Which subject line won. Which flow sequence converts better. Which segment responds to which message type. For these decisions, you're comparing email to email, and Klaviyo's attribution, even with a generous window, gives you a consistent lens. The Klaviyo metrics that actually matter guide covers which internal numbers deserve attention and which ones are just vanity.
Use Triple Whale's number when you're doing budget allocation across channels. If the decision is email vs. paid social, you need a cross-channel view with consistent attribution rules. Triple Whale gives that. Using Klaviyo's number in a channel comparison will consistently overstate email contribution and lead your paid team to underspend.
If you're working with an external media buyer or agency, this matters a lot. Handing them Klaviyo's $48K when Triple Whale shows $22K, without explanation, causes them to throttle paid spend based on inflated email numbers. The article on using Klaviyo data to brief your paid media agency covers how to frame attribution data for teams that live in Triple Whale.
For internal reporting, I'd show both numbers with the ratio visible. 'Klaviyo: $48K. Triple Whale: $22K. Our standard ratio: 2.1x. This period: 2.2x, consistent with baseline.' That framing turns a confusing discrepancy into a health signal instead of a fight.
The right number depends on the decision you're making, not on which tool you prefer.
Step 6: monitor the ratio over time
Attribution drift is real. The ratio you establish today won't stay fixed, and you want to catch shifts before they compound in your reporting.
If your ratio widens (Klaviyo claims more relative to Triple Whale), the most common causes are: a new flow targeting a high-intent segment, a drop in paid spend that shifts Triple Whale's channel weighting, or a tracking gap where the Klaviyo pixel fired but Triple Whale's pixel didn't. The last one is worth checking first because it's often invisible until you look.
If the ratio narrows, check whether you've changed Klaviyo's attribution window, shifted toward colder audience targeting, or added a paid channel that Triple Whale is absorbing email revenue into.
Across 20+ Klaviyo accounts, a ratio shift above 0.3x almost always has an identifiable cause. The problem is that most teams don't notice until it shows up in a monthly review, by which point two or three decisions have already been made on unreliable numbers.
If you're managing Klaviyo across multiple stores, tracking these ratios at scale is where something like SPARKCRM becomes useful. The article on reducing Klaviyo firefighting with monitoring and alerts covers how to build the monitoring habits that catch these shifts before they show up in a report.
Review the ratio monthly. Flag any shift above 0.3x. Investigate before it compounds.
When the numbers will never fully agree (and that's fine)
Some brands will never get Klaviyo and Triple Whale to report similar numbers. That's acceptable. Attribution is a model, not reality.
If you're running a content-heavy email program to a warm, loyal list, Klaviyo will always claim more than Triple Whale concedes. If you're running primarily discount campaigns to cold audiences with heavy paid support, the gap might be smaller. Both situations are normal.
What you want to avoid is treating either number as 'the truth' in isolation. The gap between them is information. A widening gap usually means something changed in your channel mix, your segmentation approach, or your tracking setup. A stable gap means your attribution hygiene is holding.
Attribution alignment is not a one-time fix. It's a habit. The teams that get this right review the ratio regularly, investigate outliers, and communicate clearly about which number they're using for which decision. That's what makes cross-channel reporting actually useful.
Reconciliation checklist
- Confirm Klaviyo's attribution window in Settings > Attribution
- Set Triple Whale's email click window to match Klaviyo, or tighten Klaviyo to 1-day click
- Verify the Klaviyo pixel fires on order confirmation pages
- Confirm click-only attribution if open tracking is disabled
- Check email address match rate, flag stores with loyalty or referral apps
- Export 30-day revenue from both tools and calculate your baseline ratio
- Identify campaigns with outlier ratios (above 3x) and investigate the segment targeting
- Align on which number the paid team uses for budget decisions
- Review the ratio monthly, flag any shift above 0.3x, and investigate the cause
Found this article helpful? Share it with others!