> 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/analytics/consumption-metrics.md).

# Consumption

## **Overview**

The **Consumption** **Analytics** tab displays how audiences are using your content—primarily focusing on streams and downloads. You can see total stream counts, selected (filtered) streams, and a breakdown by DSP. This is the go-to page for a high-level view of your catalog’s performance and to identify which platforms drive the most traffic.

## **Feature Breakdown:**

* **Total Streams vs. Selected Streams**: Compare your overall performance vs. filtered views.
* **Platform Breakdown**: Apple Music, Spotify, Amazon, and more.
* **Album & Track Downloads**: Identify how many downloads occur in a given period.
* View streams and downloads by **Discovery type, Source of stream and subscription**.
* **Customize** **Date Range & Granularity**: Switch between daily, weekly, monthly, or quarterly data.
* **Exclude** platforms like TikTok.

## **Who Is It For?**

* **Label Managers** wanting to see which artists are trending upward or downward in terms of raw consumption.
* **Artist Teams** needing a quick snapshot of daily or weekly performance for promotional planning.

**Real-World Scenario #1**\
A label manager wants to measure streams after a major playlist placement. Using the **Consumption** tab, they filter by date range (the playlist’s active period) and watch for spikes in daily streams.

**Real-World Scenario #2**\
An artist checks monthly track downloads. They notice Apple Music has more album downloads than other services, prompting them to focus on Apple Music-specific promotions.

## **Key Benefits**

* Quickly see total consumption volumes and confirm promotional campaign impacts.
* Identify top-performing DSPs and plan partnerships or targeted marketing.
* Track how downloads compare to streaming consumption over time.

## **How It Works: Step by Step Guides**

1. **Open the Consumption Tab**
   * From the main Analytics menu, click **Consumption**.
2. **Apply Filters**
   * Use the **Exclude TikTok** toggle or select specific DSPs to narrow down the data.
   * Refine by date range (e.g., daily, monthly).
3. **Review the Charts**
   * Switch between line chart or bar chart for stream evolution.
   * Compare total vs. selected streams.
4. **Drill Down**
   * Expand the table below the graph to see album downloads, track downloads, or DSP-level data.

*(Link out to more detailed “How To” guides if needed.)*

## **Frequently Asked Questions**

* **Q1: Why are my downloads not showing on certain DSPs?**\
  A: Not all DSPs support downloads. Also, some might delay reporting. Double-check your date range or contact support for platform-specific delays.
* **Q2: How do I switch from daily to monthly data?**\
  A: Use the granularity drop-down in the top-right corner of the chart.

## **Keep Reading**

* How to Create Custom Data Filters
* Ingesting Data from New DSPs

## **Next Steps and Future Releases**

* **More DSP Integrations**: Expanding the list of integrated streaming platforms.


---

# 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/analytics/consumption-metrics.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.