Klaviyo + Amazon Attribution

What did Amazon Attribution see from tagged Klaviyo traffic?

Connect Klaviyo and Amazon Attribution to Hendrik. Compare a verified Klaviyo tagged message destination with Amazon Attribution’s separate measurement of Amazon activity.

See Hendrik at work

Klaviyo + Amazon Attribution review

Previous: 1–28 January. Current: 29 January–25 February. Both periods contain 28 days. Monetary values use USD and all timestamps use UTC. This example assumes the named external campaign or message used the specified Amazon Attribution tag. Verify that relationship in your setup.

MetricPreviousCurrent
Klaviyoflow-attributed orders (count, 28 days)310420
Amazon Attributionattributed Amazon sales (USD, 28 days)22,000 USD28,000 USD

What Hendrik checks

  1. Message and audience definition

    Check Klaviyo attribution setting, send volume, audience, exclusions, flow changes, and message window before interpreting attributed value.

  2. Tag and marketplace identity

    Check the Attribution tag, marketplace, attribution window, and the established identity of the external activity.

  3. Explain the divergence

    Klaviyo: flow-attributed orders (count, 28 days) changed from 310 to 420. Amazon Attribution: attributed Amazon sales (USD, 28 days) changed from 22,000 USD to 28,000 USD. Compare the timing and definitions before attributing one change to the other.

About this example Synthetic data · Illustrative analysis · Changes require your approval.

How Hendrik handles your data

Want Hendrik to answer this with your data?

One analysis, different integrations

What each integration adds

Connect your stack

Set up each integration in one workspace.

  1. Create your Hendrik account. Choose a workspace for your business.
  2. Connect your data. Use each integration’s setup instructions above. Availability and permissions are shown in your workspace.
  3. Ask your first question. Hendrik uses the available data and tells you when a comparison needs more history or more data.
Requirements and data limits

What you need

  • Use one explicit 28-day comparison window, time zone, market, and legal-entity scope before comparing values.
  • Connected Klaviyo account with the relevant message, flow, and attribution definitions.
  • Connected Amazon Attribution data with a known tagged destination and attribution window.
  • Keep provider-specific definitions visible and use an identity or product mapping only where it is established for this workspace.

Keep these differences in mind

  • Message attribution is observational and does not show that exposure caused a store, payment, or subscription outcome.
  • Tagged Amazon Attribution results need a real tag, destination, and window; they do not establish shared campaign identity elsewhere.
  • Klaviyo attribution and Amazon Attribution must remain separate measurement programs.

Your data. Your next step.

Put Hendrik to work on your stack.

Create your account, choose your workspace and connect your data.

See plans and pricing