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 campaigns with the same display event, Batch will use an automatic priority system to show first the In-App campaign that has fewer chances to be displayed, based on multiple criteria.

For example:

If two In-App campaigns are live with the "New Session" display event, the campaign 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 feature works on campaigns with an identical display event (or label).

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

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

Critical campaigns will be displayed over Important ones that will be displayed over Standard campaigns.

If multiple campaigns 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 campaign is to make it as contextualized as possible.
To make sure that the campaign 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 about 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 support@batch.com if you want to activate it!

Did this answer your question?