> For the complete documentation index, see [llms.txt](https://docs.sportradar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportradar.com/ctrl/guide/configuration/tournaments-prematch/alert-factors.md).
# Alert factors
On the config overview, alert factors can be adjusted per tournament. This option allows the user to assign more weight \[0.0 - 2.0] to alerts from a preferred tournament.
A heavier weighted alert factor will act as a multiplier of the alert score of that tournament; therefore, its alerts will be given higher priority than the same alerts from a tournament with a lower factor.
After changing the alert factor assigned to a tournament, the user must press **Save** to action the change. Assigning a tournament an alert factor of 0.0 means no alerts are produced for that tournament. The alerted matches would then appear higher up or lower down in the Alerts console, sorted by alert score.
---
# 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.sportradar.com/ctrl/guide/configuration/tournaments-prematch/alert-factors.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.
