> 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/summarize-episode-analytics.md).

# Summarize episode analytics

Summarize one episode's downloads and dimensions within its plan-visible history window.

Use the episode ID to keep the analysis tied to one published item.

## Before you start

* Find and inspect the episode.
* Confirm analytics permission for its podcast.
* Choose a trailing, exact, or publication-relative range.

## Summarize the episode

1. Ask your agent for `analytics_summary` with the episode ID.
2. Omit range fields for the default trailing 30-day request.
3. Review the requested and effective history ranges.
4. Sum `downloads.complete` for the reported download total.
5. Review formats, platforms, countries, clients, and sources only when those fields are available.
6. State the aggregation granularity and coverage dates.
7. Compare the result with the episode's publication date when relevant.

## Expected result

You receive a chronological episode series and a summary limited to the dates visible under the current plan.

## If the episode is not published

A trailing or exact range can still return available data. Do not describe a draft's result as post-publication performance.

## Next step

[Compare an episode's first days after publication](/documentation/start-here/ai-agents/analyze-podcast-performance/compare-an-episodes-first-days-after-publication.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 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/summarize-episode-analytics.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.