> 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-create-your-first-welcome-campaign-mep.md).
# How to create your first welcome campaign? (MEP)
{% hint style="info" %}
Follow the instructions below if you are using Batch's Mobile Engagement Platform (More on the [difference between Batch's CEP and MEP](https://doc.batch.com/getting-started/other/faq/what-are-the-differences-between-batch-customer-engagement-platform-and-mobile-engagement-platform)).
{% endhint %}
The installation date is natively collected by Batch's SDK. It means you can use it to create user segments as "users who installed the app 2 days ago".
## Targeting
In the targeting block of your campaign, click on "**Add conditions**", and pick "**Installation date**".
According to your campaign's goal, set the number of days after installation ("**Installation occurred 2 days ago**" in this example):
## Timing
The advantage of these welcome campaigns is that you only have to set them up once. Then, you can let them run in the background.
In the "**When**" section of your campaign's creation form, choose the "**Recurring**" option.\
Choose a starting and ending date for the campaign:
{% hint style="info" %}
The notification needs to be **sent every day** ( = every 1 day in the form) so all new users can receive their welcoming campaigns.
{% endhint %}
You're all set! :sparkles:
---
# 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-create-your-first-welcome-campaign-mep.md?ask=&goal=
```
`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.
