You may set up multiple in-app campaigns to run simultaneously with the same triggering event, e.g. session start. Some users might qualify for several of these campaigns, so Localytics must use prioritization logic to decide whether both messages should display sequentially and, if so, in what order.
To resolve this, Localytics will not display the messages sequentially to avoid a potentially negative user experience. Instead, we will render only the earliest-created in-app message, where "earliest" is defined as the lowest campaign ID. If the user then performs the triggering event again and still meets the qualification criteria, then the user will receive the next in-app message.