How to track checkout to purchase for Amazon Ads

Architecture

The exact event sequence

Five stages. Stage three is the one you often can't instrument, which is precisely why stage four has to be the source. The identifier has to survive all of them.

1. Step 1

   Checkout started

   Browser-side, with value. The last point you reliably control the page.

2. Step 2

   Payment info submitted

   Worth splitting out — it turns one opaque step into a diagnosable one.

3. Step 3

   Payment authorised

   Often on someone else's domain, and frequently invisible to your tags entirely.

4. Step 4

   Order created

   From the order webhook. This is the only step that sees every order regardless of how payment happened.

5. Step 5

   Purchase sent with the order ID

   Deduplicated on that ID, with refunds wired to reverse.

Diagnostic sequence

What's specific to Amazon Ads

The funnel logic above is the same wherever you advertise. These are the parts that change because it's Amazon Ads.

1. 1

   Click identifier: no click identifier for on-Amazon conversions

   This is the important thing and most guidance skips it: Amazon Ads spans two very different situations. Sponsored ad formats driving to an Amazon listing produce conversions Amazon measures itself, with no click identifier passed to you and no per-order join available. Amazon DSP driving to your own site is a different case, where a click identifier can reach your landing page and be captured like any other network's.

2. 2

   Import mechanism: conversion upload, where applicable

   Where you are driving to your own site, conversions can be sent back. Where you are driving to an Amazon listing, the transaction happens inside Amazon's checkout and there is nothing to send — Amazon's own attribution reporting is the only view available and it is aggregated.

3. 3

   Deduplication

   For on-Amazon purchases the question does not apply, because you are not measuring the conversion at all — Amazon is. For traffic to your own site the usual shared-identifier pattern applies.

4. 4

   Window and timing

   Amazon's attribution windows differ by ad product and by whether the conversion happens on Amazon or on your site. Establish which product and which destination you are reporting on before comparing any figure.

5. 5

   The Amazon Ads gotcha

   The structural limit is worth stating plainly to anyone selling you on this: for sales that complete inside Amazon, per-order click attribution does not exist and cannot be built. Amazon Attribution gives aggregated, delayed reporting. Anyone offering per-order joins on Amazon-completed sales is describing something that is not available.

Source-of-truth validation

How to prove the chain works

One real journey, followed all the way, then a reconciliation. Neither on its own is enough.

• A live Amazon Ads ad clicked, and the identifier confirmed present on the landing URL.
• The same identifier confirmed on the order record in your store after a full real journey through every step.
• Purchase sent with the order ID confirmed arriving at Amazon Ads, verified by Amazon's own attribution reporting for on-Amazon sales, and your normal reconciliation for off-Amazon conversions.
• Your store's order records, web orders only reconciled against Amazon Ads per record over a fully closed window.
• The same reconciliation repeated 30 days later.

Straight talk

When this doesn't apply to you

Worth checking before you build anything, because two of these are common and both mean the work isn't worth doing.

• If your checkout is entirely on your own domain with no wallet options and a confirmation page every customer reaches, the browser-side event may genuinely be sufficient — reconcile a closed week and find out before building anything.
• If all your Amazon Ads spend drives to Amazon listings, there is no conversion tracking build here — only a reporting exercise inside Amazon's own tools, and it is worth knowing that before commissioning anything.
• If your cycle from click to purchase sent with the order id regularly exceeds the import window, the final event can't drive bidding whatever you build. Optimize toward payment info submitted instead and use the later data for budget decisions rather than for bidding.
• If almost none of your orders carry a click identifier today, that's the whole project. Fix capture first — the import is the easy half and no tooling rescues a record with nothing to reference.