> 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/monitor-insights-data.md).

# Monitor Insights data

Check data freshness, item counts, rule outcomes, and reporting differences before changing your strategy.

Review Insights data regularly before changing rules, labels, or campaign structure.

{% hint style="warning" %}

### Fact-check with Product and Engineering

Confirm dashboard refresh timing, data retention, and which failures appear in Channable. Confirm whether Channable sends notifications for delayed or failed data updates.
{% endhint %}

### Review your data

1. Open the Insights dashboard you use for decisions.
2. Check the selected date range and the latest available data.
3. Compare the number of items with your channel's expected item count.
4. Review products that moved between performance segments.
5. Check rules that excluded items or assigned labels.

### Verify unexpected changes

If results change unexpectedly, compare the same date range and filters in the source platform.

Use [Verify Insights data with Google Ads](https://helpcenter.channable.com/manage-improve-product-data/insights/insights-troubleshooting/verify-insights-data-with-google-ads.md) for Google Ads data. Use [Understanding data mismatches between Insights and Google Ads](https://helpcenter.channable.com/manage-improve-product-data/insights/insights-troubleshooting/understanding-data-mismatches-between-insights-and-google-ads.md) to review common filter differences.

### Change one thing at a time

When you update a threshold or rule, record the change and its date. Review the result after enough data has accumulated for your reporting period.

{% hint style="warning" %}

### Fact-check with Product and Engineering

Confirm recommended review intervals and the expected delay before rule changes appear in each connected channel.
{% endhint %}

### Next steps

* [Performance rule recipes](https://helpcenter.channable.com/manage-improve-product-data/insights/performance-rule-recipes.md)
* [Use Insights in rules](https://helpcenter.channable.com/manage-improve-product-data/insights/use-insights-in-rules.md)
* [Insights troubleshooting](https://helpcenter.channable.com/manage-improve-product-data/insights/insights-troubleshooting.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/monitor-insights-data.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.
