> 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/client-side/tag/tag-prioritization.md).
# Prioritization rules
#### Explanation
* **Before to launch the test**, The AB Tasty's Tag checks the prioritization configured by the client on [/prioritization](https://app2.abtasty.com/prioritization) the goal is for the user can discover what are the campaigns with possible overlap with the campaign then set up a configuration to prioritize some of them.
#### How tag works
1. Firstly the tag check if the user has the cookie of an MPP test or MEP test on the page, if it's there we apply these tests **no matter the priority**, otherwise we continue with the step 2.
2. The tests are sorted by level priority as set by the user. If a test hasn't priority for the tag this test is priority 0 and **we always apply these tests with priority 0**.
1. We check if the user match with the tests on priority 1, otherwise we continue to downgrade of the level until finding a match
1. Once the match is made, we do not check any more, **other unchecked tests are ignored**.
:::danger To end the process or move to another priority level, we need the tests to be accepted or rejected, if a test is in an infinite loop for example, the tag cannot move to another priority level. :::
---
# 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.abtasty.com/client-side/tag/tag-prioritization.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.
