# How to create your own welcome scenario?

The first moments with your users are crucial, especially after the app installation, during the first few days to engage your users. A well-designed welcome push allows you to:

* Confirm to the user that they made the right choice
* Highlight the app's key value proposition from the very first minutes
* Encourage a first action (onboarding, discovery, activation, etc.)

**⇒ Goals:** improve engagement, reduction of early churn and an increase in high-value sessions\
\
With the native *"Subscribed to mobile push notifications"  or "Subscribed to web push notifications"*  you are able to create a personalized scenario.

## 1. Create a new Omnichannel Trigger

Go to **automations** tab and create a new "**Omnichannel** **Trigger**"

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

## 2. Trigger conditions

Then, on the automation builder, select "**Event**" and pick up the native **Web or Push notifications Subscribed event**, depending on the channel you want to address (Web or Mobile push).

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

{% hint style="warning" %}
**Mobile push** and **Web push** welcome scenarios have to be created separately, as they have two distinct events.

With the **Mobile push subscription event**, you also have the possibility to add a filter based on the OS (IOS or Android), if you want to dissociate the journeys.
{% endhint %}

## 3. Add targeting conditions on installation date *(optional)*

As trigger event for notification subscriptions is available for all users,  it is possible to add a targeting condition based on the installation date to ensure that only users who have **recently installed the application** are targeted, but this is optional.

To do this, you can click on "**Add targeting**" below the trigger event and select "**App installation**" condition. Then, you can then restrict targeting to users who have installed the app within the last *x* days.

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

{% hint style="warning" %}
Note that targeting conditions are verified at **every step of the automation** *(delays, yes/no splits, messages, etc.).* Therefore, if your welcome journey includes a message at D+7, for example, you must ensure the "**App installation**" condition is set to less than or equal to 7 days (or even more) in the targeting, so that users remain eligible for all steps of the automation.
{% endhint %}

## 4. Add capping *(optional)*

{% hint style="info" %}
A **subscription event** is generated each time a device subscribes to push notifications, even if it’s the 5th time.&#x20;
{% endhint %}

Since subscription can occur multiple times - it could be relevant to add Capping to your automation.

For instance, if a user accepts to receive notifications, then opt out, and then opt back in - it is useful in certain cases to add **capping** to ensure the user does not enter the same scenario multiple times.

To apply capping at the automation level, you need to go to the **Settings** of the automation > **No Re-entry rules** and then choose the number of times a user can enter the scenario.

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

## 5. Create your journey

Next, you can **personalize** **your** **journey** by adding an initial "**Delay**" and "**Push Messages**" steps.

*In the example below: after users have opted into notifications, I want to wait 45 minutes before sending them the first push notification. Then, one day later, I want to send another notification to encourage guest users to log in, and for those who are already logged in, share a specific feature of the application. To send different message you can add a* [*Yes/no Split*](https://doc.batch.com/guides-and-best-practices/orchestration/how-to-use-the-yes-no-split-feature) *in the journey.*

Here is the documentation if you want to know more about the [steps in the automation builder](https://doc.batch.com/getting-started/features/customer-engagement-platform/orchestration/trigger-automations#adding-steps-to-the-scenario).

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

## 6. Test your push notifications

Finally, we highly recommend to always **test your notifications** to ensure they look the same on your **iOS** and **Android** **devices**. You can use the "**send test**" feature with your Installation ID or your Custom ID.

<figure><img src="/files/1SThfWP00G01Xq3E5E6i" alt=""><figcaption></figcaption></figure>

Here is the documentation to help you find your Installation ID:

* Mobile : [iOS](https://doc.batch.com/developer/technical-guides/how-to-guides/mobile/ios-specific/how-to-find-my-installation-id-on-an-ios-device), [Android](https://doc.batch.com/developer/technical-guides/how-to-guides/mobile/android-specific/how-to-find-my-installation-id-on-an-android-device)
* [Web](https://doc.batch.com/developer/technical-guides/how-to-guides/mobile/android-specific/how-to-send-a-test-notification-to-my-web-browser-on-android)<br>

When finished, you can **Save draft** if you don't want to activate it now, or **run** it immediatly ✅


---

# Agent Instructions: 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:

```
GET https://doc.batch.com/guides-and-best-practices/orchestration/how-to-create-your-own-welcome-scenario.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.