> For the complete documentation index, see [llms.txt](https://docs.podigee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podigee.com/documentation/grow-and-monetize/analytics.md).

# Analytics

Read downloads, listeners, and subscribers, compare podcasts, export data, and get weekly reports.

Use this section to read how your podcasts and episodes perform and to understand what each number counts. It also explains how to get the data out of Podigee as CSV files or weekly reports.

Analytics is available from the top navigation for every published podcast that you own or can view. Some views depend on your plan. Each page states the plans that include the view, for example "available on Grow and above, or an older plan that includes it".

## Start with one podcast

* [Explore your podcast analytics](/documentation/grow-and-monetize/analytics/explore-your-podcast-analytics.md): open Analytics, select a podcast, and read the overview and the downloads chart.
* [Understand downloads, listeners, and subscribers](/documentation/grow-and-monetize/analytics/understand-downloads-listeners-and-subscribers.md): what the overview numbers count.
* [View downloads over time](/documentation/grow-and-monetize/analytics/view-downloads-over-time.md): date ranges and hourly to monthly steps.
* [See where and how listeners download](/documentation/grow-and-monetize/analytics/see-where-and-how-listeners-download.md): sources, platforms, apps, and countries.
* [Understand analytics history by plan](/documentation/grow-and-monetize/analytics/understand-analytics-history-by-plan.md): how far back your data reaches.

## Go deeper

* [Analyze episodes](/documentation/grow-and-monetize/analytics/analyze-episodes.md): the episode list, one episode, and the launch comparison.
* [Understand listener insights](/documentation/grow-and-monetize/analytics/understand-listener-insights.md): listener trends, listening depth, and shared audiences.
* [Compare several podcasts](/documentation/grow-and-monetize/analytics/compare-several-podcasts.md): up to ten podcasts combined or side by side.

## Get the data out

* [Export analytics as CSV](/documentation/grow-and-monetize/analytics/export-analytics-as-csv.md): save any table for the selected date range.
* [Receive weekly analytics reports](/documentation/grow-and-monetize/analytics/receive-weekly-analytics-reports.md): PDF, CSV, and ZIP reports per week.
* [Export your download history after a plan change](/documentation/grow-and-monetize/analytics/export-your-download-history-after-a-plan-change.md): the transition export for customers who moved from an older plan.

## Ask an AI agent instead

The same numbers are available to AI agents through the Podigee Model Context Protocol (MCP) server. Start with [Ask your first analytics question](/documentation/start-here/ai-agents/start-here/ask-your-first-analytics-question.md) and the [analytics semantics reference](/documentation/start-here/ai-agents/mcp-reference/analytics-semantics.md).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.podigee.com/documentation/grow-and-monetize/analytics.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.