> For the complete documentation index, see [llms.txt](https://docs.revelator.com/data-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/data-pro/guides/consumption-bi/audience-insights.md).

# Audience Insights

The Audience Insights tab is designed to surface the data describing the audience exposed to the particular asset: an artist, release, or track. Unfortunately, due to the issues regarding the listener data we've described at the beginning of this guide, listener-based audience insights are only available when at the asset granularity, which means that listeners data won't be available when filtering by DSP, source type, or country.

To account for this, audience insights are also available on a stream basis by clicking the corresponding button at the top of the audience page. Audience insights by streams allow you to get to a deeper level of granularity and review the audience profiles for specific DSPs, countries, or source types (e.g., generate the audience profile for algorithmic traffic on Spotify in the UK). Yet, the stream-based audience insights are also less precise, as they skew to more engaged parts of your audience (a single listener can, theoretically, generate a 100 streams and thus be counted 100 times when generating an audience profile)**.**

![](/files/R3MUDccjOWzCdyvfjloR)

![](/files/nYz2vWwCVYHp9eJqqJu0)

### **Audience insights by listeners**

You can easily assess the audience profile in terms of age and gender for a specific artist, release, or track. The audience profile is generated based on listeners in the last four weeks.

![](/files/xWQOd4o1t567YFbav0vS)

### **Audience insights by streams**

You can also assess the audience profiles in terms of age and gender at a deeper granularity level: filter by country, DSP, source type & more. Based on all streams generated during the selected timeframe.

* Benchmark engagements rates for different audience subsets and countries/DSP
* On-hover tooltips on the map view will allow you to quickly extract the audience profile in a specific market.

![](/files/L2XIcn4hn1kjsRjeUGOk)

![](https://lh4.googleusercontent.com/f2MNE6lb_x-5DdHaYxONCKFRMO0XCsWnBvHzqGHFHtRHmTfUzQAxlj30z6gVNUDEkroX6wbWc-O0McYf09f_nCrRIUbpIyVPtlOoTphSkFcjk8pik2o4EiShkUD6aC2otf7XpNIluicRThRnrHUrpA)


---

# 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/data-pro/guides/consumption-bi/audience-insights.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.