> For the complete documentation index, see [llms.txt](https://docs.abtasty.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.abtasty.com/assets-library/creating-and-managing-triggers/list-of-trigger-criteria/browser-language-criterion.md).
# Browser language criterion
Browser language is a triggering criterion that enables defining a [segment](/assets-library/creating-and-managing-segments.md).
To learn how to create a segment, please refer to this [article](/web-experimentation-and-personalization/targeting-step/how-to-create-a-segment-who-section.md).
## 📖 Definition
The Browser language triggering criterion enables you to include or exclude the browser language used by the visitors for their current session.
## 🔎 How does it work?
ABTasty gets this information from the browser’s `navigator.language` variable.
## ⚙️ Configuration
To configure the Browser language criterion, select if you want to include (`is`) or exclude (`is not`) a specific browser language.
Then, select the language you want to include or exclude (according to your previous selection) in the second drop-down list.
If you include a specific browser language, all the other languages will automatically be excluded from the targeting.
Conversely, if you exclude a specific browser language, the other languages will be included in the targeting of your campaign.
## 💡 Use case
You may want to display a message to your most engaged users who speak English. In this case, you need to display the campaign to loyal users using English as their browser language.
To do so, select `is` `English` in the Browser language triggering criteria and choose `Loyal` in the Engagement level segmentation criteria of your campaign.\
**Need additional information?**
Submit your request at
Always happy to help!
---
# 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.abtasty.com/assets-library/creating-and-managing-triggers/list-of-trigger-criteria/browser-language-criterion.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.