> 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/for-partners/analytics-dashboard.md).

# Analytics Dashboard

A turnkey analytics product that **collects, normalizes, and visualizes** on-chain data for your **network and wallets** — fully **branded** to your domain and design. No data pipeline required — **RubyScore handles the infrastructure**.

### What you get

#### Ready-made network metrics (out of the box)

* **New users**
* **Active wallets**
* **Number of transactions**
* **Transaction volume**
* **Bridge transactions**
* **TVL** 

Or fully customizable to your specified metrics

#### Wallet metrics (core set)

* **Gas spent**
* **Amount on balance**
* **Transaction volume**
* **Number of transactions**
* **Transactions on different days / weeks / months** (temporal activity)
* **Transactions with unique contracts**

O*r extend with your own custom wallet metrics*

#### Delivery & integrations

* **Branded, interactive charts and diagrams**
* **API** for embedding metrics into your products and internal tools

### Why teams use it

* Launch your **own analytics panel** without building a data pipeline.
* Track ecosystem **health and growth** with defendable on-chain metrics.

### Get started

* **Email:** <partnerships@rubyscore.io>
* **Telegram:** <https://t.me/egormajj>


---

# 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/for-partners/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.