> 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/performance-rule-recipes.md).
# Performance rule recipes
Use Insights data in channel rules to label, prioritize, or exclude products based on performance.
Use these recipes to turn Insights data into repeatable channel actions.
### :memo-circle-check: Before you start
**You'll need**
* An active Insights dashboard, and use [Insights in rules](/manage-improve-product-data/insights/use-insights-in-rules.md).
**Good to know**
* It's best to avoid decisions based on too little data. Define a minimum number of clicks, impressions, orders, or days first.
* Channable applies rules from top to bottom. Place broad labels before more specific labels, and review the result after each change.
### Label high-performing products
Use a label to identify products that meet your performance target. Use the label in your channel or campaign structure.
1. In your channel's **Rules** step, add a rule.
2. Add an `IF` condition for your target metric, such as ROAS or POAS.
3. Add a `THEN` action that sets a custom label.
4. Click **Save rule**.
5. Check **Items after** before you run the channel.
{% hint style="info" %}
#### Example rule
**If** :chart-simple: `roas` `is greater or equal to` "500"
**And** :chart-simple: `clicks` `is greater or equal to` "30"
**Then** take `custom_label_1` and `set to value` "Top performers"
{% endhint %}
### Exclude products with weak results
Exclude products only after they meet a minimum data threshold. This prevents a single early click from changing your strategy.
1. In your channel's **Rules** step, add a rule.
2. Add conditions for a minimum data threshold and a weak outcome.
3. Add a `THEN` action that excludes the item.
4. Click **Save rule**.
5. Check **Items after** before you run the channel.
{% hint style="info" %}
#### Example rule
**If** :chart-simple: `clicks` `is less than` "100"
**And** :chart-simple: `conversions` `is equal to` "0"
**Then** take `all` and `exclude`
{% endhint %}
If performance for those excluded products improves, they will be included in future runs.
### Review marketplace costs
Use order-based Insights data to review listings with high costs. Combine cost, commission, shipping, and revenue where those fields are available.
1. In your channel's **Rules** step, add a rule.
2. Add a condition that identifies a cost threshold.
3. Add an action that assigns a review label.
4. Click **Save rule**.
5. Review the labeled items before excluding them.
{% hint style="info" %}
#### Example rule
**If** :chart-simple: `cost` `is greater or equal to` "10"
**Then** take `performance` and `set to value` "Needs review"
{% endhint %}
### Next steps
* [Use Insights in rules](/manage-improve-product-data/insights/use-insights-in-rules.md)
* [Insights for Ads](/manage-improve-product-data/insights/insights-for-ads.md)
* [Insights for orders](/manage-improve-product-data/insights/insights-for-orders.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/performance-rule-recipes.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.