In-app messages are essential to marketers' customer experience strategy, offering rich content to users as they engage with an app in real time. These messages can be visually pleasing and attention-grabbing, supporting use cases such as sales promotions, new feature notifications, surveys, and rewards offers. In the context of a Workflow, in-app messaging can be a powerful way to shape a user's journey. This guide will explain how you can add an in-app message to your Workflow.
Starting from the Workflows campaign builder screen, select the "+" sign and you will see the node type selector. Select "Send In-App Message."
Expiration and Triggers
Since in-app messages are displayed in the app UI, many users can qualify yet never view the message if they don't launch the app. Therefore, you should set an expiration period for in-apps in Workflows.
If the message is triggered, the user will travel down the "Did" branch. If the message expires before being triggered, the user travels down the "Did Not" branch. Determine a trigger and message expiration time at the top of the builder. Triggers can be any event tagged in your app group and message expiration can be any number of days or hours.
Choose event attributes or dimensions depending on whether you would like the in-app message to display on a specific event trigger or at the beginning of a user's session. You can choose attributes or dimensions for events and dimensions for session start.
In-app message creatives can be built outside of Workflows by a developer or through the Localytics In-App Builder. Choose between "Message Builder" (or IAB) or "File Uploader" to upload the file.
All messages must eventually be uploaded in order to be sent.
Following upload be sure to select the display style of the message: Fullscreen, Center, Top Banner, or Bottom Banner.
Once you've selected triggers and expiration time and have built your in-app creative, hit "Update" and you'll be ready to go with your first Workflows in-app!
Messages are displayed on the next session after a user has passed through the qualifying node, which is the node immediately prior to the message node. The message will expire after a time set by you, remaining on the user's device until it is either triggered by the user or the user expires out of the node. Once a user has qualified for the message, it will display on the device where it is triggered regardless of which device the user qualified on.
Workflows in-app metrics that are added to the CSV export are:
- In-App Message Not Received - The number of in-app messages users missed due to the device being out of range, the SDK being improperly integrated, or not performing the trigger event before the message expired
- In-App Message Received - The number of in-app messages users triggered based on events or session start
- In-App Message Opens - The number of times users clicked calls to action within the message
The open rate, or number of in-app message opens divided by in-app messages sent, is the sole metric displayed on the in-app node.