Skip to main content
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.
Available on Premium and above plans. Usage Analytics is only available to account administrators.

​
Pre-built dashboards

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

​
Build your own dashboards

Usage Analytics runs the full Cube application in 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. 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.

​
Querying usage data from your own tools

To pull your account’s usage and billing data into an external BI tool instead of (or in addition to) using the console, request a scoped Cube API token:
The returned token is scoped to your account’s Usage Analytics views (the same ones described in Build your own dashboards) and can be used to authenticate Core Data API requests against those views from tools like Power BI. Only account administrators can request this token.

​
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. 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.