> For the complete documentation index, see [llms.txt](https://docs.nosto.com/salesforce/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/salesforce/configuring.md).
# Configuring
## Custom Preferences
Custom Preferences (Merchant Tools > Site Preferences > Custom Preferences) are used for configuring Nosto accounts and product attribute mapping.
From the configuration page you can enable / disable Nosto, map locales to Nosto accounts and define the product attribute mapping.
### Enable Nosto tagging
This site preference is to enable/ disable Nosto functionality at a site level
### Nosto Script link
Here you will configure Nosto account (or Nosto script source) for each locale. Please note that each site and each locale inside a site must have separate Nosto account.
You will map the locale to a Nosto script source in JSON format. Locale is the key and the script source. If you would for example have two locales (en\_US and en\_GB) you would need two Nosto account (example-nosto-1, example-nosto-2). The JSON would then be
```javascript
{
"en_US": "",
"en_GB": ""
}
```
### Nosto Product attribute configuration
This preference contains product attributes and mapping to Nosto product tagging. In practice the key is the field in Nosto product tagging and the value is corresponding field in Salesforce Commerce Cloud product object.
If the key is not a standard Nosto product tag the key and the value will be pushed into that custom fields. In the example mapping below `size` and the value of the size will be pushed into the custom fields.
For configurable products the same attribute mapping is applied for "main product" and variations.
```javascript
{
"description": "longDescription",
"brand": "brand",
"rating_value": "custom.ratingValue",
"size": "custom.size"
}
```
Please not that if the product tagging is not appearing on product pages it is most likely due to invalid product attribute mapping. Most common case is that some Nosto product attribute is mapped to a non-existent SFCC product attribute. If a product attribute doesn't have value the it is omitted from the Nosto product tagging.
## Nosto Brand Configuration (Category Level)
This setting is used for configuring the brand for Nosto product tagging. In other words, which category should be used a product brand in Nosto recommendations.
Navigate to the targeted catalog (Merchant Tools > Products and Catalogs > Catalogs) and click on it to open it in edit mode. You can see setting "Is Nosto Brand" under "Category Attributes" tab. You can find Nosto category settings under Category Attributes tab.
---
# 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://docs.nosto.com/salesforce/configuring.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.