Meta Ads to Amazon Attribution: The Complete Setup Guide

Selling on Amazon with Meta ads has one structural problem: the purchase happens on a site you do not control, so neither the Meta Pixel nor a normal Conversions API setup can see it. Amazon Attribution closes part of that gap by reporting which tagged clicks turned into orders. This guide walks through the complete setup, from prerequisites to the moment a real Amazon purchase shows up as a Purchase event inside Meta Events Manager, using PixlBridge to automate the plumbing in between.

Coming soon: PixlBridge's Amazon connection is coming soon, so you can't connect Amazon in PixlBridge yet. The PixlBridge steps below describe how it will work; the Amazon and Meta steps apply today.

What you need before you start

• An Amazon Ads account enrolled in Amazon Attribution. Attribution is available to Brand Registry sellers, vendors and KDP authors in supported marketplaces. If your account is not enrolled yet, open advertising.amazon.com, choose Amazon Attribution and register your brand. Enrolment is free.
• A Meta ad account and a Pixel (dataset) in the same Business Manager. The dataset is where Conversions API events will land. You do not need a website for this; the dataset just needs to exist.
• Admin access to both. The connect flows use Facebook Login for Business and Login with Amazon, so the person connecting must be able to grant ads permissions on each side.
• Your ASINs. One tracked link points at one Amazon product page (or a storefront URL). Keep a list of the ASINs you advertise.

How the loop works

A shopper taps your ad. Instead of sending them straight to Amazon, the ad's destination is a short tracked link on go.pixlbridge.com. The redirect records the click context: the fbclid Meta appends to outbound clicks, a first-party _fbp cookie, the device type and browser. It then forwards the shopper to the Amazon product page with an Amazon Attribution tag appended, and on mobile it deep links into the Amazon app where possible. When Amazon Attribution later reports that the tagged click produced an order, PixlBridge matches the order back to the click and posts a Purchase (and AddToCart, when reported) to your Meta dataset through the Conversions API, carrying the click's match keys.

Step 1: connect Meta

In your PixlBridge workspace open Connections and choose Connect Meta. You are sent to Facebook Login for Business, where you approve the ads permissions. Back in PixlBridge, pick the ad account and the Pixel/dataset that should receive events. If you only have one of each, they are selected automatically.

Two things to know: a Meta ad account can be live in only one PixlBridge workspace at a time (this is what makes per-ad reporting unambiguous), and the token Meta issues is long-lived and refreshed by PixlBridge in the background. If it ever expires, the connection shows needs reauthorisation and a single click fixes it.

Step 2: connect Amazon

Choose Connect Amazon. Login with Amazon asks you to approve access to the Amazon Ads API. PixlBridge then lists your advertising profiles across the North America, Europe and Far East regions and, for the profile you select, the Amazon Attribution advertisers it can see. Pick the advertiser that matches your brand.

If the list is empty, the account is not enrolled in Amazon Attribution yet (the connection will say no attribution advertisers). Enrol first, then reconnect.

Step 3: sync your Meta campaigns

Once Meta is connected, PixlBridge pulls your campaign, ad set and ad catalog. This matters because attribution is reported per link, and each link is tied to a specific Meta ad. When Meta ads are paused or deleted, links attached to them are retired automatically so your reports stay clean.

Step 4: create tracked links

Open Links, choose New link, and fill in:

1. Destination: the ASIN (PixlBridge builds the product URL for your marketplace) or a full Amazon URL. Only Amazon hosts are accepted; the redirect can never be pointed elsewhere.
2. Meta ad: the ad this link will be used in, picked from the synced catalog. This is what lets PixlBridge report sales per creative later.
3. Attribution tag: PixlBridge creates the Amazon Attribution tag for you through the Ads API. If you already have a tag for this ad, paste it instead.

The result is a short URL such as https://go.pixlbridge.com/r/k3f9q2. Create one link per ad. Reusing a link across ads works, but you lose the per-creative split.

Step 5: put the link in the ad

In Ads Manager, set the ad's Website URL to the tracked link. Do not add UTM or Amazon parameters to it; PixlBridge appends the attribution tag and, if you use it, your Brand Referral Bonus tag at redirect time (see the Brand Referral Bonus guide). Leave Meta's default URL parameters on; Meta adds fbclid automatically and that is one of the match keys we rely on.

Publish the ad and click it yourself once from a phone. In PixlBridge the link should show a click within seconds, with the device and browser recorded.

Step 6: wait for Amazon to report

This is the part that surprises people coming from Shopify: Amazon Attribution is a reporting product, not a real-time webhook. PixlBridge downloads your attribution reports on a schedule and keeps a rolling 30-day window. Amazon reports conversions typically within a day or two, per Amazon, and may correct its figures afterwards as returns and late attributions settle.

PixlBridge handles the corrections for you: it is built so each Amazon order becomes one conversion record with a deterministic event id, so an order that is reported today and corrected later doesn't turn into two Meta events. Because the order is tied to the tagged click, the record carries the click's fbc (derived from fbclid), fbp, IP address and user agent.

Step 7: verify events in Meta

Open Meta Events Manager, select your dataset and look at the Overview tab. Server events from PixlBridge appear under the Server connection method with the event names Purchase and AddToCart. Before real orders arrive you can prove the pipe works: in PixlBridge, open the Meta connection and use Send test event with a test event code from Events Manager; it shows up in the Test events tab.

Meta accepts server events up to seven days after they happened. Amazon's reporting delay is well inside that window, so purchases arrive late but still count.

Step 8: read the results

The PixlBridge dashboard joins three things per campaign, ad set, ad and creative: Meta spend (from the Marketing API), clicks (from the redirect) and Amazon attributed sales (from the reports). The blended ROAS column is simply attributed Amazon sales divided by Meta spend for the same period. Reports can be grouped by day, week, month or ASIN and exported as CSV.

Two caveats worth internalising. Amazon Attribution uses a 14-day lookback, so a report cut on Monday will keep growing for a while. And Meta's own reporting will now also show purchases; the two numbers will not match exactly, because Meta applies its own attribution settings (for example 7-day click) and view-through rules. Treat the PixlBridge number as the deterministic one and Meta's as the delivery system's view.

Troubleshooting

Clicks but no conversions after a few days

• Check the Amazon connection: the selected advertiser and region must be the ones running the tagged products.
• Open the link's details: the destination shown there must contain the attribution tag. If the destination URL already had a tag= parameter when you created the link, the existing one wins and the attribution tag is not applied.
• Give it time. Low-volume products can genuinely take days to show the first attributed order.

Events not appearing in Events Manager

• The Meta connection needs a selected Pixel/dataset. A connection in needs selection state stores events locally until you pick one.
• Look at the connection's health panel: each sync job reports success or the provider's error message.

In-app browsers

Most Meta clicks come from the Facebook or Instagram in-app browser. PixlBridge detects them and, on iOS and Android, tries to hand the shopper to the Amazon app, which converts better than the mobile web. The click is recorded either way.

Where to go from here

With purchases flowing, the interesting change is on the Meta side: you can now run Sales campaigns optimised for Purchase against an Amazon destination. Read why Meta optimises for link clicks instead of buyers for how to restructure campaigns around the new signal, and see the pricing page for link and event allowances per plan.