> 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/request-an-exact-analytics-date-range.md).

# Request an exact analytics date range

Request a bounded ISO 8601 analytics period and verify the effective plan-visible range.

Use `from` and `to` together when reporting needs fixed calendar boundaries.

## Before you start

* Choose a podcast ID or episode ID, not both.
* Choose dates or date-times in the intended time zone.
* Keep the requested period at 366 days or fewer.

## Request the range

1. Set both `from` and `to` as ISO 8601 dates or date-times.
2. Confirm that `from` is before or equal to `to`.
3. Do not combine the pair with `days_offset` or `days_since_published`.
4. Request the analytics summary.
5. Compare `requested_range` with `effective_range`.
6. Report the effective range and whether `history_clamped` is true.

A date such as `2026-08-01` starts at the beginning of that date in Podigee's application time zone. Use an explicit offset when an exact instant matters.

## Expected result

Podigee returns analytics for the requested period or the plan-visible portion of it.

## If the request is rejected

Provide both boundaries, remove conflicting offset fields, correct the ISO 8601 value, or shorten the range to 366 days or fewer.

## 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/request-an-exact-analytics-date-range.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.