> 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-it/approfondimenti/risoluzione-dei-problemi-di-insight/comprendere-le-discrepanze-tra-i-dati-di-insight-e-google-ads.md). # Comprendere le discrepanze tra i dati di Insight e Google Ads Comprendi perché l'ID di Google Merchant Center y i filtri dell'Etiqueta del feed possono causare che i dati di Insight Para differiscano de Google Ads. Quando confronti i dati di performance tra il tuo Pannello Insight en Channable y il tuo account Google Ads, potresti notare alcune discrepanze. Le discrepanze sono spesso causate da come i dati vengono filtrati en Channable. Il tuo Pannello Insight ti consente di applicare filtri specifici Para concentrarti su un sottoinsieme preciso de dati di prodotto. Quando attivi questi filtri, i dati visualizzati en Channable sono più dettagliati della vista predefinita en Google Ads. Le cause più comuni delle discrepanze sono: * **ID di Google Merchant Center** * **Paesi di destinazione dell'Etiqueta del feed** Questo accade spesso quando filtri specifici dei dati come **ID di Google Merchant Center** y **Paesi di destinazione dell'Etiqueta del feed** sono attivati en le Impostazioni avanzate de tuo Pannello Insight. Per ulteriori informazioni su come verificare i dati de tuo Pannello Insight Para il tuo account Google Ads, consulta la nostra guida dedicata. --- # 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-it/approfondimenti/risoluzione-dei-problemi-di-insight/comprendere-le-discrepanze-tra-i-dati-di-insight-e-google-ads.md?ask=&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.