---
title: Usage Analytics
description: Use built-in Usage Analytics dashboards to understand how your deployments are used — query activity, performance, user adoption, and AI usage.
---

The **Usage Analytics** page provides a set of pre-built dashboards that show
how your deployments are used: how many queries run and how fast they return,
how effectively the cache serves them, how actively users engage with the
platform, and how much AI activity and token consumption your account generates.

Usage Analytics is itself a Cube application: your account's usage telemetry
is modeled as a curated set of views, and the pre-built dashboards are regular
Cube dashboards on top of them. You can use the same views to
[build your own dashboards](#build-your-own-dashboards).

<Note>

Available on [Premium and above plans](https://cube.dev/pricing).
Usage Analytics is only available to account administrators.

</Note>

## Pre-built dashboards

Each dashboard answers a different question about your account's usage.

<Frame>
  <img
    className="block dark:hidden"
    src="https://lgo0ecceic.ucarecd.net/70ac173a-7e90-4adc-be4e-bb72022c37e8/"
    alt="Usage Analytics overview dashboard"
  />
  <img
    className="hidden dark:block"
    src="https://lgo0ecceic.ucarecd.net/f87796f9-f005-4277-8606-147308adb4b8/"
    alt="Usage Analytics overview dashboard"
  />
</Frame>

| Dashboard | Description |
| --- | --- |
| **Overview** | High-level health and adoption at a glance: requests, error rate, cache hit rate, response time, AI activity, and top tenants. |
| **Query Activity & Performance** | Query volume by API type, latency percentiles, execution-stage breakdown, slowest queries, errors, and activity heatmap. |
| **Users & Adoption** | Active users over time, new vs. returning users, engagement frequency, seat utilization, and dormant accounts. |
| **AI & Token Tracking** | AI messages and conversations by surface, AI adoption, token consumption with estimated cost, and latency. |

## Build your own dashboards

Usage Analytics runs the full Cube application in
[Creator Mode](/embedding/iframe/creator-mode), embedded inside Cube. Beyond
the pre-built dashboards, you get the complete authoring experience: explore
the usage data, create workbooks, and assemble your own dashboards from it.

Your dashboards query the same three curated views that power the pre-built
ones. Anything you build stays private unless you share it.

| View | What it contains |
| --- | --- |
| **API Requests** | Every query hitting your deployments' data APIs, with timing, caching, errors, and the user, tenant, and deployment behind each request. |
| **AI Usage** | AI messages grouped into conversations and sessions, with context, token consumption, estimated cost, and latency. |
| **Users & Adoption** | Users and their engagement: sign-ups, active users, activity frequency, seat utilization, and dormant accounts. |

The API Requests view includes the security context behind each request, so
embedded analytics customers can slice usage by tenant — for example, to find
the heaviest tenants or compare per-tenant latency and cache efficiency.

## Query programmatically

Beyond the embedded dashboards, account administrators can mint a short-lived
Cube API token to query the same usage and billing data directly — from the
[REST API](https://cube.dev/docs/product/apis-integrations/rest-api), a BI
tool, or a script — instead of only viewing it in-app.

```bash
curl -X POST https://your-account.cubecloud.dev/api/v1/usage-analytics/token \
  -H "Authorization: Bearer <api-token>"
```

The response includes a `token`, the `apiUrl` to send it to, and an
`expiresAt` timestamp:

```json
{
  "token": "eyJhbGc...",
  "apiUrl": "https://usage-analytics.cubecloud.dev/cubejs-api/v1",
  "deploymentId": 331,
  "expiresAt": "2026-09-03T13:00:00.000Z"
}
```

The token is scoped to your account, the same way the embedded page is, so
queries only ever see your own data. It expires after **1 hour** — issue a
fresh one for each session or scheduled refresh rather than caching it.
Requires an API key belonging to an account administrator, and Usage
Analytics enabled for the account.

## Data freshness and isolation

Usage Analytics data is available on a slight delay compared to live activity.
For real-time inspection of individual queries, use
[Query History](/admin/monitoring/query-history).

Usage Analytics content is isolated from your own deployments' content: the
views and dashboards described above don't appear in your data model, and your
end users can't access them.
