> For the complete documentation index, see [llms.txt](https://guides.getalby.com/creators/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.getalby.com/creators/value-for-value-podcaster-guide/7.-analyze-listener-data.md).

# 7. Analyze listener data

Today as a podcaster you can only analyze WHAT episodes your listeners are consuming. The reason is that you can only measure downloads and listeners for each episode of an RSS-based podcast. But you do not know HOW your listeners are consuming one specific episode of your podcast.&#x20;

As you start experimenting with Value for Value, looking for insights and patterns in your analytics will help you identify what's working and what's not. That´s why we created [SATurn](https://saturn.fly.dev/), a boostergram viewer and analytics app for your [Alby podcaster wallet](https://getalby.com/podcast-wallet).&#x20;

<figure><img src="/files/cZVD8Ray25JZN9rYk7EQ" alt=""><figcaption><p>SATurn app, an analytics dashboard for your Alby podcaster wallet</p></figcaption></figure>

SATurn allows you to get insights into your podcast’s performance. It helps you to understand HOW people are listening to your shows and episodes of any Value for Value podcast player and which episodes resonate best with your audience: You learn if listeners are skipping over your episode intro or your second mid-roll or what sections they like in particular.

<figure><img src="/files/ybmyUphAhF34RJGkXnHV" alt=""><figcaption><p>The episode view allows you to see listening stats along the timeline of your podcast.</p></figcaption></figure>

SATurn is in alpha and available under: <https://saturn.fly.dev/>

If you are using the Alby podcaster wallet, go to SATurn and connect your Alby account.&#x20;


---

# 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://guides.getalby.com/creators/value-for-value-podcaster-guide/7.-analyze-listener-data.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.
