Skip to main content
Now booking · 2–4 day turnaround

Amazon Ads · PQL → closed won · Conversion tracking

How to track product-qualified lead to closed won for Amazon Ads

A product-qualified lead is defined by what someone did in the product, not by what they filled in. That makes the qualifying event a product decision rather than a marketing one — and it means the definition lives in code that marketing usually cannot see. On Amazon Ads the specifics that matter are the click identifier (no click identifier for on-Amazon conversions), the import mechanism (the Amazon Ads conversion API, for off-Amazon destinations only), and Deduplication only arises for off-Amazon conversions where both a tag and a server event exist. The chain only works end to end if the identifier is captured on landing and stored on the closed-won opportunity in your CRM — no cookie survives the gap between ad click and closed won.

✓ 30-minute call · No commitment · You leave with a written remediation plan even if we’re not the right fit.

Built in 2–4 daysOne-time fee95% accuracy guaranteed400-day cookie lifetime1st-party server-side

Written guarantee

95%+ conversion accuracy on Amazon Ads · PQL → closed won

Measured against your own order records at handover. Miss it and we keep working at no cost until it’s met.

Built on — and certified for — the platforms that matter

Stape

Pro Partner

Meta

Tech Provider

Google

Tag Manager

TikTok

Events API

Microsoft

UET Partner

LinkedIn

CAPI Partner

Pinterest

CAPI Partner

Built on the same partner stack used by enterprise DTC brands.

Ariful Islam — Founder, Tracking Consulting

Meet your consultant

Ariful Islam

Founder · 8+ years in paid media & tracking

Verified earnings

$200K+

earned on Upwork

Top Rated Plus
4.9/5 on Upwork · 300+

Verify the receipts

You work directly with Arif — no SDR, no account manager.

The problem

Where this funnel usually breaks

Amazon Ads · PQL → closed won-specific issues
Leak #01

The PQL definition living only in engineering

Marketing optimises toward a threshold it cannot see and cannot influence, and the definition changes without notice.

Leak #02

Individual signups counted, accounts ignored

Five colleagues from one company is one opportunity. Counting people inflates the pipeline and hides that a single account is in market.

Leak #03

Thresholds tuned without telling anyone

A product team lowering the seat threshold triples PQL volume overnight, and the marketing report reads it as campaign success.

Leak #04

Self-serve revenue and sales-assisted revenue pooled

The same account can pay a card charge and sign a contract. Counting both double-counts the customer.

Specific to Amazon Ads × PQL → closed won

Amazon Ads and PQL sales: no realistic path to closed-won credit

On Amazon Ads, a PQL-to-closed-won funnel can only be measured off-Amazon: send signup and PQL events from your server through Amazon's conversion API for DSP traffic to your site. There is no click identifier to store on the account, so closed-won deals belong in your CRM rather than in Amazon reporting.

Product-led B2B software isn't bought on Amazon, so on-Amazon ad products don't apply, and DSP's strength is shopping behavior rather than workplace software adoption. AWS Marketplace is a separate procurement route; a deal transacted there is not an Amazon Ads conversion and shouldn't be reported as one.

If you run DSP to reach business audiences, send the signup and the PQL as conversion events through Amazon's off-Amazon tooling, and record the source on the account at signup. Expect aggregated reporting and lookback windows far shorter than a sales cycle, and ask Amazon which windows apply to your line items before setting any target.

Closed won should be credited from the CRM using the account's source field, not sent back to Amazon. The minimal honest setup is that source field plus a signup event, reviewed after a quarter for any accounts that reached PQL. If none did, stop the test; a richer integration won't make an audience of shoppers adopt team software, and the hours are better spent on search and LinkedIn capture.

Architecture

The exact event sequence

Five stages. The break is at qualification: the threshold is set in the product, and if marketing does not know what it is, the reported conversion is a number nobody can explain. The identifier has to survive all of them.

  1. Step 1

    Ad click

    Onto a self-serve signup, usually with no sales contact at all.

  2. Step 2

    Self-serve signup

    An individual, frequently without their company's knowledge.

  3. Step 3

    Usage threshold crossed

    The PQL definition. Seats added, volume used, a specific feature adopted.

  4. Step 4

    Sales contact

    Triggered by the product signal rather than by a form.

  5. Step 5

    Closed won

    At a contract value far above what the individual was paying.

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.

Source of truthyour CRM, joined to the product usage that triggered qualification
  • A live Amazon Ads ad clicked, and the identifier confirmed present on the landing URL.
  • The same identifier confirmed on the closed-won opportunity in your CRM after a full real journey through every step.
  • Closed won 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 crm, joined to the product usage that triggered qualification 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 you have no sales motion on top of self-serve, there is no PQL stage — measure the self-serve conversion directly.
  • 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 closed won regularly exceeds the import window, the final event can't drive bidding whatever you build. Optimize toward accounts crossing the usage threshold, deduplicated to the organisation instead and use the later data for budget decisions rather than for bidding.
  • If almost none of your closed-won deals 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.
The outcome

What working looks like

Closed won attributed to the click

Server-side

Weeks later if necessary, because the identifier lives on the closed-won opportunity in your CRM rather than in a cookie.

Amazon Ads bidding fed the real outcome

8+ EMQ

Via conversion upload, where applicable, so it optimizes toward closed-won deals from product-qualified accounts rather than toward self-serve signups.

A reconciliation that closes

Deduped

Your crm, joined to the product usage that triggered qualification matched per record against what Amazon Ads reports, over a fully closed window.

What you get

The implementation, on Amazon Ads

Item 01

Capture the Amazon click identifier, where one exists on landing

For off-Amazon destinations, capture and persist the click identifier as with any network. For on-Amazon destinations there is nothing to capture.

Item 02

Persist it to the closed-won opportunity in your CRM

Store the identifier on the account rather than the user, since the person who signed up is frequently not the person who signs.

Item 03

Send closed won from the record

Your CRM on closed-won, deduplicated to the account, with the qualifying product event recorded on the opportunity. Dispatched to Amazon Ads through the Amazon Ads conversion API, for off-Amazon destinations only.

Item 04

Deduplicate and reverse

Deduplication only arises for off-amazon conversions where both a tag and a server event exist. Lost and disqualified opportunities reverse.

Want this built for Amazon Ads · PQL → closed won? One fixed price, $400–$1,800, no monthly fee. Live in 2–4 business days, 95%+ accuracy in writing. See packages

Book a free 30-min call

Got questions?

The honestanswers.

No buzzwords, no upsell. If we don’t know, we say so.

01Can Amazon DSP reach B2B software buyers?

Amazon offers some business-oriented audiences in DSP; check availability with your Amazon contact. Even so, judge the test on PQL rate in your CRM rather than on DSP reports.

02Does AWS Marketplace revenue count as an Amazon Ads conversion?

No. Marketplace is a procurement route, and its sales aren't attributed to Amazon Ads campaigns. Track it as a closed-won deal source in your CRM.

03Why isn't self-serve signup enough to optimize on?

Because signups are individuals and deals are organisations, and the ratio between them differs enough by channel to invert which campaigns look effective.

04How does the identifier survive to closed won?

It doesn't, as a cookie — the gap is too long. It has to be written onto the closed-won opportunity in your CRM at the point of ad click, where it lives as a field rather than as browser storage.

05What does Amazon Ads need to accept the conversion?

For off-Amazon conversions: an event, a timestamp, a value and the click identifier. For on-Amazon conversions: nothing, because the measurement is not yours to do.

06How long does this take to build?

Two to four days for the implementation, plus a closed reconciliation window before we'd call it verified. Capture and persistence are the fiddly parts; the import itself is usually an afternoon.

07Can I do this myself?

Yes, and the reference pages on this site cover the mechanics. The part that's genuinely tedious rather than clever is keeping the Amazon click identifier, where one exists alive through multi-step forms and a signup by one person and a purchase by another at the same company, which fails silently at every stage.

Still have questions?Book a 30-min call— bring them all.

Free · 30 minutes · No commitment

Get product-qualified lead to closed won tracked properly on Amazon Ads

Book a free 30-minute call. We measure your actual identifier coverage on your own account, live, and you leave with a written plan — including the option that you don't need us.

Free · 30-min consultation · No commitment · Replies in under 2 hours · Available worldwide via WhatsApp

95% guarantee · from $400