> 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/help-center/podigee-hosting/why-did-i-get-a-happy-podday-email.md).

# Why did I get a "Happy PodDay" email?

The "Happy PodDay" email marks the publication anniversary of your podcast. No action is needed.

Podigee sends the email with the subject **Happy PodDay** to the podcast owner on the anniversary of the first publication of the podcast.

## When the email is sent

* The first publication of the podcast was at least two years ago.
* The podcast published an episode within the last month.
* The third anniversary has its own version of the email.

## What the email contains

The age of the podcast and the total number of complete downloads so far.

## What you need to do

Nothing. The email is informational.


---

# 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/help-center/podigee-hosting/why-did-i-get-a-happy-podday-email.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.