Off-Amazon Destinations on Amazon DSP

The destination types, according to Amazon's own guidance

Amazon's own DSP creative guidance describes destinations as flexible in a way sponsored ads' aren't — while Sponsored Products, Sponsored Brands and Sponsored Display link only to Amazon-owned pages, DSP campaigns can point at a genuine Amazon destination or a non-Amazon one, including a brand's own website. Two off-site landing page patterns are named specifically: an off-site page with educational content and promotions, and an off-site page built around calls-to-action, value proposition and lead-generation or checkout elements. Which pattern fits depends on the campaign's actual goal — the first suits a brand-awareness or consideration objective, the second suits direct conversion.

The Amazon logo requirement

Amazon's policy is specific: advertisers directing traffic to an off-site destination must display the Amazon logo on that page, unaltered, and not incorporated into a sentence. The stated reason is to communicate that the product is also available on Amazon — a genuine requirement, not a suggestion, and one that a creative or web team unfamiliar with DSP-specific policy can easily miss if they're not briefed on it before building the landing page.

What DSP's own reporting shows for an off-site destination, and what it doesn't

Amazon DSP's native console reports what it always reports for any campaign: impressions, clicks, spend, CPM, CPC. For an off-site destination, that's where Amazon's own reporting stops — it doesn't natively show what happened after the click landed on the off-site page, because that activity happens outside Amazon's own systems. Amazon Attribution, the tool built to measure off-Amazon marketing channels' impact, works in the opposite direction: it measures off-Amazon channels driving to Amazon, not Amazon-originated traffic landing off-Amazon. Neither Amazon tool closes this specific gap — measuring what happened on the off-site page itself requires that page's own analytics or a conversion pixel.

Why brands default to only using the checkout-focused pattern

Most brands new to DSP jump straight to the call-to-action, checkout-focused destination pattern, because it's the one that most resembles the direct-response advertising they already know from Meta and Google. That's a reasonable starting point, but it skips the educational pattern's genuine use case — reaching an audience that isn't ready to buy yet and doesn't need to be rushed to a checkout to be worth the impression. A brand entering a category shoppers don't yet know they need often gets more long-run value from an educational off-site page paired with a separate, later retargeting flow than from forcing every DSP impression toward an immediate conversion attempt.

A worked example combining both destination types in one plan

Take a brand running two DSP off-site line items: $5,000 to an educational content page introducing a new product category (no direct purchase path, aimed at consideration), and $10,000 to a checkout-focused landing page with a direct add-to-cart flow. The educational line's success metric is time-on-page and downstream branded search lift — not a direct sale, since that's not what the page is built for. The checkout-focused line's success metric is conversion rate and cost-per-acquisition on the destination site itself, measured through the site's own analytics, since Amazon's reporting stops at the click for both.

The common mistake, including ours

The mistake is treating both off-site destination types with the same measurement expectation — checking an educational content page for a direct-sale ROAS it was never built to produce, or leaving a checkout-focused page unmeasured because the team assumed "off-site" meant unmeasurable by definition. We've seen a client team abandon a genuinely well-performing checkout-focused link-out line because nobody had set up conversion tracking on the destination page, and the DSP console alone — showing clicks and spend with no conversion data — looked like proof of failure rather than an absence of the right measurement tool.

That specific error is easy to repeat because it looks, from inside the DSP console alone, exactly like a genuinely underperforming campaign — clicks and spend with no visible return. The only way to tell the two apart is checking whether conversion tracking exists on the destination at all before drawing a conclusion from what the console shows.

Why the pixeling gap adds a second layer of complexity

Amazon's own pixeling policy governs third-party pixels placed on Amazon-owned properties — Amazon.com, IMDb and similar sites in Amazon's network — and it's explicit about cookie expiry, technical specs and resegmentation restrictions in that context. It's silent on pixel placement for advertiser-owned domains, because that's simply outside its scope: a pixel on your own off-site landing page is governed by your own site's privacy policy and consent management, not Amazon's ad policy. That's worth knowing precisely because it means the compliance question and the measurement question for an off-site DSP destination are genuinely separate problems, solved with separate tools — Amazon's ad policy for the creative and logo requirement, your own site's infrastructure for the pixel and conversion tracking.

What to set up before launching either destination type

Confirm the Amazon logo requirement is built into the landing page creative before submitting for review — a straightforward, avoidable rejection otherwise. For an educational page, set expectations and success metrics that match its actual objective rather than a sales metric it isn't built to hit. For a checkout-focused page, build conversion tracking on the destination site before spend starts, not after the first performance review raises the question — the destination page needs its own measurement plan regardless of how well Amazon DSP's own console is reporting clicks and spend.