> 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/use-insights-in-rules.md).
# Use Insights in rules
Use Insights performance data in channel rules to filter products, assign labels, and automate actions.
> #### **Who can use this feature**
>
> You need the **Core Pro** plan in your [Channable subscription](/account-billing/manage-your-subscription/channables-pricing-plans.md) to use this feature.
You can use data from an active Insights dashboard in your channel rules.
Use these rules to update items or your strategy using performance metrics, such as ACOS, average CPC, impressions, and conversions.
{% hint style="warning" %}
Available fields depend on your channel and dashboard type: Insights for Orders or Insights for Ads.
{% endhint %}
{% hint style="info" %}
Insights label names changed on July 13, 2026.
Your metrics and segmentation logic remain unchanged. If your dashboard uses labels in Rules or Mapping, your previous names remain active. [Request a switch](/manage-improve-product-data/insights/insights-for-ads/how-to-switch-to-the-new-insights-segmentation-label-names.md) to use Heroes, Sidekicks, Villains, and Zombies by December 28, 2026.
{% endhint %}
### Use Insights fields in rules
In the **Rules** step of your channel, create a new rule.
When selecting a condition (IF) or action (THEN), you'll see :chart-simple: **\[your insights dashboard name]** among other options like :file: **Project fields** and :gear-complex: **Internal fields**.
Click on :chart-simple: **\[your insights dashboard name]** to see an overview of insights performance data fields connected to that dashboard, like `cpc` , `impressions` .
Click on the fields to use them. You can use these insights fields as a [condition](/manage-improve-product-data/rules-bulk-edit-and-enrich/how-to-use-conditions-if-in-rules.md) to filter products and/or an [action](/manage-improve-product-data/rules-bulk-edit-and-enrich/how-to-use-actions-then-in-rules.md) to determine what happens to the item(s).
{% hint style="info" %}
#### **Example: *****assign a label using ROAS***
Create a rule that assigns `ROAS 500%` when `ROAS` exceeds `500`.
1. Create an `IF` condition where `ROAS` is greater than `500`.
2. Add a `THEN` action that sets `custom_label_1` to `ROAS 500%`.
3. Click **Save rule**.
4. Click **Items after** to see which items have a higher ROAS than 500.
5. Click **Run now** to run your channel.
Your channel will now set the custom label 1 for those items to ROAS 500%.
{% endhint %}
{% hint style="warning" %}
Channable applies rules from top to bottom. If you're using the data to assign labels, if several items meet the condition of that label, the latest instance will override any older instance.
{% endhint %}
### Use performance segmentation (Labelizer) labels
For Google Ads, you can use the Labelizer segmentation fields to create rules specifically for Heroes, Sidekicks, Villains, and Zombies.
See [Use Performance Segmentation in rules and Google Ads](/manage-improve-product-data/insights/insights-for-ads/use-performance-segmentation-in-rules-and-google-ads.md) for the full setup.
For examples that label, review, or exclude products, see [Performance rule recipes](/manage-improve-product-data/insights/performance-rule-recipes.md).
### Next steps
* [Use conditions (IF) in rules](/manage-improve-product-data/rules-bulk-edit-and-enrich/how-to-use-conditions-if-in-rules.md)
* [Use actions (THEN) in rules](/manage-improve-product-data/rules-bulk-edit-and-enrich/how-to-use-actions-then-in-rules.md)
* [Create and check rules](/manage-improve-product-data/rules-bulk-edit-and-enrich/using-rules.md)
* [Monitor Insights data](/manage-improve-product-data/insights/insights-troubleshooting/monitor-insights-data.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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://helpcenter.channable.com/manage-improve-product-data/insights/use-insights-in-rules.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.
