> 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/itservices/user-interface/insight-tech-user-interface/accounts.md).
# Accounts
The Accounts page offers a comprehensive overview of individual player profiles, combining data from multiple Insight Tech Services modules into a single, navigable interface. It serves as the primary destination for monitoring player behaviour, assessing risk levels, evaluating marketing potential, and tracking responsible gaming indicators.
### What it shows
Each row in the table represents a player account that has recently been evaluated by one or more models. This page consolidates key data points such as betting history, account metadata, classification scores, and behavioural insights. Depending on the selected tab (e.g. *Risk Data*, *Marketing Data*, *Responsible Gaming*), the table layout and displayed metrics will adapt to highlight the most relevant information.
Typical columns include:
* **Account ID** and operator metadata
* **Betting activity** indicators
* **Model outputs** relevant to the selected focus
* **Category labels** based on internal classification rules
### Tabs & filters
The **Accounts** interface is divided into functional tabs aligned with core Insight Tech modules:
* **Risk Data:** Displays risk signals such as Late Bet Score, Bot Score, Marker Score, and Customer Confidence Factors.
* **Marketing Data:** Shows engagement metrics, churn risk, and player value scores.
* **Responsible Gaming:** Highlights RG flags and thresholds derived from player behaviour patterns.
Each tab includes quick filters to narrow the list by predefined categories.
---
# 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.sportradar.com/itservices/user-interface/insight-tech-user-interface/accounts.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.