Set optional message features

You can enable optional features in the Settings step of the In-App Automation composer. Each feature’s purpose and settings are detailed here.

Choose message priority

Assign a message priority to ensure that your audience sees the highest priority messages first.

Message priority determines the order in which messages appear to users; messages appear to the user in order from highest to lowest priority. Message priority is an integer between 1-100, where 1 is the highest priority, 100 the lowest. If a user receives two messages with the same priority, the more recently updated message appears first.

For example, you may have two messages configured to display on the next app open: an urgent account security warning, and a promotional marketing message. If you have assigned a high priority to the security warning and a lower priority to the marketing message, the higher priority message will appear first.

Use the slider to set rough priorities, or look at the number value to make fine distinctions.


Setting a message priority is useful because multiple messages can become eligible for display at one time.


Setting message priority does not guarantee one message will display before another, because all other other conditions must be met for a message to become eligible for display. Priority is available as a tiebreaker when you have multiple messages ready for display.

Override default missed behavior action

Override the project-level setting, specifying how the message is handled when audience conditions are not fully met. Select one of:

  • Cancel: The message cannot be displayed again on the device, even if the message is edited.

  • Ignore: The message will not count toward the display limit set in Repeat this message, and the waiting period will not apply. The trigger event must occur again before the message is eligible for redisplay.

  • Increment: The message will count toward the display limit set in Repeat this message, and the waiting period will apply. The trigger event must occur again before the message is eligible for redisplay.

Override message limits

Override the project-level Message LimitsLimits that cap the number of messages you can send within a specified time frame, preventing you from over-messaging your users. Message limits are set at the project level. , ensuring that your audience will receive your message even if they’ve reached the message limit.

Repeat this message

Configure the maximum number of times a message may be displayed and the minimum waiting period before it is eligible for redisplay.

Enter the maximum number of times the message may be displayed, then enter the minimum number of minutes, hours, or days that must elapse before a message becomes eligible for redisplay.


TriggersAn event that causes an In-App Automation message to appear to your audience. are not monitored while a message is ineligible for display. The trigger event must occur again after the minimum time elapses before the message will redisplay.

For example, if you set the maximum number of displays to 3 and the minimum time between displays to 1 week, the message will display a maximum of 3 times and at most once per week.


Use this option if you want your message to be eligible to be repeated (redisplayed) to your users. Redisplaying your message is useful because users can dismiss or ignore your messages.

Specify start and end dates

Set start and end dates and times during which your message can be displayed.

Click the date field and either use the date picker, or enter a date in YYYY-MM-DD format, then select the time and time zone.