> 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/mcp-reference/analytics-semantics.md).

# Analytics semantics

Analytics range precedence, download fields, plan history, chronological series, and zero filling.

## Range precedence

Choose one of `from` plus `to`, `days_offset`, or episode-only `days_since_published`. The default is a trailing 30-day window ending yesterday. A request cannot exceed 366 days.

Publication-relative episode analytics start at the beginning of the publication date. When an episode has no publication date, the current implementation falls back to its creation date. Do not describe that draft result as post-publication performance.

## Plan-visible history

The response includes requested and effective ranges, retention days when bounded, unlimited and limited indicators, clamp status, earliest visible date, and an upgrade URL. Report the effective range. Do not imply access outside it.

## Download metric

Use `downloads.complete` as Podigee's reported IAB-style download count. `raw` and `total` can include partial and duplicate fetches. `streaming` counts stream starts.

## Ordering and missing dates

Non-hourly results are zero-filled for dates with no traffic and sorted chronologically. A zero is a real returned period. A missing dimension can instead reflect the current permission level or an unavailable data source.

## Aggregation

Read `aggregation_granularity` before charting or averaging. The returned timerange uses epoch seconds aligned to that granularity.


---

# 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/mcp-reference/analytics-semantics.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.