> 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/manage-improve-product-data/insights/insights-troubleshooting/understanding-data-mismatches-between-insights-and-google-ads.md).

# Understanding data mismatches between Insights and Google Ads

Understand why Google Merchant Center ID and feed label filters can cause Insights data to differ from Google Ads.

When you’re comparing performance data between your Insights dashboard in Channable and your Google Ads account, you might notice some discrepancies.

Mismatches are often caused by how data is filtered in Channable.

Your Insights dashboard allows you to apply specific filters to focus on a precise subset of product data. When you enable these filters, the data displayed in Channable is more granular than the default view in Google Ads.

The most common causes for discrepancies are:

* **Google Merchant Center ID**
* **Feed label target countries**

This often happens when specific data filters like **Google Merchant Center IDs** and **Feed label target countries** are enabled in the Advanced Settings of your Insights dashboard.

For more information on how to verify your data from your Insights dashboard to your Google Ads account, check out our dedicated guide.


---

# 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/manage-improve-product-data/insights/insights-troubleshooting/understanding-data-mismatches-between-insights-and-google-ads.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.