All Collections
Campaign Edition & Analytics
Message Edition
How to create your first push notification campaign on the dashboard?
How to create your first push notification campaign on the dashboard?

Need help creating your first push campaign? Here are all the steps you need to follow.

Antoine avatar
Written by Antoine
Updated over a week ago

Creating your first campaign on a new platform can bring on many questions, this is why we created a short guide to help go through every step of the process:

  1. Targeting: full base or fine-tuning segmentation, through native targeting or custom ones;

  2. Scheduling: sending time that can either be now, scheduled, recurrent or triggered by an action of the user;

  3. Message edition: the content of the campaign that will be sent to the user.

Step 1: Targeting

The targeting block is where you will define the segmentation of your campaign (learn more here).

By default, Batch considers that you will target your entire audience. Then, you can refine your segmentation by clicking 'Add Conditions'. From then on, you will be able to select native targeting elements (language, country, application version, etc.), but also custom ones (data specific to your app business and selected thanks to the tagging plan).

You can add up as many conditions as you want, create specific scenarios by clicking on 'And/Or', and even exclude some of your audience by selecting a condition and clicking on the 'Invert' button.

At the bottom of the block, the potential number of users who will receive the campaign will be updated accordingly in the 'Estimated Reach' section.

Step 2: Scheduling

Here's the part where you schedule your campaign (know more here).

In the Campaigns tab, you can choose to:

  • send it immediately;

  • schedule it on a specific date and time;

In the Automations tab, you can choose to:

  • schedule a recurring campaign that will repeat at specified intervals based on a starting and ending date;

  • schedule a trigger campaign that will allow you to send notifications to your users based on a specific action triggered in the app.

You can also set a "capping" to limit the number of times users receives a recurring campaign.

Note: Recurring and Trigger campaigns are a great way to set automated onboarding and retention scenarios that can be sent on a daily basis.

Step 3: Message Edition

The final part is where you compose your message (know more here).

You can personalize your notification based on custom data you use for user segmentation (e.g the first name) and also add emojis.

  • The title is optional but will help you structure your notification.
    Note: it will appear in bold, and is up to 45 characters on iOS and 40 on Android. Pay attention to always add a title on Android, otherwise, it will be your app name, which will be redundant because your app name always appears on all your notification by default.

  • The body contains a description of your message.
    Note: it is up to 180 characters on iOS and is visible on 4 lines for the push notifications displayed on the lock screen. Android displays only one line of text from the lock screen. Only 50 characters will be displayed, including spaces. The text is totally displayed once the push is unfolded. Make sure to put the main information at the beginning of your message.

  • You can also add rich content (e.g an image, a GIF, or a video) to your message in only one click.
    Note: on iOS, the image will only appear for users on OS 10 (or more). On Android, video & GIFs are not supported.

  • You can add a redirection link towards a page of your app, your website, a landing page, or on stores.
    Note: by default, without a deeplink, your push will open the app’s home.

When you're all set, you can save your campaign as a draft if you want to add modifications to it later on, or directly run it if it's ready to go!

This article belongs to Batch's FAQ. Need more help?

Find insightful articles, documentation, case & market studies, guides, and even more in our website's Resources section on and our blog.

Did this answer your question?