> 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/how-to-use-actions-then-in-rules/list-actions/count-occurrences-in-a-list.md).

# Count occurrences in a list

Count matching values in a list field and store the result in another field.

Use **`Count occurrences in list`** to count selected values in a list field and store the result in another field.

This action is useful for tasks such as:

* Counting selected brands, sizes, or colors.
* Creating a count you can use in another rule.

***

## Example `Count occurrences in list` use cases

### Count selected brands

#### How to build a rule

* Condition: **`For all items`**
* Action: THEN **`Count occurrences in list`**
  * Search for `Nike` count values in `brand_list` and store in `brand_count_nike`

{% hint style="info" %}

#### Important details

Matching ignores capitalization, so `nike` and `Nike` match the same value.
{% 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/how-to-use-actions-then-in-rules/list-actions/count-occurrences-in-a-list.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.
