> 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/understand-analytics-history-and-completeness.md).

# Understand analytics history and completeness

Interpret plan-visible ranges, zero-filled dates, ordering, dimensions, and missing data.

Always interpret the analytics series together with its history window and aggregation metadata.

## History window

* `requested_range` is what the client asked for.
* `effective_range` is what Podigee returned under the current plan and podcast lifetime.
* `history_limited` reports whether the plan has a finite visible history.
* `history_clamped` reports whether Podigee shortened this request.
* `history_available_from` reports the earliest currently visible instant when available.
* `upgrade_url` points to the current plan review route.

Do not imply access to dates outside the effective range.

## Download counts

Use `downloads.complete` as the download count that Podigee reports everywhere else. `raw` and `total` can include partial or duplicate fetches. `streaming` counts stream starts.

## Series completeness

Results are returned in chronological order. In daily, weekly, and monthly results, dates with no traffic are included with a complete download count of zero. This prevents averages and charts from silently excluding quiet days. Hourly results are not zero-filled.

The response can omit dimensions that the current permission level does not expose. An unavailable backend or field is not evidence of zero activity.

## Related tasks

* [Summarize podcast analytics](/documentation/start-here/ai-agents/analyze-podcast-performance/summarize-podcast-analytics.md)
* [Request an exact analytics date range](/documentation/start-here/ai-agents/analyze-podcast-performance/request-an-exact-analytics-date-range.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/understand-analytics-history-and-completeness.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.