> For the complete documentation index, see [llms.txt](https://docs.crobox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.crobox.com/how-to-guides/settings/markets.md).

# Markets

Set up the countries, languages, and currencies your website serves.

A **market** is a country your website serves, with its languages, currency, and timezone. Crobox uses your markets to show visitors the right language, prices, and products, and to filter experiences and analytics by **Market**.

Open **Settings → Markets**. The overview lists each market with its **Name**, **Country**, **Language**, **Currency**, **Timezone**, and **Status**.

{% hint style="info" %}
Markets is available when multi-language support is included in your plan. Contact your Customer Success Manager to enable it.
{% endhint %}

### Add a market

{% stepper %}
{% step %}

#### Open the form

Click **New Market**.
{% endstep %}

{% step %}

#### Fill in the market

* **Country** - The country this market serves.
* **Name** - The name you'll see in the App, such as *Germany*.
* **Languages** - The languages your website offers in this country. Select more than one for a multilingual country, such as Dutch and French for Belgium.
* **Currency** - The currency prices are shown in.
* **Timezone** - The market's local timezone.
  {% endstep %}

{% step %}

#### Save

Save the market. Its languages become available to translate your experiences into, and its locales can be targeted by your product feeds.
{% endstep %}
{% endstepper %}

### Fallback market

The **Fallback Market** serves visitors who don't match any of your markets. It's marked with an icon in the **Status** column.

To change it, open the menu at the end of a market's row and select **Mark as Fallback**. Only one market can be the fallback, so the previous one stops being the fallback. Select **Remove Fallback** to unset it.

### Archive a market

Open the menu at the end of a row and select **Archive** to stop using a market without deleting it. Archived markets are hidden from the overview; turn on **Show archived markets** to see them, and select **Unarchive** to bring one back.

### Frequently asked questions

<details>

<summary>How do markets relate to my product feeds?</summary>

A feed's **Target Locales** are built from your markets, in the form Language - Country - Currency. Add a market before you target its locale in a feed. See [Setting up a Product Feed](https://docs.crobox.com/how-to-guides/product-data/setting-up-a-product-feed.md).

</details>

<details>

<summary>Why is the page called Regions in my App?</summary>

**Markets** used to be called **Regions**. It's the same page.

</details>


---

# 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.crobox.com/how-to-guides/settings/markets.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.
