> 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/start-here/ai-agents/analyze-podcast-performance.md).

# Analyze podcast performance

- [Summarize podcast analytics](https://docs.podigee.com/documentation/start-here/ai-agents/analyze-podcast-performance/summarize-podcast-analytics.md): Summarize a podcast's plan-visible analytics window with complete download counts.
- [Summarize episode analytics](https://docs.podigee.com/documentation/start-here/ai-agents/analyze-podcast-performance/summarize-episode-analytics.md): Summarize one episode's downloads and dimensions within its plan-visible history window.
- [Request an exact analytics date range](https://docs.podigee.com/documentation/start-here/ai-agents/analyze-podcast-performance/request-an-exact-analytics-date-range.md): Request a bounded ISO 8601 analytics period and verify the effective plan-visible range.
- [Compare an episode's first days after publication](https://docs.podigee.com/documentation/start-here/ai-agents/analyze-podcast-performance/compare-an-episodes-first-days-after-publication.md): Use the same publication-relative window to compare early episode performance.
- [Find available analytics reports](https://docs.podigee.com/documentation/start-here/ai-agents/analyze-podcast-performance/find-available-analytics-reports.md): List generated analytics reports available inside the connected Podigee account boundary.
- [Understand analytics history and completeness](https://docs.podigee.com/documentation/start-here/ai-agents/analyze-podcast-performance/understand-analytics-history-and-completeness.md): Interpret plan-visible ranges, zero-filled dates, ordering, dimensions, and missing data.


---

# 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.podigee.com/documentation/start-here/ai-agents/analyze-podcast-performance.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.