My Sponsored Products convert on Amazon — can Admaxxer attribute them?

Not via the pixel — the conversion happens on amazon.com, off your domain. Native integration (when shipped) pulls Sponsored Products revenue directly from the Amazon Ads API via the LWA refresh-token flow. For now, those orders sit in your Amazon Seller Central reports outside the Admaxxer dashboard.

What about Amazon DSP campaigns that drive traffic to my DTC store?

Those are fully attributable today via UTMs + the amzn_cid click-ID (already captured per GL#361). UTM-tag your DSP destination URLs and the visitor_payments row picks up both campaign-level UTMs and the click-ID at payment time.

Do I need Amazon Attribution tags?

If you want spend reconciliation in Amazon Seller Central before our native integration ships — yes, set up Amazon Attribution and pass through both their tracking parameters and Admaxxer UTMs. Both can coexist on the same URL; the pixel preserves arbitrary URL params.

When will native Amazon Ads land?

Active development. The LWA refresh-token paste-token flow is the canonical auth path (matching Meta and Google's paste-token pattern). Star the integration on /integrations to be notified.

Coming soon · Amazon Ads integration

Amazon Ads integration — coming soon

Native API integration for Amazon Ads is in active development. Until then, you can attribute every Amazon Ads dollar today with a two-step UTM-and-pixel bridge: tag your Amazon Ads URLs with the UTM template below, paste the Admaxxer pixel on your storefront, and our 30-platform smart-referrer classifier (per GL#361) auto-attributes revenue with 365-day first-touch persistence.

Star the integration on /integrations FAQ

The bridge — use our pixel + UTM tagging today

Three steps. About five minutes total.

Step 1 — Install the Admaxxer pixel

If you haven't already, drop the Admaxxer pixel into your storefront's <head>. Works on Shopify, WooCommerce, BigCommerce, Squarespace, Wix, Webflow, and any custom storefront. See install instructions for 35+ platforms.

Step 2 — Tag every Amazon Ads URL with UTMs

In the Amazon Ads UI, append these query parameters to every destination URL:

utm_source=amazon — identifies Amazon Ads as the source
utm_medium=cpc — categorizes the channel type
utm_campaign=<your_campaign_name> — for per-campaign breakdown in MER, ROAS, and cohort LTV
utm_content=<creative_or_keyword> — optional, for per-creative reporting

Example tagged URL:

https://yourstore.com/dtc-collection?utm_source=amazon&utm_medium=cpc&utm_campaign=amazon-dsp-2026-q2&utm_content=hero-creative

Step 3 — Revenue auto-attribution kicks in

The first time a visitor lands on your site from a tagged Amazon Ads URL, the Admaxxer pixel writes the UTM tuple into localStorage for 365 days. Our pixel already captures amzn_cid from Amazon Ads click URLs (per GL#361) — even before native integration ships. When the visitor checks out — even months later, even from a different device that we stitch via email_hash — the order is attributed back to the original Amazon Ads campaign on the visitor_payments row.

Tag once, our 30-platform classifier (including AI-chat referrers) does the rest.

What's already working today via UTMs

Revenue attribution per campaign — both last-touch and first-touch, on every order row.
Click-ID coverage — amzn_cid captured at payment time on visitor_payments rows.
Cohort LTV by acquisition campaign — 7 / 30 / 90-day windows, partial-refund-aware.
MMM contribution analysis — the channel shows up in the geometric-adstock model with full per-campaign granularity.
Cross-session stitch — first-touch UTMs persist 365 days, so a click in March that converts in August still attributes correctly.
One classifier, every channel — tag once and the 30-platform smart-referrer classifier (including AI-chat traffic) handles the rest with no per-source config.

What native integration will add when shipped

UTM tagging gets you accurate revenue-side attribution today. Native API integration adds spend-side reconciliation and platform-side reporting depth:

Spend + revenue reconciliation for Sponsored Products that convert on Amazon (off-site, where the pixel can't reach).
Sponsored Brands and Amazon DSP cost-per-click pulled via the LWA refresh-token flow.
ASIN-level performance: which products are driving Amazon Ads ROAS vs DTC ROAS for the same SKU.
Amazon Marketing Cloud (AMC) audience joins onto first-party revenue cohorts.
Amazon Attribution tags auto-applied so DTC-landing campaigns surface in the same MER tile.

Amazon Ads specifics

Amazon Ads splits across three product surfaces — Sponsored Products, Sponsored Brands, and Amazon DSP. For DSP and Sponsored Brands campaigns that send traffic to your DTC storefront (rather than the Amazon product page), UTM-tag the destination URL. The pixel captures amzn_cid on those landing-page hits per GL#361. Amazon's affiliate-style parameters (tag=, linkCode=, ascsubtag=) are different from UTMs — the pixel preserves arbitrary URL params on the visitor_payments row, so both ride along without conflict. Sponsored Products that route through amazon.com checkout aren't pixel-attributable (the conversion happens entirely on Amazon); native LWA-refresh-token integration will pull that revenue side directly.

Frequently asked

My Sponsored Products convert on Amazon — can Admaxxer attribute them?: Not via the pixel — the conversion happens on amazon.com, off your domain. Native integration (when shipped) pulls Sponsored Products revenue directly from the Amazon Ads API via the LWA refresh-token flow. For now, those orders sit in your Amazon Seller Central reports outside the Admaxxer dashboard.
What about Amazon DSP campaigns that drive traffic to my DTC store?: Those are fully attributable today via UTMs + the amzn_cid click-ID (already captured per GL#361). UTM-tag your DSP destination URLs and the visitor_payments row picks up both campaign-level UTMs and the click-ID at payment time.
Do I need Amazon Attribution tags?: If you want spend reconciliation in Amazon Seller Central before our native integration ships — yes, set up Amazon Attribution and pass through both their tracking parameters and Admaxxer UTMs. Both can coexist on the same URL; the pixel preserves arbitrary URL params.
When will native Amazon Ads land?: Active development. The LWA refresh-token paste-token flow is the canonical auth path (matching Meta and Google's paste-token pattern). Star the integration on /integrations to be notified.

Next steps

Install the Admaxxer pixel — 35+ platforms supported.
UTM best practices — canonical UTM templates for every channel.
Revenue tracking deep-dive — how the 30-platform classifier and 365-day first-touch model work end-to-end (GL#361).
Star the Amazon Ads integration on /integrations — you'll be notified the moment native API support ships.