Amazon Ads UTM tracking (off-Amazon destinations)
Amazon Ads that send traffic to your own website — such as Amazon DSP placements or brand campaigns pointing off-platform — can be tagged with UTM parameters on the destination URL. Ads that land on an Amazon product or Store page cannot, because you do not control Amazon's URLs. This page draws that line clearly and gives a structure for the off-Amazon case.
When UTMs apply to Amazon Ads
UTM parameters only work on URLs you control. Amazon Ads formats that send clicks to your own website — primarily Amazon DSP campaigns and any brand placement linking off-platform — let you set that destination URL, so you can append UTMs.
Formats that drive to an Amazon product detail page, Brand Store, or listing cannot carry your UTMs, because Amazon owns those URLs and the visitor never lands on your analytics.
- utm_source=amazon
- utm_medium=display (DSP) or the format-appropriate medium
- utm_campaign=<campaign-name>
- utm_content=<placement or creative>
On-Amazon vs off-Amazon
This is the key distinction. On-Amazon conversions are measured inside Amazon's own reporting and attribution — your site never sees them. Off-Amazon traffic to your domain is where UTMs and your analytics take over.
Worked example (DSP to your site):
https://example.com/landing?utm_source=amazon&utm_medium=display&utm_campaign=dsp-prospecting&utm_content=300x250
Verification note
Amazon Ads product surfaces and DSP UI change over time and vary by account access. Confirm in your own Amazon Ads or DSP console which destination URLs you can edit before standardizing a UTM convention. The specifics of any one ad format are marked as not fully verifiable from public docs here; the on-Amazon vs off-Amazon principle is the durable rule.
How it appears in analytics and logs
A visit with utm_source=amazon and utm_medium=display from a DSP placement confirms an Amazon-Ads click to your site. Clicks that land on an Amazon.com product page never reach your analytics at all, so no UTM applies there.
Diagnostic use case
Tag Amazon Ads that drive to your own domain so those clicks are attributed; understand why on-Amazon destinations cannot carry your UTMs.
What WebmasterID can help detect
WebmasterID attributes utm_source=amazon visits that reach your own site server-side; it cannot see clicks that stay on Amazon's domain, which is a platform boundary, not a gap to invent around.
Common mistakes
- Expecting UTMs on ads that land on an Amazon product page — you don't own that URL.
- Double-counting on-Amazon conversions (in Amazon's reports) and off-Amazon visits.
- Inconsistent utm_medium across DSP formats.
- Encoding shopper or order data into UTM values.
Privacy and accuracy notes
Amazon Ads UTM values should hold campaign and placement labels only. Never encode a shopper or order. UTM values are public in the destination URL.
Related pages
- Display ads UTM tracking
Display and programmatic ads need their own medium so banner clicks are not confused with paid search or social. This page shows how to use utm_medium=display consistently and explains how platform click IDs differ from the utm_* parameters generic analytics tools read.
- Programmatic & DSP UTM tracking
Programmatic display bought through a demand-side platform (DSP) serves across countless publishers via real-time bidding. UTM parameters plus the DSP's dynamic macros on the landing URL are how those scattered clicks get attributed. This page gives a recommended structure and explains the macro approach common to DSPs.
- UTM vs click IDs (gclid, fbclid, msclkid)
UTM parameters are manual labels you write; click IDs like gclid, fbclid, and msclkid are opaque identifiers a platform auto-appends. This page explains how they differ, which tools read which, and why setting conflicting manual and auto-tagged values on one URL causes double-counting.
- Attribution analytics
Attribute off-Amazon DSP clicks that reach your own site.
Sources and verification notes
- Amazon Ads — Amazon DSP overviewDSP can drive to off-Amazon destinations you control; format specifics vary by account.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.