Send Mobile App Messages over Flow
Flow communications are used for customer journeys that include most common scenarios involving failover, automation, and geo-targeting:
- The Failover scenario provides a convenient way to send push notifications to your audience with an automatic fallback to another channel in an order defined in Flow. In this way, your message will be delivered depending on your end user`s availability.
- Automation lets you create a customer journey for your mobile app audience using push notifications based on events, tags, preferences and subscriptions changes.
- Contextual geo-targeting triggers push notifications to the mobile app users based on their live geo-data provided by mobile operating systems (iOS, Android).
The mobile app audience engagement represents a major trigger of your main points of growth. Automated communication is an essential part of that engagement, and it involves a customer journey based on customer behavior inside the mobile app. With the Flow communication, you can build a variety of customer journeys with all the available channels used by your customer.
NOTE
For the best experience with mobile apps communication in Flow, we recommend that you use the audience profiling capabilities.
Failover Scenario
A failover scenario helps you reach an audience regardless of whether your mobile app users are online or whether they have enabled their push notifications. The system will perform an automatic failover to another channel according to the order you defined in Flow.
To reach an audience using a failover scenario, you should do the following:
- Define the audience or use one of the predefined segments.
- Add the Failover element.
- Select Push as the first channel and define the message content. If needed, define the advanced options.
- Select another failover channel, for example, SMS.
- Click VALIDATE and then click LAUNCH NOW.
Automated Push
With an automation scenario, you can automatically add a person to a flow based on the mobile app users’ preferences and subscriptions. To create an automation scenario, follow the steps below:
- Log in to the web interface and navigate to Moments, click CREATE FLOW and People events as your starting point.
- Define the audience by specifying the attributes and tag values that each person`s profile needs to have to be included in the flow
NOTE
You can use different combinations of attributes and tags to make a person`s profile eligible for the Flow.
- Build the flow using the logic that you want implemented. Remember to include the name of the flow.
- Select Send Push or In-App Notification as the first channel and select whether you are creating a Push Notification or an In-App Notification
- Define the message content and specify additional conditions in the Advanced options if needed.
- Click VALIDATE and then click LAUNCH.
NOTE
Mobile app users whose specific attributes changed after the flow started will be automatically added to the flow.
Check out the Send Real-Time Travel Notifications use case.
Contextual Geotargeting
Contextual geotargeting bridges the gap between the mobile and physical worlds. It pushes notifications to the end-user's device its end users enters a predefined geolocation.
The requirements for using the Infobip contextual geotargeting:
- The mobile app has to have the Geofencing API implemented
- The mobile app user has to give the app permissions to track his/her location
To send push notifications with the contextual geotargeting activated in Flow, follow these steps:
- Log into the web interface, navigate to Moments > Create Flow.
- Define the audience or use one of the predefined audience segments.
- Add Send Push notification element and compose your message.
- Specify advanced options and geographic areas associated with the notification and its parameters.
- Click ANALYZE and then LAUNCH.
NOTE
For the better end user experience and to meet clients` expectations, the minimum radius of the geofence should be set to 100-150 meters.
Check out the Increase Store Footfall with Geo-Contextual Targeting use case. Also, be sure to check out our other use cases in the use case section od the Documenation Hub.