> 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

Anniversary campaigns are an essential part of creating or improving your customer relationship. Let's go through the steps together! 

{% stepper %}
{% step %}

## Targeting <a href="#how-to-set-up-an-anniversary-campaign" id="how-to-set-up-an-anniversary-campaign"></a>

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:

<figure><img src="/files/x1ASvzHBG1vD7wJ7O26T" alt=""><figcaption></figcaption></figure>

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**:

<figure><img src="/files/ubEf06roXKBqGDuCJvih" alt=""><figcaption></figcaption></figure>

Anniversary campaign **sent the day before**:

<figure><img src="/files/bgsAzKlP7B5ZR1CKlBfk" alt=""><figcaption></figcaption></figure>

Anniversary campaign **sent the day after**:

<figure><img src="/files/f6yplbgw0IDflpofrMqy" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

## Timing

The second part of creating an anniversary campaign is selecting the frequency at which your campaign should be sent.

<figure><img src="/files/K62byfiWWxu57Tt7hAwi" alt=""><figcaption></figcaption></figure>

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 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://doc.batch.com/guides-and-best-practices/orchestration/how-to-automate-birthday-anniversary-wishes-with-a-push-notification.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.