You can deliver location messages to a subset of your MobilePush audience by using the Android SDK. For example, when a mobile device breaks a geofence or comes into proximity of a Bluetooth beacon, the SDK can trigger a callback to your mobile app to evaluate whether to show the message.
Your app can apply criteria, including information within the MobilePush message itself, to determine whether to show the push notification, geofence message, or beacon message. Here are some use cases.
- Show the message if the user’s
my storelocation is within the geofence region.
- Show the message if the user has items in the app shopping cart and if the message has an “abandonedCart”:”true” custom key.
- Show the message only when the store is open based on the app’s store location list and the region and local time.
- Don’t show messages if the user isn’t logged in to the app.
- Show specific messages based on the user’s customer profile. For example, customers who are coffee lovers get messages about coffee, but customers who prefer pastry receive a message to “add a coffee” when they’re in the shop.
Provide an implementation of ShouldShowNotificationListener to the NotificationManager. When you implement shouldShowNotification, you can access all information about the triggering message, including Region data for geofence and beacon triggers.
To make sure that only gold loyalty-level customers receive the message in this example, the marketer sets the custom key “loyaltyLevel” to “gold” when creating the location message. Then, the message is shown only if the customer’s contact attribute is also set to “gold”.