Meta Ads
Spend, delivery, and Meta reported conversions show the Meta Ads side of the question.
How to connect Meta AdsMeta Ads + Amazon Attribution
What did Amazon Attribution see from tagged Meta traffic?
Connect Meta Ads and Amazon Attribution to Hendrik. Compare a verified tagged Meta Ads activity with Amazon Attribution’s marketplace-specific off-Amazon data.
See Hendrik at work
Meta Ads + 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.
| Metric | Previous | Current |
|---|---|---|
| Meta Adsreported conversion value (USD, 28 days) | 71,000 USD | 82,000 USD |
| Amazon Attributionattributed Amazon sales (USD, 28 days) | 22,000 USD | 28,000 USD |
| Meta Adsspend (USD, consecutive 28-day periods) | 21,000 USD | 26,000 USD |
What Hendrik checks
Attribution and delivery mix
Check Meta attribution setting, conversion event, placements, audiences, and creative delivery before interpreting reported outcomes.
Tag and marketplace identity
Check the Attribution tag, marketplace, attribution window, and the established identity of the external activity.
Explain the divergence
Meta Ads: reported conversion value (USD, 28 days) changed from 71,000 USD to 82,000 USD. 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 dataWant Hendrik to answer this with your data?
One analysis, different integrations
What each integration adds
Amazon Attribution
Tagged off Amazon activity shows what Amazon Attribution reports for that tag and destination.
How to connect Amazon AttributionConnect your stack
Set up each integration in one workspace.
- Create your Hendrik account. Choose a workspace for your business.
- Connect your data. Use each integration’s setup instructions above. Availability and permissions are shown in your workspace.
- 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 Meta Ads account with delivery and conversion reporting for the stated window.
- 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
- Meta attribution remains separate from store, payment, or CRM outcomes; do not sum it with another platform’s conversion value.
- Tagged Amazon Attribution results need a real tag, destination, and window; they do not establish shared campaign identity elsewhere.
- Meta attribution and Amazon Attribution are not deduplicated outcomes.
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