> 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/rules-bulk-edit-and-enrich/using-rules/use-fields-in-rules.md).

# Use fields in rules

Choose project, internal, Analytics, Insights, and static values in your rules.

Rules can use product data from your project and values created in Channable.

### Project fields

Project fields contain imported product data, such as `title`, `price`, and `brand`. Use these fields to select items or store a rule result.

### Internal fields

Internal fields contain values created in Channable. For example, the `category` field contains categories assigned in the **Categories** step. Other internal fields include `cpc`.

### Analytics and Insights fields

Analytics fields come from your Google Analytics connection. Channable Insights fields come from your Channable Insights connection.

Use these fields when your rule needs performance data from those connections.

### Static values

Some channel fields let you choose a fixed value instead of a project field. For example, a channel can offer predefined payment, shipping, or return profiles.

{% hint style="info" icon="lightbulb" %}

#### Tip

Choose a project field instead of a static value when the value differs between products. Make sure the field contains accepted channel values.
{% endhint %}


---

# 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/rules-bulk-edit-and-enrich/using-rules/use-fields-in-rules.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.
