> For the complete documentation index, see [llms.txt](https://docs.revelator.com/pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.revelator.com/pro/platform/catalog/managing-your-assets/viewing-a-release/analytics.md).

# Analytics

### The **Analytics** tab tracks performance data, offering insights into:​

* **Streams**: Number of times the release has been played.​
* **Revenue**: Income generated from the release.​
* **Geographical Distribution**: Locations where the release is most popular.​
* **Trends**: Performance trends over time.​

### **Consumption Metrics**

* Total number of streams for the release.
* Streams filtered by specific criteria.
* Streams by DSP, like Spotify and Apple Music.
* Filters:
  * Exclude platforms like TikTok.
  * Customize date ranges and time periods.
  * Granularity: Daily, weekly, monthly, or quarterly data.

### **Engagement Metrics**

* Skip Rate: Percentage of listeners who skipped the track.
* Completion Rate: Percentage of listeners who completed the track.
* Saves: How many times the track was added to libraries.
* Sub30 Streams: Streams that lasted less than 30 seconds.

### **Trends**

* Tracks performance trends with visual data over time.
* Top DSPs: Platforms with the most streams and revenue.
* Top Countries: Geographical breakdown of listener distribution.
* Top Channels: Types of content consumption like streaming or downloads.
* Top Formats: Audio formats or content types consumed.
* Top Releases: Albums and singles that perform best.

### **Revenue Metrics**

* Total Revenue: Earnings from streams and downloads.
* Total Units: Number of downloads or sales.
* Top Tracks and Releases: Highest-earning tracks and releases.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.revelator.com/pro/platform/catalog/managing-your-assets/viewing-a-release/analytics.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.