All Collections
In-App Messaging
Message Edition
How does In-App automations' priority work?
How does In-App automations' priority work?

Batch allows you to prioritize your In-App automations by selecting priority levels or using our automatic system.

Antoine avatar
Written by Antoine
Updated over a week ago

The In-App message is a powerful way to reach your users contextually during their use of the application.

However, there may be times when you need to deliver an urgent or one-time message while onboarding or conversion campaigns are already in place on existing pages.

Here are more details on how Batch allows you to handle these use cases:

Batch automatic priority system

If you have created several In-App automations with the same display event, Batch will use an automatic priority system to show first the In-App automation that has fewer chances to be displayed, based on multiple criteria.

For example:

If two In-App automations are live with the "New Session" display event, the automation that will be displayed is the one with the more restricting capping, the nearest end date, the narrowest targeting (using Smart Segments), and/or the longer grace period.

In-App priority level feature

Priority-level features work on automations with an identical display event (or label).

By default, the priority is set to Standard for every In-App automation.

Select a priority level between Standard, Important and Critical when creating/editing an automation:

πŸ’‘ Critical automations will be displayed over Important ones that will be displayed over Standard automations.

If multiple automations are live with the same display event and priority level, we rely on our automatic priority system.

Best practices

The best way to create an efficient In-App automation is to make it as contextualized as possible.
To make sure that the automation will be shown to the right user at the right time, set a targeting using native and custom attributes and select a specific display event using a custom event and label.

For example, ask a non-logged user to create an account when he adds a product to his wishlist.

On the contrary, you should not ask a new user to rate your app right after he opened it for the first time or when one of the features is out of service.

Here are some best practices for the In-App priority level feature:

  • Standard-level priority should be selected for your long-term use cases: onboarding, app review, etc.

  • Important level priority should be selected for temporary campaigns: conversion or subscription campaigns, account creation, reopt-in campaign, etc.

  • Critical level priority should be selected for emergency campaigns: downtime or out-of-service messages, asking your user to update the app, etc.

πŸ’‘ Please note that this priority level feature is available on Enterprise plans and is an option for other plans.

Feel free to contact our team at if you want to activate it!

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?