Amazon Ads conversion tracking for multi-location businesses
A multi-location business has one website, many Google Business Profiles, many phone numbers, and a reporting requirement that runs both ways — head office needs the portfolio view and each location needs its own numbers. What Amazon Ads adds on top of that is a mechanical requirement: the Amazon click identifier, where one exists have to reach the record that holds the money, because Amazon Ads can only credit a conversion it can tie back to a click it recognizes. This page covers both halves — what a conversion is in multi-location businesses, and what Amazon Ads specifically needs to accept it.
Free30 minutesNo obligation
Specific to Amazon Ads × Multi-location
Amazon Ads for multi-location brands: DSP to your own locator
For a multi-location business, Amazon Ads conversions are trackable only when Amazon DSP sends traffic to your own site, where the click identifier is captured and a branch booking or order is sent back from your system. Sales completed on Amazon are measured by Amazon in aggregate and can never be tied to a branch.
Multi-location brands reach Amazon Ads in two ways. Retail brands with physical stores may also sell on Amazon, where sales are measured by Amazon and belong to no branch. Service and retail chains may use Amazon DSP's audience data to reach households near their locations and send them to a store locator or branch booking page, which is the case worth building for.
For DSP traffic, capture the click identifier on the landing page, carry it through the store locator into the branch booking or order, and send the conversion from your own system with value. Check DSP's geographic targeting against your branch footprint. Impressions bought in areas without a branch show up as reach and produce visits that can't convert.
Don't let Amazon's aggregated marketplace sales mix with branch revenue. A furniture chain selling the same sofa on Amazon and in-store will see Amazon claim sales in markets where it also runs local campaigns. Report marketplace sales as their own channel, and compare branch revenue by market against DSP spend rather than against Amazon's attribution totals.
Amazon Ads · Multi-location · what breaks
Why Amazon Ads under-reports for multi-location businesses
- 01
Conversions in one undifferentiated pool
No location can be evaluated.
- 02
Location pages sharing one phone number
So calls can't be attributed to a branch.
- 03
Head office and branch reporting in conflict
Two audiences, one number.
- 04
The Amazon click identifier, where one exists never reaches the record
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.
Amazon Ads · Multi-location · the fix
What working looks like — Amazon Ads · Multi-location
Every conversion carrying a location
At the point it happens.
Per-location and portfolio views
From the same data.
Budget allocated on measured performance
Rather than on instinct.
Amazon Ads · Multi-location · architecture
How Amazon Ads and multi-location businesses actually connect
- 1
The conversion in multi-location businesses
Enquiry, booking or order, fulfilment — each carrying a location. The location dimension matters more than any individual stage.
- 2
Amazon Ads needs a click to match
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.
- 3
The identifier: the Amazon click identifier, where one exists
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.
- 4
Where it gets sent from
each location's own booking, order or job records.
- 5
Deduplication and window
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. 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.
Amazon Ads · Multi-location · events
The conversion map for multi-location businesses
The stages are ordinary. What makes this vertical hard is that every one of them needs a location attached.
| Event | What it means here |
|---|---|
| Enquiry with location | Browser-side, location from the page or the form. |
| Call with location | A tracked number pool per branch. |
| Booking or order with location | Server-side from the branch's own system. |
| Fulfilment with location | Server-side. The conversion that carries value. |
| Location dimension | Present on every event. Without it none of this is usable. |
Amazon Ads · Multi-location · diagnose
Diagnostic order — Amazon Ads · Multi-location
- 01
Count records carrying the Amazon click identifier, where one exists
- 02
One phone number across all location pages
Calls can't be attributed to a branch, which is usually most of the conversions.
- 03
Location missing from the conversion event
So the data exists and can't be split.
- 04
Google Business Profile calls uncredited
A large local channel, invisible.
- 05
Read Amazon's own attribution reporting for on-Amazon sales, and your normal reconciliation for off-Amazon conversions
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.
Amazon Ads · Multi-location · prove
How it gets proven — Amazon Ads · Multi-location
Source of truth
each location's own booking, order or job records
- Location present on every conversion event, verified on live conversions at more than one branch.
- A tracked number pool confirmed per location.
- Per-location reconciliation for a closed month.
- Portfolio totals that add up from the per-location figures.
- Amazon's own attribution reporting for on-Amazon sales, and your normal reconciliation for off-Amazon conversions read directly, not inferred from an upload succeeding.
Amazon Ads · Multi-location · free audit
What we check in the free audit
- Count records carrying the Amazon click identifier, where one exists
- One phone number across all location pages
- Location missing from the conversion event
- Google Business Profile calls uncredited
- Read Amazon's own attribution reporting for on-Amazon sales, and your normal reconciliation for off-Amazon conversions
Checked against
each location's own booking, order or job records
Free30 minutesNo obligation
Amazon Ads · Multi-location · when not to buy
When you don't need this — Amazon Ads · Multi-location
- If Amazon Ads already reports conversions that reconcile against each location's own booking within a few percent, this is working and there is nothing to buy.
- Measure identifier coverage yourself first — pull your last hundred records and count how many carry the Amazon click identifier, where one exists.
- 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.
Amazon Ads · Multi-location · what we deliver
What gets built — Amazon Ads · Multi-location
Location captured on every conversion
From the page, the form, or the number dialled.
A tracked number pool per location
So calls resolve to a branch.
Location-level records as the source of truth
The branch system, not a site-wide total.
Reporting built both ways
Portfolio and per branch.
Dispatch via the Amazon Ads conversion API, for off-Amazon destinations only
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.
Written guarantee
95%+ tracking accuracy
Measured against each location's own booking, order or job records. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
Amazon Ads · Multi-location questions, answered
Yes, if they drive to your own site and the click identifier is carried into the branch booking or order. Your system then records which branch fulfilled it; Amazon's own reporting won't.
No. They happen inside Amazon's checkout with no branch attached. Report them as a separate channel rather than splitting them across locations.
Yes, if location is captured on every conversion — from the page path, a form field, or the number dialled. Without that, the data is one undifferentiated pool.
A tracked number pool per location. One shared number makes branch-level call attribution impossible, and calls are usually most of the volume.
Track them per location and separately from paid. They're a real channel and mixing them makes both unreadable.
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.
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.
By reading Amazon's own attribution reporting for on-Amazon sales, and your normal reconciliation for off-Amazon conversions and reconciling against each location's own booking, order or job records. An upload that succeeds is not an upload that matched.
More on Amazon Ads · Multi-location
- Multi-locationConversion tracking for multi-location businesses, attributed to the right branc…
- Google Ads · Multi-locationGoogle Ads conversion tracking for multi-location businesses
- Meta · Multi-locationMeta Ads conversion tracking for multi-location businesses
RELATED GUIDES
More for multi location businesses: other angles on the same outcome
- Multi-locationConversion tracking for multi-location businesses, attributed to the right branch
- Amazon Ads · Vacation rentalsAmazon Ads conversion tracking for vacation rental management companies
- Amazon Ads · Dance and musicAmazon Ads conversion tracking for dance and music schools
- Amazon Ads · Franchise enquiry → agreementHow to track franchise enquiry to signed agreement for Amazon Ads
- Amazon Ads × POS SystemHow to reconcile Amazon Ads against your point-of-sale system
- Clover → Amazon AdsConnecting Clover to Amazon Ads
- Amazon Ads · Salons and barbersAmazon Ads conversion tracking for nail salons and barbershops
- Amazon Ads · Martial artsAmazon Ads conversion tracking for martial arts schools
Free · 30 min
Get Amazon Ads reporting what multi-location businesses actually earn
WhatsAppFree30 minutesNo obligation
