Best Practices

Zone Configuration

The shape and distribution of Geofences, GEOLINE™, and Beacons should suit the commercial and natural environment they relate to. There are no limitations on the number of Zones, Fences or Actions to be created for an app. We suggest having a look at our use cases to get ideas of the best solution that fit your marketing campaign.

For example, if you want to target customers that regularly visit cafes in San Francisco, rather than Geofencing all of the cafes and adding them to a single Zone, you should Geofence each cafe in its individual Zone and then build Journeys for them in Journey Builder to track your customers. You can add multiple Geofences, GEOLINE™ or Beacons in one Zone, but it should be suit your use case and help better your user engagement.

Minimum Re-trigger Time

Minimum re-trigger time (MRT) is the amount of time that needs to expire before the Zone allows a re-trigger of the actions on a device. If checkout is not enabled for a Zone, the MRT starts immediately after a user checks into a fence or beacon. For example, if you enter 10:00 as the MRT for a Zone, actions will only re-trigger when the user checks into the same Zone after 10 hours and the Zone will be not tracked for triggering for the next 10 hours. This, in turn, will help reduce battery drain.

If check-out is enabled, the MRT activates only after a device has checked out of the Fence or Beacon it checked into. For example:

  • You set the MRT to 1 hour and you trigger the Zone at 10:00 AM.
  • You stay in the Zone for 35 minutes and then check out of the Zone at 10:35 AM.
  • The Zone will be disabled for 1 hour and will be available again at 11:35 AM.

We recommend setting the MRT to as high a value as possible to avoid spamming the device with notifications and to save on battery power.

Start Active Time and End Active Time

Start Active Time and End Active Time can also be set for a Zone as a whole. These are entered as a time range and override any Time Range Conditions that have been set within Actions. The Start and End Active Times for a Zone make the Zone undetectable by a device outside of that time range, thereby substantially reducing battery consumption. Limiting the active time can lower battery consumption.

Rule Download Interval

Rule Download Interval is the minimum period of time the Bluedot Point SDK waits before downloading the new set of Zones, Geofences, GEOLINE™, Beacons, Actions, and Conditions (collectively known as the rule set). It is recommended to use the longest suitable time period depending on your data update frequency as a longer interval will save battery power. The default allocated time is 1 hour and the maximum time is 48 hours.


You can add iOS, Android, or Both type Beacons to your Bluedot Location Marketing account. In most cases, you would add a Both type Beacon with the necessary configuration details, to target users on both iOS and Android devices.

Add a Beacon as iOS or Android only if your use case requires it, as creating a Beacon as associated with a particular platform will stop it from being triggered on the other platform.  For example adding a Beacon as type Android will cause it to be not detected on iOS devices and the Zone it is added to will not trigger.

The following configuration details are required by the Bluedot Point SDK to trigger Beacons:

  • Android configuration for Beacons
    • Tx Power: Transmit power is a configuration setting common to all Bluetooth beacons. This may be represented in the documentation or determined by the configuration tool supplied by the beacon manufacturer. Specifying Tx Power allows Android devices to range for beacons at a specifically configured proximity.
    • MAC Address: A unique identifier assigned to network interfaces for identification on a physical network. An example of a MAC address is “00-15-E9-2B-99-3C”. This identifier allows an Android device to identify a Beacon.
  • iOS configuration for Beacons
    • Proximity UUID: Every Beacon conforming to the iBeacon standard has an identifier known as the Proximity UUID. An example of a Proximity UUID is “de305d54-75b4-431b-adb2-eb6b9e546014”. Given that iOS currently, has a restriction of approximately 20 Proximity UUIDs, multiple Beacons can be logically grouped by having the same Proximity UUID and differentiated using the Major and Minor values.
    • Major and Minor: Used to identify individual Beacons within a Proximity UUID group. Minor and Major are integer values between 1 and 65535.
Created by Bluedot DevOps on February 24, 2018

Start the discussion