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

# Analytics Dashboard

A visual dashboard with metrics for networks, wallets, and campaigns. It helps measure ecosystem growth, activity quality, and the effectiveness of initiatives.

***

### How it works

* Pulls **aggregated on-chain data**: active/new wallets, volumes, and transactions.
* Provides views by **network, wallet, and campaign**, with filters for time range, chain, category, and wallet labels.
* Updates continuously as blockchains are indexed; supports **API integration**.

***

### Visual Wallet Achievements

* **Amount on balance** — current/average balance.
* **Transactions with unique contracts** — count of distinct contracts and interaction diversity.
* **Transactions on different days** — active days.
* **Transactions on different weeks** — weekly activity distribution.
* **Transactions on different months** — month-over-month stability.
* **Transaction volume** — total notional volume.
* **Number of transactions** — total transaction count.
* **Gas spent** — total gas burned.

Each user can review their wallet’s achievements and see **how to level up** their activity.


---

# 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:

```
GET https://docs.rubyscore.io/products/analytics-dashboard.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.