All Collections
Best Practices & Use Cases
Best Practices
How to choose the best delivery option for my push campaign?
How to choose the best delivery option for my push campaign?

Now, Scheduled, Recurring or Trigger? Which delivery type to choose and why.

Antoine avatar
Written by Antoine
Updated over a week ago

Timing is everything.

While creating your campaign, you must decide when to send it to optimize your open rates and user engagement.

Batch allows you to:

  • Send a push campaign now

  • Send a push campaign on a specific date and time

  • Schedule a recurring campaign that will repeat at specified intervals

  • Trigger push notifications based on a user action (e.g. abandoned cart alert, etc)

Let's discover the advantage of each option:

Campaigns tab


Your campaign will be sent as soon as you click the "Save & Run" button.

Use cases: Breaking news / Last minute maintenance / etc.


Use the "Scheduled" option to send your campaign whenever you want in the future, based on your users' local time or on global time (UTC).

  • Local time: this option lets you send a push notification that will be received based on the user's timezone so at the same hour in every country. This ensures that marketing efforts target your users at a uniform time.

  • Global time: this option allows you to send a push notification to your users at a specific UTC regardless of their location. Every user will receive the message at the same time regardless of their timezone.

Use cases: Flash sales / New feature release / Specific event / etc.

Automations tab


The "Recurring" option allows you to create automated and recurring push campaigns.

  • Choose a starting date for the campaign.

  • Chose the recurrence of your campaign: on a daily, weekly, or monthly basis. For example, you can send a push notification every day, or once a week.

  • You can also define an ending date for the campaign, or let it run and manually stop it later.

  • Add a capping to manage marketing pressure and avoid targeting the same audience too many times if it's not useful.

Here is an example of a recurring campaign. On the right, you will be able to review the scheduling options you selected for your campaign.

Recurring campaigns are great to onboard your new users for instance. You can schedule several campaigns that will be sent throughout their first week after installing your app, to help them discover all the features and benefits it has to offer!

They are also a good way to announce special offers that last over a certain period, encourage them to upgrade to a newer version and more.

Use cases: Onboarding campaigns / Retention campaigns / Loyalty campaigns / etc.


The "trigger" option enables you to send a notification from one minute to several days after users have installed the app or triggered an action in the app.

Trigger campaigns are useful to manage a wide variety of use cases, from simple welcome notifications sent shortly after users install the app to advanced abandoned cart alerts.

The trigger action is the most important part of your push campaign. There are two options to choose from:

  • Installation: The "Installation" trigger is available by default. Users trigger it when they open the app for the first time.

  • Custom Events: You can choose any events that have been tagged in your app during the integration of the SDK (see more here). You can also add an event label if you want to trigger the notification on a specific action:

Then, set the timer: It's the time interval in minutes, hours, or days to wait for receiving notification. Batch will wait this amount of time from when users trigger the event. The minimum timer delay is 1 minute and the maximum timer delay is 30 days.

Finally, you can set a cancellation event. Users who trigger the cancellation event before the timer is finished won't receive the notification. You can use an event tagged in your app and select a label too.

Use the Capping and Grace period features to control marketing pressure:

  • The frequency capping allows you to limit the maximum number of times an opt-in install receives a notification. This is useful to avoid overwhelming your users with the same message.

  • Use the grace period to set a delay in minutes or hours between each notification sent to the same opt-in install. This is handy to avoid sending too many messages to users too close together.

You can schedule the start and the end date of your trigger campaign based on the Local Time or Global Time (UTC) (see above in Scheduled).

Need more help?

Feel free to send your questions or to share your use cases with your Customer Success Manager or on the live chat.

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?