> 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-podcast-analytics.md).

# Summarize podcast analytics

Summarize a podcast's plan-visible analytics window with complete download counts.

Use `analytics_summary` for a clear podcast-level result with plan window metadata.

## Before you start

* Find the podcast ID.
* Confirm that the connected user can view its analytics.
* Choose the default trailing window or a specific range.

## Summarize the podcast

1. Ask your agent for an analytics summary with the podcast ID.
2. Omit range fields for the default trailing 30-day request.
3. Use `days_offset` from 1 to 366 for another trailing window.
4. Review the requested and effective ranges in `meta.history_window`.
5. Sum `downloads.complete` across returned periods for Podigee's reported download count.
6. Review the aggregation granularity and chronological series.
7. State when the plan clamped the requested history.

## Expected result

You receive a chronological analytics series, a plan-visible effective range, and a summary that can be traced to complete download counts.

## If the effective range is shorter

Report the range that Podigee actually returned. Do not extrapolate into unavailable dates. Use the returned upgrade URL when the user wants to review a plan with more visible history.

## Next step

[Understand analytics history and completeness](/documentation/start-here/ai-agents/analyze-podcast-performance/understand-analytics-history-and-completeness.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-podcast-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.