> 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-es/insights/solucion-de-problemas-de-insights/comprender-las-discrepancias-de-datos-entre-insights-y-google-ads.md).

# Comprender las discrepancias de datos entre Insights y Google Ads

Descubre por qué los filtros de ID de Google Merchant Center y de etiqueta del feed pueden hacer que los datos de Insights difieran de Google Ads.

Cuando comparas los datos de rendimiento entre tu Tablero de Insights In Channable e tu Cuenta de Google Ads, puede que notes algunas discrepancias.

Las discrepancias suelen deberse a cómo se filtran los datos In Channable.

Tu Tablero de Insights te permite aplicar filtros específicos para centrarte en un subconjunto preciso di datos del producto. A continuación, al activarlos, los datos que se muestran In Channable son más granulares que la vista predeterminada In Google Ads.

Las causas más comunes de las discrepancias son:

* **ID de Google Merchant Center**
* **Países de destino de la Etichetta del feed**

Esto suele ocurrir cuando se activan filtros de datos específicos como **IDs de Google Merchant Center** e **Países de destino de la Etichetta del feed** están activados In la Configuración avanzada di tu Tablero de Insights.

Para obtener más información sobre cómo verificar tus datos da tu Tablero de Insights A tu Cuenta de Google Ads, consulta nuestra guía dedicada.


---

# 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-es/insights/solucion-de-problemas-de-insights/comprender-las-discrepancias-de-datos-entre-insights-y-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.