> For the complete documentation index, see [llms.txt](https://docs.aisera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aisera.com/aiseragpt/how-to-set-up-an-aiseragpt-bot/configure-an-aiseragpt-bot/create-a-universal-bot/universal-bot-analytics.md).
# Universal Bot Analytics
If you choose [Universal Bot](https://aisera.com/platform/universal-bot/) when you create an application/bot in the Aisera Gen AI Platform, you can create sub-bots that have different domains to perform specific agentic tasks.
You can select your Universal bot from the bot list for your tenant (**Settings > AiseraGPT**) and then select **Analytics > Pre-Built Analytics** to see three consolidated views of insights for the sub-bots associated with your Universal app.
The Pre-built Analytics window for the Universal app consolidates all the KPI data from the different apps related to your Universal bot, on the Requests, Sessions, and Users tabs.
Use the pull-down list to choose the bots that you want to include in the metrics data displayed on the Requests, Sessions, and User tabs.
\
You can choose to see the metrics only for your Universal bot, only for a child bot, or analytics data for all of the bots.
---
# 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.aisera.com/aiseragpt/how-to-set-up-an-aiseragpt-bot/configure-an-aiseragpt-bot/create-a-universal-bot/universal-bot-analytics.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.