> 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/compare-an-episodes-first-days-after-publication.md).

# Compare an episode's first days after publication

Use the same publication-relative window to compare early episode performance.

Use `days_since_published` to create a consistent early-performance window.

## Before you start

* Find the episode ID and read its publication date.
* Choose a comparison window from 1 to 366 days.
* Use the same window for every episode in the comparison.

## Request the comparison window

1. Ask for episode analytics with `days_since_published` set to the chosen number.
2. Do not combine it with `from`, `to`, or `days_offset`.
3. Review the requested and effective ranges.
4. Sum `downloads.complete` within the effective range.
5. Repeat for the comparison episodes with the same number of days.
6. State any plan clamping or incomplete period before comparing totals.

## Expected result

Each published episode is measured from the start of its publication date over the same requested number of days, subject to plan-visible history.

## If the episode is a draft

Podigee falls back to the episode creation date when no publication date exists. Do not label that result as days after publication. Publish the episode first or use an exact range with a clear description.

## 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/compare-an-episodes-first-days-after-publication.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.