You are here:
MobilePush Beacon Scenarios
Learn more about what happens in different situations when you use beacons with MobilePush.
| Scenario | Behavior | Notes |
|---|---|---|
| When a mobile device crosses a magic fence that surrounds configured beacons... | … the known beacons and associated messages are downloaded to the device. | A magic fence tells the app which beacon GUID to download. If the device isn’t connected to the network, or if another network error occurs, the app tries to download the beacon GUID again. The interval between retry attempts increases throughout the first day and continues retrying every 24 hours thereafter. |
| When the mobile device comes within range of a known beacon... | … the app displays the message associated with that beacon. | The app respects the restrictions you place on the frequency and maximum number of times the message is sent. Set these restrictions in Marketing Cloud Engagement when you create a message. |
| When the device downloads the message... | … the app sends a “message received” event to Marketing Cloud Engagement. | View “opened” and “sent” analytics on the overview screen or the message details screen. |
| When a user directly interacts with the message by tapping or swiping on the message... | … the app sends a “message opened” event to Marketing Cloud Engagement. | View “opened” and “sent” analytics on the overview screen or the message details screen. |
| When a user reopens the app on the mobile device or leaves and reenters the magic fence... | … the app downloads any new beacon messages that are available. | ― |
| If it has been longer than 24 hours since the mobile device left and reentered the magic fence or since the user opened the app... | … the app updates the messages on the device every 24 hours, regardless of user interaction. | This behavior only occurs on iOS devices. On Android devices, messages only update one time in the first 24 hours. |
| When a user reboots the device... | … the app displays the message. | The device also must be within range of a downloaded beacon and must be set to range for beacons in the MobilePush SDK. The app shows the message as long as any message constraints, such as display one time per day, haven’t yet been met. It can take up to a minute for Android devices to display the message. |
| When a user switches airplane mode on and then off... | … the app displays the message. | This behavior only applies to iOS devices. The device also must be within range of a known beacon and must be set to range for beacons in the MobilePush SDK. The app doesn’t display the message on an Android device when it comes out of airplane mode. |
| When a beacon is turned on... | … the app displays the message. | The device must already have the message downloaded and be within the geofence for at least one minute. |
| When Bluetooth is switched off and then on... | … the app displays the message. | This behavior only applies to iOS devices. On Android devices, the app doesn’t display the message. |
| When the device is in low-power mode... | … the app displays the message. | ― |
Did this article solve your issue?
Let us know so we can improve!
