Benchmark browse category marketplace is a dimension in Amazon Ads unified reporting that records which Amazon store the category behind a benchmark comparison belongs to. Amazon runs separate shops in separate countries, and each shop files its products in its own category tree. A category identifier taken from Amazon.com does not necessarily point to the same thing on Amazon.de, and the brands competing in a category in Japan are not the brands competing in Mexico. The field exists so that a benchmark figure, such as a median click-through rate, can be traced to the national market whose peer brands produced it.

It is one of seven fields in the Benchmark category of Amazon's unified reporting dimensions reference, updated on November 11, 2026. Like the other six, it has no former name in the legacy sponsored ads or Amazon DSP reports.

Where the field sits

Unified reporting, generally available in the Ads Console since June 8, 2026, sorts its 156 dimension attributes into 11 categories. The Benchmark block holds benchmark brand ID, benchmark brand name, benchmark browse category ID, benchmark browse category path, benchmark browse category level, benchmark browse category marketplace and benchmark campaign goal. All seven carry markers for DVA+, Sponsored Products, Sponsored Brands and Sponsored Display.

Amazon's reference describes six of the seven as "derived from the products promoted in the campaign", according to PPC Land's reading of the page. Benchmark campaign goal is the exception, derived from campaign goal and optimisation settings. The four browse category fields describe a single object. The ID is the category's numeric identifier, the path is its readable chain of names, the level is its depth, and the marketplace is the store whose tree the other three refer to.

None of these fields is a metric. A Support Center page updated the same day says benchmark dimensions show "the peer group for each comparison", according to PPC Land's November 12 analysis. The numbers sitting beside them are percentiles: columns such as "CTR (p25)", "CTR (p50)" and "CTR (p75)" for eight metrics, including cost per click (CPC), cost per thousand impressions (CPM) and three new-to-brand purchase measures.

Why a category needs a marketplace

The answer lies in how Amazon organises products. Every item is filed under one or more browse nodes, the categories and sub-categories of the store. Amazon's Creators API reference says its BrowseNodeInfo resource "returns BrowseNodes the item falls under and the ancestry of that browse node". Each node has an ID, a display name and a ladder of ancestors running up to a root node, which "will not have any ancestor". One of Amazon's examples shows a single book returning three nodes, and notes that a node's display name is the one used "in US marketplace".

Trees are maintained store by store. Sellers download a Browse Tree Guide for each marketplace from Seller Central, and a vendor guide from WISEPIM, updated October 11, 2026, says Amazon.com, Amazon.co.uk and Amazon.de "each have their own Browse Tree with different node IDs". Amazon's API pages do not state that rule directly, but they treat marketplace as an input: the GetBrowseNodes operation accepts a marketplace parameter and returns names "in the default language of the marketplace".

A benchmark browse category ID is therefore only half an address. The marketplace field supplies the other half.

What a marketplace is

In Amazon's seller documentation a marketplace is a country store with its own identifier. The Selling Partner API (SP-API) page on store identifiers, last modified on October 23, 2026, lists 23 marketplaceId values, from ATVPDKIKX0DER for the United States to A1PA6795UKMFR9 for Germany and A1VC38T7YXB528 for Japan. The list labels Britain as "UK" rather than the ISO code "GB".

Amazon's unified reporting reference does not show the format of the benchmark marketplace value in the material reviewed for this article. It could appear as a country code, a store name or a marketplace identifier, a distinction that matters when unified exports are joined with seller data.

Benchmarks do not cover every store. General availability on May 18, 2026 extended them to 18 markets: the United States, Canada, Mexico, Brazil, Australia, Japan, India, Germany, France, Italy, Spain, the United Kingdom, the Netherlands, Turkey, Sweden, Saudi Arabia, the United Arab Emirates and Egypt. Five stores in the SP-API list - Ireland, Belgium, South Africa, Poland and Singapore - are absent. Eligibility also varies by market. Brand Registry owners and representatives qualify everywhere, but endemic advertisers, meaning sellers and vendors of products sold on Amazon, qualify in only 15 of the 18; Amazon's announcement leaves Saudi Arabia, the United Arab Emirates and Egypt off that second list.

How the value is populated

The advertiser does not choose the marketplace. It follows from the products a campaign promotes: those products sit in a store's browse tree, the benchmark category is drawn from that tree, and the marketplace field records which store it was.

Peer selection then happens inside that market and category. Amazon's white paper, "The New Standard: How Benchmarks Are Transforming Performance Evaluation", promoted on March 27, 2026 in an article by Salena Huang, a product marketing manager, describes a system called PeerSets. It matches brands using a K-Nearest Neighbors (KNN) model on brand-level revenue and average sales price within a category, adds a large language model (LLM) assessment of competition, and requires at least five peer brands, with no single brand contributing more than 49% of the spend weight.

The market has a direct effect on whether a benchmark exists at all. A narrow category in the United States may hold dozens of advertising brands. The same category in Sweden or Egypt may hold fewer than five, in which case no benchmark is surfaced. PPC Land's June report noted that Amazon requires a minimum number of advertisers per category and market without giving a number beyond the paper's five-brand floor.

Origin and evolution

Category benchmarks at Amazon predate the field. On January 28, 2021, Amazon announced a Sponsored Brands category benchmark report comparing impressions, CTR, return on ad spend (ROAS) and advertising cost of sales (ACOS) with peers "at the median, lower performing quartile (bottom 25%), and top performing quartile (top 25%) within specific shopping categories", over a 90-day look-back window. It covered 15 marketplaces.

The current system started on November 18, 2025, when Amazon introduced self-service benchmarks through two Reporting API report types, dspBenchmarks for Amazon DSP and crossProgramBenchmarks for sponsored ads. The beta was limited to the United States, so a marketplace field would have carried one value. The move to 18 markets in May 2026 made the store a variable, and the November 11, 2026 dimensions reference is the first public listing of the field.

Why it matters

Advertisers running in several countries now see their own results and peer percentiles in one table. Unified reporting also has a separate dimension, campaign country, which Amazon defines as "the country in which the campaign is delivering". A multinational export can contain many rows whose benchmark category belongs to one store; the marketplace field is what stops a German CPC being read against a US peer set.

PPC Land found that none of Amazon's 16 recommended actions attached to benchmark metrics suggests cutting spend. Cost levels differ sharply between markets, so a benchmark drawn from the wrong store would push those recommendations in the wrong direction.

Limitations and disputes

The derivation rule is unpublished for difficult cases. Amazon does not say how the marketplace is set when a campaign promotes products listed in more than one store, or for DVA+ campaigns that serve off-Amazon inventory but promote Amazon-listed products.

Coverage statements conflict. Amazon's May 2026 announcement lists Amazon DSP, Sponsored Products, Sponsored Brands, Sponsored Display and Sponsored TV. The November 11 Support Center page lists Sponsored Products, Sponsored Brands, Streaming TV and DVA+, omitting Sponsored Display, while the dimensions reference marks the field for Sponsored Display and says Sponsored TV is not yet supported.

The method cannot be audited. Peer brands are not named, and smaller markets are more exposed to the five-brand floor, so benchmark coverage is likely thinner outside the largest stores. Amazon publishes no coverage figures by market. Migration is also incomplete: the benchmark report remains among ten report types not yet available in unified reporting, even though the benchmark dimensions are already there.

Benchmark browse category marketplace is not...

Advertised product marketplace. A unified dimension describing the store of the product an advertisement promoted, row by row. The benchmark field describes the store of the peer category.

Converted product marketplace. Amazon defines it as "the marketplace where the conversion event for the attributed product occurred". It concerns where a sale happened, not where the benchmark came from.

Campaign country. The country where a campaign delivers. A DVA+ campaign can deliver in one country while its benchmark category is drawn from a store's tree.

Marketplace in programmatic trading. In open-web advertising, "private marketplace" means an invitation-only auction. The Amazon field refers to a country store, not a trading venue.

Recent developments

On November 11, 2026, Amazon listed the Benchmark block in its dimensions reference and updated its benchmark metrics page. On November 12, its migration page confirmed that legacy report pages become read-only on December 17, 2026 and close on January 31, 2027, after which unified reporting will be the only route to these fields. Separately, Amazon has deprecated its Product Advertising API 5.0, the long-standing public reference for browse nodes, in favour of the Creators API, which now hosts that documentation.

Timeline

  • January 28, 2021 - Amazon announces a Sponsored Brands category benchmark report in 15 marketplaces.
  • November 11, 2025 - Unified reporting opens in beta.
  • November 18, 2025 - Self-service benchmarks launch in the United States through dspBenchmarks and crossProgramBenchmarks; Amazon's announcement is dated November 19.
  • March 27, 2026 - Amazon promotes its benchmarks white paper describing PeerSets, the five-brand minimum and the 49% cap.
  • May 18, 2026 - Benchmarks reach general availability in 18 markets.
  • June 8, 2026 - Unified reporting reaches general availability in the Ads Console.
  • September 29, 2026 - Amazon DSP renamed DVA.
  • October 23, 2026 - SP-API store identifiers page last modified, listing 23 marketplaces.
  • November 11, 2026 - Dimensions reference lists the seven Benchmark fields, including benchmark browse category marketplace.
  • November 12, 2026 - Migration page lists the benchmark report among ten types not yet in unified reporting.
  • December 17, 2026 - Legacy report pages scheduled to become read-only.
  • January 31, 2027 - Legacy report pages scheduled for decommissioning.

Summary

Who: Amazon Ads populates the field; brand owners, endemic advertisers, agencies and reporting tools using benchmarks for DVA+, Sponsored Products, Sponsored Brands and Sponsored Display read it.

What: A unified reporting dimension naming the Amazon store whose browse tree holds the category, and whose brands form the peer group, behind a benchmark row.

When: Benchmarks launched in the United States on November 18, 2025 and reached 18 markets on May 18, 2026; the field was first listed on November 11, 2026.

Where: In Amazon Ads unified reporting in the Ads Console and the Reporting API, across 18 benchmark markets from the United States to Egypt.

Why: Category IDs and peer brands are specific to each Amazon store, so a benchmark is only interpretable when its market is known, particularly in multinational reports and in smaller markets where the five-brand floor limits coverage.