Mobile integrations
This reference article covers the necessary mobile integrations involved in using geofences.
Cross-platform requirements
Geofence-triggered campaigns are available on iOS and Android. To support geofences, the following must be in place:
- Your integration must support background push notifications.
- Braze geofences or location collection must be enabled.
- For devices on iOS version 11 and up, the user must allow location access always for geofencing to work.
Starting with Braze SDK version 3.6.0, Braze location collection is disabled by default. To verify that it’s enabled on Android, confirm that com_braze_enable_location_collection
is set to true
in your braze.xml
.
Geofence configuration
Latitude and longitude
The geographic center of the geofence.
Radius
The radius of the geofence in meters, measured from the geographic center. We recommend setting a minimum radius of 100–150 meters for all geofences.
Refer to these guides for more guidance based on your platform:
Cooldown
Users receive geofence-triggered notifications after performing enter or exit transitions on individual geofences. After a transition occurs, there is a pre-defined time during which that user may not perform the same transition on that individual geofence again. This time is called the “cooldown” and is pre-defined by Braze. Its main purpose is to prevent unnecessary network requests.
Technology partners
You can also leverage geofences with some of our partners, for example:
Frequently asked questions
Visit our Geofence FAQ for answers to frequently asked questions about geofences.