> For the complete documentation index, see [llms.txt](https://resources.hubz.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://resources.hubz.io/hubz-analytics/how-to-analyze-hubz-analytics-dashboard.md).

# How to Analyze Hubz Analytics Dashboard

<figure><img src="https://908288364-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl62AvrjH5McId1NOcFWb%2Fuploads%2FeSmDMmgBCfOc1BURvzPh%2FAnalytics.png?alt=media&amp;token=29cc664b-15b1-41ad-81b3-13bd61670442" alt=""><figcaption></figcaption></figure>

* Open Telegram and use the search bar to find "[Hubz](https://t.me/hubz_app_bot)".
* Select the Hubz bot from the search results.
* Enter the “/start” command in the chat with [Hubz](https://t.me/hubz_app_bot).
* Tap the "Go to Admin [Dashboard](https://dashboard.hubz.io/)" button on the chat.
* In the Admin Dashboard within the Hubz bot, select the "Analytics" tab.
* Select a group to view its specific transactions and chat information.
* In the Chain Linked Chat details, review your earnings and the number of users for each chat.
* Tap the "View Detailed Analytics" button on the bottom.
* Review the analytics for the selected group, including metrics such as the total number of clicks, wallet connects, subscribers, and joined group members.


---

# 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://resources.hubz.io/hubz-analytics/how-to-analyze-hubz-analytics-dashboard.md?ask=<question>&goal=<user_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.