Conversion source environment is a dimension in Amazon Ads unified reporting that labels the setting in which a reported off-Amazon conversion took place: a website, a mobile or connected-TV app, or an offline location such as a physical shop. It exists because Amazon now accepts conversion data from several kinds of input, and a single "off-Amazon conversions" total mixes site sign-ups, app installs and in-store purchases matched from a customer file. The dimension splits that total by where the event happened.

The field is one of seven attributes in the Conversion category of the unified report. Amazon's dimensions reference, updated on November 11, 2026, lists 156 dimension attributes across 11 categories, and the Conversion category is one of the few that is marked for every major ad product: DVA+ (Amazon's merged display, video and audio campaign type), Sponsored Products, Sponsored Brands and Sponsored Display. Its siblings are Conversion source, Conversion source owner, Conversion source attribution type, Scaled, Conversion definition (off-Amazon) and Conversion type (off-Amazon).

Where the field sits

Unified reporting is the single report builder Amazon Ads opened in beta on November 11, 2025 and made generally available on June 8, 2026. It replaces the separate report pages for sponsored ads and for Amazon DSP, which Amazon renamed DVA on September 29, 2026. Conversion source environment is a dimension, which means it adds rows rather than numbers: choosing it breaks each campaign or ad group row into one row per environment, and the off-Amazon conversion metrics are then counted within each.

The seven Conversion attributes, according to PPC Land's reading of Amazon's reference, "primarily apply to off-Amazon conversions provided through advertiser or partner integrations." On-Amazon purchases, detail page views and add-to-cart events recorded on Amazon's own store are measured by Amazon directly and do not come through an external source. For those rows, and for any ad product where a dimension does not apply, Amazon's documentation says the value appears as null.

The field's practical home is the off-Amazon side of a DVA or DVA+ campaign: an insurer counting quotes, or a mobile game counting installs. Sponsored ads carry the marker too, but they mostly send traffic to Amazon product pages, so off-Amazon rows there are rarer.

How the value gets populated

The dimension does not describe an ad impression or a device. It describes the conversion event, and its value is set when the event enters Amazon's systems. Off-Amazon events reach Amazon through four routes, each tied to an environment.

The Amazon Ad Tag (AAT) is a JavaScript tag placed on an advertiser's website. It replaced the older DSP pixels, according to Atom11, and fires page view, sign-up, add-to-cart or checkout events from the browser. Events arriving this way are web events.

The Conversions API, now succeeded by the Events API, is a server-to-server feed. Here the environment is declared explicitly in each event. Connector documentation from Amperity and Treasure Data lists a required event source field with six uppercase values: ANDROID, FIRE_TV, IOS, OFFLINE, WEBSITE and a measurement partner value. PPC Land's report on Amazon's consent rules lists the same six values for the Events API open beta.

Mobile measurement partners (MMPs) pass app installs and in-app events. Amazon added this route in Amazon DSP events manager in February 2024, naming Adjust, Kochava and Singular, and extended it to Android and Fire OS app conversions on March 18, 2024, in the US, Canada, Mexico and Brazil. Amazon's announcement noted that off-Amazon measurement "was previously limited to web and offline use cases."

Offline uploads carry in-store or call-centre transactions. LiveRamp's documentation for the file-based offline program shows hashed names, emails and addresses alongside a free-text transaction category such as "In Store", mapped to a conversion definition in events manager.

The environment value does not record which tag, API or partner carried the data. That is the job of the separate Conversion source field, which PPC Land's summary of Amazon's reference describes as "the system or integration that reported conversions to Amazon Ads."

Amazon's public help pages do not enumerate the field's values, so the mapping above is drawn from the input specifications, the only public place where environment values are listed.

A worked example

Consider a DVA+ campaign for a meal-kit brand that tracks three outcomes. Its website carries the Ad Tag for sign-ups. Its iOS and Android apps report first opens through Adjust. Its retail partner shares weekly sales files through an offline upload.

A unified report built with Campaign name and Conversion source environment returns separate rows for website, iOS, Android and offline. Suppose the campaign shows 4,000 off-Amazon conversions in total. Broken down, that might be 2,600 web sign-ups, 900 app first opens and 500 store purchases. A web sign-up is observed by a tag on the brand's own page; a store purchase is a match between a loyalty card and an Amazon account. Read as one number, the 4,000 overstates how much was directly observed.

Adding Conversion source attribution type and Scaled to the same report sharpens the picture. The app rows may reflect the MMP's attribution rules rather than Amazon's, and some offline rows may be projected from a panel rather than counted one by one. PPC Land described Scaled as indicating "whether the conversion was scaled by the source to represent a larger population."

Origin and evolution

The field is new, but the problem it addresses is older. Until 2022, Amazon DSP reported external outcomes as pixel conversions. On October 3, 2022, Amazon renamed 20 pixel metrics as "Off-Amazon" metrics, saying the data "can come from the advertiser or an Amazon-integrated partner" and would include conversions from "new, non-pixel-based interfaces."

The inputs multiplied over the following two years. Events manager was announced at unBoxed 2023 as a central place to pass back off-Amazon events. App conversions from MMPs followed in early 2024. On August 16, 2024, Amazon began modeling off-Amazon conversions for US advertisers where the link between an ad and a conversion was missing, reporting modeled and measured results together. In July 2026, Omnichannel Metrics began naming the specific retailers where DSP exposure led to offline purchases.

The Conversion category, including the environment field, appears in Amazon's dimensions reference as dated November 11, 2026. A reporting guide from Adbrew, citing a reference updated on October 23, 2026, already listed Conversion source and Conversion type (off-Amazon).

Why it matters

For advertisers using Amazon's programmatic tools to sell things Amazon does not stock, off-Amazon conversions are the outcome that justifies the budget. PPC Land's coverage of Amazon's reporting migration shows why the breakdown arrives at a pressured moment. Legacy report pages become read-only on December 17, 2026, and unmigrated reports are scheduled to be lost on January 31, 2027. Dashboards rebuilt on the unified schema can carry conversions as one total or split by environment.

The split also bears on consent. Amazon's consent requirements for the Ad Tag, Conversions API and Events API took effect on June 30, 2026 for UK and European Economic Area traffic. Web, app and offline events carry consent differently, so one environment's volume can fall alone.

Limitations and disputes

The largest limitation is documentation. Amazon's reference names the field but, on the public evidence available, does not set out its values alongside the input enums, which leaves reporting vendors to infer the mapping.

The source data is uneven. The measurement partner value has two spellings in third-party documentation: Amperity writes MEASUREMENT_PARTNER, while Treasure Data and PPC Land write MEASUREMENT_ATTRIBUTION_PARTNER. Whether partner-supplied events surface as a separate environment, or under the platform where the event occurred, is not stated.

Coverage is also patchy. MMP imports launched for Android and Fire OS in four countries, and the 2024 announcement did not include iOS, although the Events API lists IOS as a value. Modeled conversions are US only. Offline categories are free text in at least one partner program, which means "In Store" and "Offline" may be grouped under one environment while describing different things.

Nor can the field fix attribution: it says where a conversion was recorded, not whether the ad caused it.

Conversion source environment is not...

Environment (Technology category). Unified reporting has a separate DVA+-only field called Environment, listed with operating system, browser and device type. It describes where the ad was served, such as a site, app or streaming device. Conversion source environment describes where the conversion happened. A connected-TV impression can lead to a web conversion.

Conversion source. That field names the system or integration that delivered the data, such as a tag, an API or a partner. Two conversions from the same environment can arrive through different sources.

Conversion type (off-Amazon). This classifies the action itself, using categories such as sign-up, lead, checkout or off-Amazon purchase. It answers "what happened", not "where".

Amazon Attribution. Amazon's separate measurement product tracks how non-Amazon media, such as search or social ads, drives sales on Amazon. It runs in the opposite direction to off-Amazon conversion reporting.

Recent developments

The Conversion category arrived as part of Amazon's wider consolidation. On September 29, 2026 Amazon renamed Amazon DSP as DVA, and it has put a four-step DVA+ campaign builder into US closed beta, with reporting merged into the same schema. PPC Land's count of the November 11 dimensions reference, published November 12, 2026, found seven Conversion attributes marked for all four main ad products, and noted that the reference does not say which sources scale their data. The Events API, which carries the most explicit environment values, remained in open beta for UK and EEA advertisers when Amazon published its consent rules in May 2026.

Timeline

  • October 3, 2022 - Amazon DSP renames 20 pixel metrics as Off-Amazon metrics and says conversion data can come from advertisers or integrated partners.
  • 2023 - Amazon DSP events manager announced at unBoxed as a central point for off-Amazon events.
  • February 13, 2024 - Events manager extended to app campaigns through MMP integrations with Adjust, Kochava and Singular.
  • March 18, 2024 - Import of Android and Fire OS app conversions from MMPs launches in the US, Canada, Mexico and Brazil.
  • August 16, 2024 - Amazon DSP begins modeling unmeasured off-Amazon conversions for US advertisers.
  • November 11, 2025 - Unified reporting opens in beta.
  • May 2026 - Amazon publishes consent requirements for the Ad Tag, Conversions API and Events API open beta.
  • June 8, 2026 - Unified reporting becomes generally available.
  • June 30, 2026 - Consent enforcement begins for UK and EEA conversion data.
  • July 7, 2026 - Omnichannel Metrics begins breaking out offline purchases by retailer.
  • September 29, 2026 - Amazon DSP renamed DVA.
  • November 11, 2026 - Amazon's dimensions reference lists the Conversion category, including Conversion source environment.
  • December 17, 2026 - Legacy report pages scheduled to become read-only.
  • January 31, 2027 - Legacy report centres scheduled to close.

Summary

Who: Amazon Ads defines the field. Advertisers, agencies and reporting vendors use it when off-Amazon conversions arrive from the Amazon Ad Tag, the Conversions or Events API, mobile measurement partners such as Adjust, Kochava and Singular, or offline uploads.

What: A unified reporting dimension in the Conversion category that labels where an off-Amazon conversion was recorded, such as a website, an app or an offline location, so that the off-Amazon conversion total can be split by environment.

When: It appears in Amazon's dimensions reference dated November 11, 2026, following the shift from pixel metrics to off-Amazon metrics in October 2022 and the addition of app and offline inputs in 2024.

Where: In unified reports built in the Amazon Ads Console or Reporting API, marked for DVA+, Sponsored Products, Sponsored Brands and Sponsored Display, and null for on-Amazon conversions.

Why: Off-Amazon conversion totals mix events observed in different ways and with different evidence standards. Splitting them by environment shows how much of a result came from web, app or offline activity before the legacy reports close on January 31, 2027.