iOS Features – Beacon triggering

Point SDK supports the triggering of actions by entering the proximity of a Beacon that can be configured for the following proximities:

  • Immediate
    The Beacon has to be almost touching, or within an inch of, a device for the trigger to occur.
  • Near
    The Beacon can be up to approximately 6 feet from a device for the trigger to occur.
  • Far
    The Beacon is farther than 6 feet away but still within receiving distance of the maximum range of the signal for the trigger to occur.

Requirements

Point SDK works with Beacons supporting the iBeacon standard and must be running on an iPhone 4s or later; iPads must be a 3rd generation or later or an iPad mini.

Bluetooth must be enabled on the device for Beacons to be detected; should the configuration from the backend determine there is a Beacon within range of the device and Bluetooth has not been enabled, the SDK provides the following callbacks in the BDPLocationDelegate protocol:

- (void)didStartRequiringUserInterventionForBluetooth

When a Beacon has been configured in a nearby location but the device has Bluetooth disabled, this method is called to notify the app that the user needs to enable Bluetooth for the Beacons to be detected.

- (void)didStopRequiringUserInterventionForBluetooth

Following on from a callback to the method above; if Bluetooth on the device becomes enabled or Beacons are no longer in range, then this method is called.

Maximising efficiency

To maximize the efficiency of Beacon processing in Point SDK, the physical location of Beacons should be configured; through the Point Access back-end or bulk upload through the Open API.

Custom Actions

If a zone containing a custom action is triggered by a Beacon, then the following method within your implementation of BDPLocationDelegate will be called:

- (void)didCheckIntoBeacon:inZone:atLocation:withProximity:willCheckOut:withCustomData:

This method passes back:

  • the name and description of the Beacon
  • which zone the Beacon belongs to, including:
    • the name and description of the zone
    • the id of the zone
    • a reference to all the fence and Beacon information within that zone
  • the location of the Beacon as specified on the Bluedot backend
  • the proximity at which the trigger occurred
  • whether a check out callback should be expected
  • the custom fields configured for the custom action in Point Access web interface, refer to Point Access – Setting custom data fields for how to create and edit custom data fields in Point Access web interface

If the willCheckOut flag was received true above, then a subsequent check out callback will also be made, when the device leaves the checked-in area:

- (void)didCheckOutFromBeacon:inZone:withProximity:onDate:withDuration:withCustomData:

The documentation section on the Check-out feature discusses this behavior in detail.

Created by Bluedot DevOps on June 19, 2018

Start the discussion