> 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/tracking-and-category-actions/set-channel-category.md).

# Set channel category

Assign categories to items for a specific advertising channel.

Use **`Set to <channel type> category`** to assign a channel category with a rule.

This action is useful for tasks such as:

* Assigning one channel category to every item.
* Assigning categories based on attributes such as gender or product type.

### Availability

These actions appear for advertising channels only:

* **`Add Google tracking`**
* **`Set to <channel type> category`**

For channels other than Amazon, both actions are always available. For Amazon, **`Set to Amazon category`** appears only when the category field uses **Internal category**.

***

## Example `Set to <channel type> category` use cases

{% hint style="info" %}

#### Tip

The [category mapping step](https://helpcenter.channable.com/manage-improve-product-data/categorize-products/manual-categorization/add-category-rule.md) is often the best option for mapping categories. Use **`Set to <channel type> category`** when you need conditional mappings or one category for all items.
{% endhint %}

### Set one category for your catalog

#### How to build a rule

* Condition: **`For all items`**
* Action: THEN **`Set to <channel type> category`** to the same channel category for every item

### Categorize clothing by gender

#### How to build a rule

* Condition: IF value(s) in `gender` **`exactly match`** `female`
* Action: THEN **`Set to <channel type> category`** to the matching clothing category


---

# 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/tracking-and-category-actions/set-channel-category.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.
