> For the complete documentation index, see [llms.txt](https://docs.nosto.com/techdocs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nosto.com/techdocs/implementing-nosto/implement-on-your-website/manual-implementation/category-and-brand-tagging.md).
# Adding the Category/Brand Tagging
Nosto utilizes meta tags to track what category or brand a certain visitor is viewing or what page type the currently viewed page is. These values are then used for dynamic filtering for categories and brands applied through the Nosto admin UI or exposure of certain pop-up campaigns for page types.
The category tagging should be exposed whenever a user is viewing a certain category.
```js
nostojs(api => {
api.setTaggingProvider("pageType", "category")
api.setTaggingProvider("categories", ["/Mens/Jackets/Ski Jackets"])
})
```
or via DOM tagging
```markup
category
/Mens/Jackets/Ski Jackets
```
The brand tagging should be exposed whenever a user is viewing a certain brand or vendor.
```js
nostojs(api => {
api.setTaggingProvider("pageType", "category")
api.setTaggingProvider("brands", ["Acme"])
})
```
or via DOM tagging
```markup
category
Acme
```
{% hint style="info" %}
To learn more about the `api.setTaggingProvider` usage, please refer to the [official API documentation](https://nosto.github.io/nosto-js/interfaces/client.API.html#settaggingprovider).
{% endhint %}
### Tagging the categories
Categories must always be delimited by a slash. For example, `/Home/Accessories` is a valid category while `Home > Accessories` is not.
### Faceting by other attributes
With Nosto you can also expose other attributes that should be used for category/brand page filtering. For example when a user clicks on a certain color, only products with that certain color attribute should be exposed by both the category list, and Nosto Onsite Recommendations. Available values correspond to custom fields tagged as part of the [Product Tagging](/techdocs/implementing-nosto/implement-on-your-website/manual-implementation/product-tagging/default-product-tagging.md).
```js
nostojs(api => {
api.setTaggingProvider("tags", ["color: Red", "gender: Men"])
})
```
or via DOM tagging
```markup
color: Red
gender: Men
```
### Tagging the current page type
Page type tagging should be exposed whenever a user is interacting with a page so Nosto understands what kind of page this is.
```js
nostojs(api => {
api.setTaggingProvider("pageType", "category")
})
```
or via DOM tagging
```markup
category
```
Page type is optional and used mainly for triggering popups and also to understand what kind of page the user is currently interacting with. The page type must always be lowercase and the accepted values for page type are: `front`, `category`, `produc`, `cart`, `order`, `search` and `notfound`.
## Troubleshooting
Once included on all pages, you can review if the site is transmitting data using the Nosto Debug Toolbar. If you can see order contents being picked up under "Tagging" → "Category" then the category and page type tagging are correctly set up in the source code.
### Translate attribute
The translate attribute is a [HTML5 standard attribute](https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/translate) which specifies whether the value of the element and it's `Text` node children should be translated. If your tagging elements are being translated by e.g. Google Translator then this is the way to opt out elements being translated by Google and possibly other vendors.
---
# 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://docs.nosto.com/techdocs/implementing-nosto/implement-on-your-website/manual-implementation/category-and-brand-tagging.md?ask=&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.