> For the complete documentation index, see [llms.txt](https://helpcenter.channable.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpcenter.channable.com/css/optimization-tools/price-benchmark-data.md).

# Price benchmark data

Compare your product prices to Google Shopping market benchmarks and use the data to spot pricing opportunities.

Price Benchmark data shows how your product price compares to the market average for the same product in Google Shopping Ads.

* The benchmark is a **click-weighted average price** calculated by Google across advertisers selling the same item. This means prices from ads that receive more clicks have a greater impact on the benchmark.
* With [Channable CSS Standard](/account-billing/manage-your-subscription/channables-pricing-plans/css-pricing.md), this data is available at product level and can be used for detailed analysis and campaign optimization.

#### Where does the data come from?

The data comes directly from Google Merchant Center, specifically from the [**Pricing** tab in Merchant Center Analytics](https://support.google.com/merchants/answer/13798101?hl=en). Google calculates the benchmark based on real Shopping Ads activity, using prices submitted in active auctions and the actual price shown in the ad when a user clicks.

To compare the same products across advertisers, Google matches listings primarily using the GTIN (Global Trade Item Number). If a GTIN is not available, Google uses a combination of Brand and MPN (Manufacturer Part Number) to identify the product.

#### Benchmark classifications

In the **Products** tab, at the ‘Price Benchmark’ column, each item is classified based on how your price compares to the market average in Google Shopping Ads:

* **Below:** Your price is lower than the market average
* **At:** Your price is within approximately ±1% of the benchmark
* **Above:** Your price is higher than the market average
* **n/a:** Not enough reliable data to calculate a benchmark.&#x20;

A product may show **No benchmark** because:

* there aren’t enough other advertisers selling the same item, if important identifiers like GTIN (or Brand and MPN) are missing so Google can’t properly match the product&#x20;

or&#x20;

* there isn’t enough auction or click data to calculate a reliable market average.

<figure><img src="https://825581969-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbBY5zPT0WiTFQ8xha2EA%2Fuploads%2FmGbwUQE5RR9ofrvp7Asd%2FProducts%20tab.png?alt=media&amp;token=63c73e97-3a51-4e2a-94b2-6104a3d0eb10" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://helpcenter.channable.com/css/optimization-tools/price-benchmark-data.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
