> 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/price-benchmark-data/use-price-benchmark-data.md).

# Use Price benchmark data

Review product trends and use Price benchmark data to prioritize pricing and campaign decisions.

In Merchant Center, the price competitiveness report compares your prices with other retailers’ prices for the same products.

You can this data to:

* See Benchmark information of each product
* See Price benchmark history of each product in a graph
* Put the price benchmark labels in a supplemental source

{% hint style="info" %}
For benchmark definitions and availability, see [Price benchmark data](/css/price-benchmark-data.md). To use benchmark labels in campaigns, see [Use Price benchmark labels in Google Ads](/css/price-benchmark-data/use-price-benchmark-labels-in-google-ads.md).
{% endhint %}

***

### <i class="fa-memo-circle-check">:memo-circle-check:</i> Before you start

**You'll need**

* A Channable (CSS) Boost Pro plan

**Good to know**

* Some products do not have a benchmark. This can happen when:
  * The product is unique, so Google cannot compare it.
  * The product does not have enough ad impressions or clicks.
  * Google does not have enough competitor prices.
  * Google cannot match the product with competitor listings.
* Google mainly matches products by GTIN. When GTIN is unavailable, Google uses brand and MPN.

{% stepper %}
{% step %}

### Find products to review

1. In Channable, open the **Products** tab.
2. Review products with available Price benchmark data (indicated by a value in the **Pr. benchmark** column of the table). If there is available data, you'll see one of the following:
   * **Above benchmark:** Your price is higher than the benchmark price
   * **At Benchmark:** Your price is the same as the benchmark price (1% margin)
   * **Below Benchmark:** your price is lower than the benchmark price
   * **No Benchmark**: Not enough data available to calculate the benchmark price for this product
     {% endstep %}

{% step %}

### Review the product trend

Open a product, scroll and review the **Price benchmark** tab to compare your price with the benchmark over time.

{% hint style="success" %}
Look for persistent gaps rather than a single change. Review price changes alongside changes in performance.
{% endhint %}
{% endstep %}

{% step %}

### Choose an action

Choose how you want to use your price benchmark data.&#x20;

{% hint style="info" %}
Check out [Use Price benchmark labels in Google Ads](/css/price-benchmark-data/use-price-benchmark-labels-in-google-ads.md)to use your labels in your campaigns.
{% endhint %}

#### <i class="fa-arrow-trend-up">:arrow-trend-up:</i> Protect competitive products

For products performing well, maintain stock and protect visibility. Use the benchmark to support decisions, not replace margin targets.

#### <i class="fa-magnifying-glass-chart">:magnifying-glass-chart:</i> Investigate weaker products

For products with a persistent gap and weaker performance, review the price, margin, and conversion data. Adjust the price, reduce spend, or keep the product unchanged based on your findings.

#### <i class="fa-chart-line">:chart-line:</i> Monitor the result

After making a change, review the trend and performance again. Avoid changing several variables at once.
{% endstep %}
{% endstepper %}


---

# 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/price-benchmark-data/use-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.