> 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/manage-product-and-improve-data-nl/inzichten/problemen-met-insights-oplossen/verschillen-in-gegevens-tussen-insights-en-google-ads-begrijpen.md).

# Verschillen in gegevens tussen Insights en Google Ads begrijpen

Begrijp waarom filters voor Google Merchant Center-ID en feedlabels ervoor kunnen zorgen dat Insights-data afwijkt vanuit Google Ads.

Wanneer je prestatiegegevens vergelijkt tussen je Insights-dashboard in Channable en je Google Ads-account, kun je een paar afwijkingen opmerken.

Afwijkingen worden vaak veroorzaakt door hoe gegevens in Channable worden gefilterd.

Met je Insights-dashboard kun je specifieke filters toepassen om je te richten op een precies deel van de productdata. Wanneer je deze filters inschakelt, zijn de gegevens die in Channable worden getoond gedetailleerder dan de standaardweergave in Google Ads.

De meest voorkomende oorzaken van afwijkingen zijn:

* **Google Merchant Center-ID**
* **Doellanden voor feedlabels**

Dit gebeurt vaak wanneer specifieke gegevensfilters zoals **Google Merchant Center-ID's** en **Doellanden voor feedlabels** zijn ingeschakeld in de Geavanceerde instellingen van je Insights-dashboard.

Voor meer informatie over hoe je je gegevens vanuit je Insights-dashboard Naar je Google Ads-account controleert, bekijk onze speciale handleiding.


---

# 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/manage-product-and-improve-data-nl/inzichten/problemen-met-insights-oplossen/verschillen-in-gegevens-tussen-insights-en-google-ads-begrijpen.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.
