# Klaviyo + Amazon Attribution integration and analysis

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

## The question this stack can answer

What did Amazon Attribution see from tagged Klaviyo traffic?

## What Hendrik reads from each source

- **Klaviyo:** Flows, campaigns, and lifecycle activity show messages, audience changes, and repeat purchase context.
- **Amazon Attribution:** Tagged off Amazon activity shows what Amazon Attribution reports for that tag and destination.

## What you need to connect

- 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.

## Important limits

- 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.

## Illustrative example

### 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.

*About this example: Synthetic data · illustrative analysis · Hendrik only acts with the permissions you give it.*

- flow-attributed orders (count, 28 days) (Klaviyo): 310 → 420
- attributed Amazon sales (USD, 28 days) (Amazon Attribution): 22,000 USD → 28,000 USD

### What Hendrik checks

- **Message and audience definition:** Check Klaviyo attribution setting, send volume, audience, exclusions, flow changes, and message window before interpreting attributed value.
- **Tag and marketplace identity:** Check the Attribution tag, marketplace, attribution window, and the established identity of the external activity.
- **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.

### What Hendrik sees

Klaviyo flow-attributed orders rose. Amazon Attribution attributed Amazon sales rose.

### What to do next

Confirm the message-to-tag relationship before changing a lifecycle program; reassess from the same Attribution configuration.

**Limit:** Klaviyo attribution and Amazon Attribution must remain separate measurement programs.

## Provider documentation

- [Klaviyo documentation](https://help.klaviyo.com/hc/en-us)
- [Amazon Attribution documentation](https://advertising.amazon.com/help/GBT6KJJEM7NDJG6U)

## Start with this stack

[Create a workspace and connect Klaviyo + Amazon Attribution](https://app.withhendrik.com/auth?mode=sign-up&acquisition_channel=marketing&return_to=%2Fonboarding%2Factivation&cta_location=integration_markdown&landing_page_id=combination-klaviyo-amazon-attribution&combination=klaviyo-amazon-attribution)