Webclat / Klaviyo Practice
Webclat / Klaviyo Practice  /  measurement

Klaviyo attribution: what it claims vs. what your analytics says

Klaviyo's dashboard will tell you exactly how much revenue email and SMS drove. GA4 and your ad platforms will each tell you a different number for the same period. None of them is lying - they're running different attribution models against overlapping but not identical data. Reconciling them, or deciding which one to report on, is the job.

Why the numbers disagree

Source of disagreementWhat it does
Attribution windowKlaviyo's default click/view windows differ from GA4's session-based model, crediting a wider or narrower time range to the same touch
Channel deduplicationA single order can be credited in full to email by Klaviyo and in full to paid social by your ad platform - both models can "win" the same order
Event completenessIf checkout/order events are incomplete (see our integration guide), Klaviyo's attributed revenue undercounts regardless of the model
Last-click vs. multi-touchKlaviyo's native reporting is last-click by default; GA4 can be configured for data-driven or other multi-touch models

None of these are bugs. They're different, legitimate ways of answering "what drove this order" - the mistake is comparing the outputs of two different models and assuming one of them is wrong.

How we approach reconciliation

  • Document the exact attribution window and model each tool is currently using.
  • Verify event completeness feeding Klaviyo's revenue calculation (see the integration guide for common gaps).
  • Build a side-by-side reconciliation for a defined period so stakeholders see where and why the numbers diverge, in dollars, not just in theory.
  • Recommend either a standardized model across tools or an explicit "here's what each number means" reporting note - whichever fits how your team actually uses the data.

Related coverage

For the ecommerce-attribution side of this problem across your full stack (not just Klaviyo), see ecomm.webclat.com's use case on measuring what Klaviyo really brings and its ecommerce attribution guide. This page covers the Klaviyo-specific half of that reconciliation.

Common questions

Why does Klaviyo show more revenue than GA4?

Most often because Klaviyo's default attribution window (commonly 5 days click / 1 day view, though this is configurable) is wider than GA4's model, or because Klaviyo counts revenue from any email/SMS-attributed order without the cross-channel deduplication a multi-touch model would apply.

Should I trust Klaviyo's revenue number or GA4's?

Neither is automatically "correct" - each measures attribution under a different model and window. The useful step is understanding what each model actually credits, then deciding which one (or which blended view) your team reports on, rather than treating either as ground truth by default.

Can Klaviyo's attribution window be changed?

Yes, Klaviyo allows configuring the attribution window in account settings. Changing it will change reported revenue going forward and should be done deliberately, with the change date noted for anyone comparing historical reports.

Do you fix the attribution model itself?

We diagnose where the disagreement comes from - window settings, event completeness, cross-channel double-counting - and recommend a reconciliation approach. Whether to standardize on one model or report both is a decision for whoever owns your analytics stack.

Get a side-by-side reconciliation, in dollars.

Klaviyo vs. GA4 vs. ad-platform revenue for a defined period, with the source of every gap documented.

Reconcile My Revenue Numbers