> 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/why-is-my-insights-dashboard-empty.md).

# Why is my Insights dashboard empty?

Fix empty Google Ads Insights dashboards by matching your product IDs.

An empty Google Ads Insights dashboard often means the product IDs in Channable don't match Google Shopping.

### Why items don't appear

Insights matches Google Ads performance data to items by their IDs. If the **Channel Unique ID** differs from the ID sent to Google Shopping, Insights cannot show those items.

### Fix the ID mismatch

1. Compare an item ID in Channable with its ID in Google Merchant Center.
2. If the IDs differ, create an [import rule](/manage-improve-product-data/rules-bulk-edit-and-enrich/rules-in-channable/import-rules-in-channable.md) that copies or transforms your item ID to match the Google Shopping ID. Import rules apply before Insights uses your product data.
3. In your Insights dashboard settings, select the matching field for **Channel Unique ID**.
4. Run your import, and then check the dashboard again.

If the IDs already match, confirm you selected the correct field for **Channel Unique ID**.

Learn more about [Insights for Google Ads](/manage-improve-product-data/insights/insights-for-ads/insights-for-google-ads.md) and [Import rules in Channable](/manage-improve-product-data/rules-bulk-edit-and-enrich/rules-in-channable/import-rules-in-channable.md).


---

# 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/why-is-my-insights-dashboard-empty.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.