Modified on: Fri, 21 Dec, 2018 at 3:37 PM
What is geofencing
It is a SDK feature that allows you to pro-actively send push message when a user enters an area that has been defined as a trigger. It requires its activation in the SDK as well as de user to Optin to the location sharing even if the app is not in foreground.
How to create a geofence campaign it on the dashboard
Import the geofences areas on the Accengage Dashboard. User guide here. Note that the geofence can take up to 1h before being eligible to trigger campaigns.
You may need these credentials to connect to our User guide:
Note that iOS and Android impose a limitation toward the number of geofences on which a device can susbribe at the same time (including geofences & iBeacons) :
> iOS : 20 areas
> Android : 100 areas
If you have more geofences than this limit for your campaigns, our SDK manages a way to update the subscribed geofences without having the user to open the app.
Common questions :
- Accengage limits the nomber of geofences to 25.000 areas maximum per apps.
- 100 goefences will represent take approximately 10Ko of data storage on the app.
Create the scheduled alarm campaign, define the geofence triggers and select the segment to target the campaign.
The user must open the app and be eligible in the segment and to the trigger to receive the alert. Therefore we recommend to anticipate the creation of the alert and the upload of the geofecence, so when your campaign goes live it will already have some eligible audience.
In order to test the campaign, you need to first activate the campaign on the dashboard, wait a few minutes, and kill > re-open the app.
In order to avoid possible double sending of the alert for one entrance, we recommend to define a minimum delay between two alert display higher than 30 minutes.
- If the radius of the geofence is too small, it may happen that the device does not have the time to notice the entrance in the area. Therefore, we recommend the following minimum radius :
- 100 m for pedestrian
- 300m for drivers
- The detection of the entrance in an area is managed by the location services of iOS & Android systems. therefore it may happen that :
- The device network can impact on the location precision
- The alert reception can be delayed if the entrance is not detected right away (up to 15 minutes delays have been observed)
- If the user is already inside the geofence area and the alert has not been triggered yet, opening the app will also act as a trigger
- The overlay of areas is possible. If the user enters a first area, then a second, he will receive 1 alert for each area (based on the capping & display delays defined in the alert settings). The minimal timing to receive an alert after entering an area is 20 seconds.
- If new areas, have been added to a campaign, the user must open the app after their upload in order to get eligible.
The Persistent messages parameter allows the alert display even if our SDK cannot contact our server in order to request the last configuration of the scheduled alarm campaign.
Please see bellow the conditions that will apply :
- It will still be mandatory to have network in order to allow the app to detect the entrance in the area.
- If the connection is lost after the entrance in the area, the persistent messages will get displayed.
- If the alert uses some dynamic fields to personalize the message, it may be possible that the displayed values will not be the latest stored in the Accengage database because of the impossibility to retrieve the server configuration.
How do Persisent Messages work
Required User permissions
In order to get eligible to this channel, the user needs to Accept the official OS permission for his location data sharing even if the app is no longer in foreground.
We recommend to trigger this popup after explaining what you'll use this data for, or only if the user visit a store locator page (or any other page using the location data).
here are the different location sharing available on iOS :
- Never : no location tracked
- Active app : only when the app is in foreground
- Always : even if the app is in background or killed (this is mandatory in order to work with beacons & geofences)
- Background modes - location service need to be ticked.
- It's activated by the mobile developer and justified to Apple
- Don't activate it for geofences otherwise the app may be rejected by Apple.
Location on iOS
In his device settings, the location service of the device must be activated in order to enable the geofencing (PRIVACY section).
When accessing the 'Share My Location' settings, we recommend to share the device location instead of the User location.
RECOMMENDATION: The location precision is higher when the Wifi is activated on the device as this feature uses Triangulation between Wifi networks.
iOS - Location Indicators
- On the nav-bar the location picto display means that the app is/was on the process of tracking location data.
- In the device settings pictos shows additional information about the tracking for each app
Location tracking was used recently
Location tracking used within the last 24 hours
Beacon monitoring is activated
iOS - Low Power mode
The Low Power mode limits the location tracking to the application in foreground. Therefor the geofence will be deactivated.
iOS - Geofence optin reminder
It may happen that the user will be reminded that an app is using the background location data. This is automatically triggered by iOS and we have no possibility to control it. iOS does not share any information on the triggers for this reminder.
Location on Android
You need to enable the High accuracy (default settings) of the Battery saving mode in order to get eligible to geofencing. It is also necessary to have data network in order to get eligible.
Android - Devices restrictions
We noticed that on some ASUS and HUAWEI devices, a system app : Auto-start Manager can block the geofence alerts even if the user is geofence optin. Generally, some brands of providers overlay can add additional constraints to the geofence alerts receptions that we may have not yet noticed.
Due to the high number of different Android brands & devices it is not possible for us to identify 100% of the possible limitations. Accengage follows and respect all the Google/Android guidelines in order to warranty a compatibility with the maximum different devices on the market.
Accengage Data policy
The storage of location data in our database needs to comply with the current legislation if the user does not open the app for some time :
- The users geofencing data will only be stored for 3 days/device maximum
- After 3 days, the geofence data will be aggregated at an app level (you'll be able to see the trafic in your geofences in our Geofence statistics (STATISTICS > GEOFENCING)
- The storage of the user last location when the app was opened will be stored and kept available for segmentation during 6 months.
Did you find it helpful?
Not what you were looking for? Try a search!