> For the complete documentation index, see [llms.txt](https://doc.batch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.batch.com/guides-and-best-practices/orchestration/how-to-automate-birthday-anniversary-wishes-with-a-push-notification.md).
# How to automate birthday/anniversary wishes with a push notification
Here is a step-by-step guide to create a campaign celebrating your user's birthday, or any other meaningful date.
Anniversary campaigns are an essential part of creating or improving your customer relationship. Let's go through the steps together!
{% stepper %}
{% step %}
## Targeting
First, create a new **recurring automation**.
Once you have selected the date attribut you want to base your reminder on, add the **Next Anniversary** condition:
Then you can choose the moment when the campaign should be sent to the users: on the due date, a day before (to remind them), or one day after (to extend the feel-good vibe :palm\_tree:).
Anniversary campaign **sent on the due day**:
Anniversary campaign **sent the day before**:
Anniversary campaign **sent the day after**:
{% endstep %}
{% step %}
## Timing
The second part of creating an anniversary campaign is selecting the frequency at which your campaign should be sent.
Select a **starting date** to launch the campaign, the **hour** you want your user to receive the message, and a **frequency** **of** **once a day** to not miss anyone.
{% endstep %}
{% endstepper %}
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://doc.batch.com/guides-and-best-practices/orchestration/how-to-automate-birthday-anniversary-wishes-with-a-push-notification.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
