[deliver]
Deliver article · 2026-07-16 · Charlotte Rodrigues

Email marketing attribution: a practical ecommerce model

Short answer. Use three layers. Klaviyo measures message-level performance inside its attribution rules. Your web analytics tool measures tagged sessions and cross-channel journeys. The ecommerce platform is the ledger for orders and refunds. Reconcile all three, but use randomized holdouts or incrementality tests when you need to know whether email caused additional revenue.

Attribution is a rule for assigning credit. It is not the same as causation. A customer may click an email, return through a branded search, and buy. Klaviyo, GA4, and the store can all report a different version of that journey without any system being technically broken.

The mistake is expecting one number to answer every question.

Start with the decision, not the tool

Question Best primary view Why
Which subject and message variant performed better? ESP experiment report Same channel and randomized variants
Which flow message creates attributed orders? Klaviyo message report Message-level conversion tracking
Which sessions arrived through email links? GA4 or another analytics tool UTM-based session reporting
What did the store actually book and refund? Shopify or ecommerce ledger Order system of record
Did email create revenue that would not happen otherwise? Randomized holdout Measures incremental lift
How should budget be split across channels? Blended model plus experiments No platform can grade itself alone

This framework prevents two common errors: treating the lowest web-analytics number as truth, or treating the highest platform number as truth.

How Klaviyo message attribution works

Klaviyo credits conversions that happen after a recipient receives and interacts with an eligible message inside the account's configured window. The selected conversion metric is often Placed Order, but Klaviyo can report other conversion events.

Klaviyo's current conversion tracking documentation says that accounts created after October 9, 2024 default to a 5-day window for email and SMS and 24 hours for push. Settings are adjustable. Do not copy a window from an article into your dashboard without checking the live account.

The model can also be configured to remove bot clicks and Apple Privacy opens from attribution. Record those choices because a settings change can move reported revenue without any customer behavior changing.

What platform attribution is good for

What it cannot prove by itself

Why GA4 reports less email revenue

Web analytics usually depends on a tracked visit. A recipient can read an email, remember the product, return through another device or channel, and buy without an email-tagged session receiving credit. Consent, browser restrictions, redirects, and cross-device behavior can also break the visible chain.

That does not make GA4 useless. It makes it a different lens. Use consistent UTM parameters on every campaign and flow link. Klaviyo can append source, medium, campaign, and optional identifiers at the account and message level.

A practical naming standard might be:

Parameter Campaign example Flow example
utm_source klaviyo klaviyo
utm_medium email email
utm_campaign 2026-07-summer-launch welcome-series
utm_content hero-cta-control email-02-proof

Do not put personal data in UTM parameters. Keep names stable enough to group across periods.

Why store revenue is the financial baseline

The ecommerce platform records orders, discounts, taxes, shipping, cancellations, and refunds. It is the appropriate starting point for total revenue, but it does not know every influence that preceded the order.

Reconcile platform-attributed revenue to store revenue at the order level when possible. Check:

Klaviyo's analytics documentation notes that dashboard revenue can be associated with the date the first message was sent rather than the day the order occurred. That is another reason daily store and messaging charts may not align.

A four-level attribution model

Level 1: operational message attribution

Use the ESP for day-to-day optimization. Keep the conversion metric and windows documented. Compare like with like: campaign to campaign, welcome message to welcome message, and the same segment over time.

Level 2: session and path analysis

Use web analytics to understand landing pages, tagged sessions, assisted paths, and onsite behavior. This layer is particularly useful for diagnosing a high click rate with a low checkout rate.

Level 3: blended business reporting

Build a monthly table that starts with store revenue and adds channel spend, platform-attributed revenue, tagged-session revenue, new customers, repeat customers, and contribution margin. Do not sum platform claims across channels because the same order may be claimed more than once.

Level 4: incrementality

Randomly withhold a representative eligible group from a campaign or flow, then compare outcomes over a predefined window.

Incremental lift = outcome rate exposed - outcome rate holdout

Incremental revenue = incremental outcome rate x eligible population x average net order value

For a flow, preserve the holdout long enough to cover the expected purchase cycle. For a major campaign, define the outcome and analysis window before the send. Do not remove the holdout early because the initial chart looks favorable.

Last click, first click, and multi-touch

Model Strength Main weakness
Last click Simple and useful for lower-funnel execution Overcredits the final interaction
First click Highlights discovery Ignores conversion work later in the path
Linear multi-touch Shows that several contacts occurred Gives equal credit without evidence
Time decay Favors recent contacts Choice of decay is subjective
Data-driven Can reflect complex patterns at scale Harder to explain and still observational
Randomized holdout Estimates causal lift Requires enough volume and disciplined setup

Multi-touch reporting can describe a journey better than last click, but it does not automatically become causal. A sophisticated allocation rule is still a rule.

How to audit an ecommerce attribution setup

  1. Name the business question. Message optimization, channel reporting, and incrementality require different methods.
  2. Inventory conversion events. Confirm the store's Placed Order event, value, currency, and unique order ID.
  3. Document Klaviyo settings. Capture windows, interaction rules, Apple privacy treatment, bot-click treatment, and conversion metric.
  4. Standardize UTMs. Use one source and medium taxonomy across campaigns and flows.
  5. Reconcile a sample of orders. Trace a small group through Klaviyo, analytics, and the store.
  6. Account for returns. Decide whether reporting uses gross, net, or contribution revenue.
  7. Separate new and repeat buyers. The same attributed dollar can have a different strategic value.
  8. Add a holdout. Test at least one high-volume campaign or flow where the decision matters.
  9. Freeze definitions. Do not change settings mid-period without annotating the report.

Common attribution mistakes

Adding every platform's revenue

Meta, Google, Klaviyo, affiliates, and SMS can claim the same order. Their totals are not additive. Start with store revenue and use platform views for optimization inside each channel.

Optimizing only to click-attributed revenue

This penalizes education and longer consideration cycles. Use holdouts and cohort outcomes for messages designed to influence a later purchase.

Using opens as proof of influence

Apple Mail Privacy Protection can load tracking pixels without a person reading the email. Exclude Apple privacy opens from attribution where appropriate and do not build causal claims on opens.

Changing windows to make the number look better

A longer window usually increases credited revenue. Choose windows based on the decision and buying cycle, then keep them stable. Preview the impact of changes before applying them.

Ignoring margins and refunds

Attributed gross revenue can reward discount-heavy messages that create weak contribution. Add net revenue, discount cost, refunds, and margin when comparing commercial strategies.

A monthly reconciliation table

Field Source Purpose
Net store revenue Ecommerce platform Financial denominator
Email-attributed revenue Klaviyo Message optimization
Email tagged-session revenue GA4 Visit and landing-page analysis
Flow and campaign split Klaviyo Program allocation
New and repeat customers Store Customer mix
Refunds and discounts Store Profit adjustment
Holdout lift Experiment Incremental impact

Add notes for launches, stockouts, site outages, attribution setting changes, and unusual promotions. Context prevents teams from turning seasonality into a false lesson.

FAQ

Does Klaviyo overattribute email revenue?

It can overcredit orders that would have happened anyway, but it can also miss influence outside its window or without a qualifying interaction. The direction and size depend on settings and customer behavior. Use a holdout to estimate incrementality.

What attribution window should I use?

There is no universal window. Start from the purchase cycle and the decision being measured. Check the account's current defaults and preview how a change affects historical reporting before applying it.

Why do Klaviyo and GA4 disagree?

They use different identity, interaction, window, and channel rules. Klaviyo sees eligible message activity; GA4 sees tagged and consented web sessions. Reconcile definitions instead of forcing the totals to match.

Is multi-touch attribution better than last click?

It can describe complex paths more fully, but the credit allocation remains observational. For investment decisions, combine it with controlled experiments.

How often should attribution be audited?

Review operational consistency monthly and perform a deeper audit after a platform migration, store integration change, consent update, or major attribution setting change.

Build a model the team can explain

The best attribution model is not the one with the highest email number. It is the one whose definitions, limits, and decisions everyone can explain. Deliver helps ecommerce teams connect tracking, lifecycle strategy, and incrementality. Book an email and CRM diagnostic.

CR
Charlotte Rodrigues · CRM Lead at Deliver. Questions about this article? charlotte@agence-deliver.com

Want to apply this to your stack?

Spend 30 minutes with Charlotte to review your CRM setup, size the opportunity and leave with a practical action plan.

Book a 30-minute call →