iOS SDK version 15.1.2,
Android SDK version 14.0.1 &
Point Access UI
version 1.11.0 released.
Point Access – Setting conditions
Conditions are rules that determine when the Action should be initiated on a mobile device that checks into a Zone. While conditions themselves are not mandatory for actions to trigger on the mobile device, they improve customer experience greatly. i.e deliver a welcome message only during the opening hours of the business. More than one of the same Conditions can be configured under an action(e.g. two Date Ranges within which an Action could trigger).
To set a Condition, select the relevant Action in the slider menu, which will reveal a New Condition drop down menu. One or more Conditions can be selected from the following pre-built conditions.
- Percentage Crossed/Sequential
- Date Range
- Time Active
Once a Condition has been set, additional fields will appear to set the specific values for that Condition to be considered satisfactory (e.g. the required date, time or percentage).
These Conditions control when and how actions are triggered. For instance, a marketing message can be sent to a user within a specific date range during which the marketing campaign active as well as the within the opening hours of the business.
Figure 1. Point Access Create New Condition
Figure 2. Point Access Select Condition Type
The Percentage Crossed/Sequential Condition configures the percentage of Geofences, GEOLINE™ or Beacons in a Zone that must be crossed by an end user’s device in order for the relevant Action to be triggered.
If the Sequential checkbox is selected then the Geofences, GEOLINE™ and Beacons must be crossed in a particular sequence by the end user’s device in order for the relevant Action to be triggered. If the sequential checkbox is not selected, then the sequence is not enforced and the relevant action is triggered when the percentage of Geofences, GEOLINE™ and Beacons are crossed by the mobile device.
To enable Sequential condition, the Sequential checkbox should be selected and this will make sure the trigger will occur in the sequence/order of the fences that is set up in the Geofences sidebar as depicted in Figure 4.
This condition can be used to increase confidence that a device has traveled along a particular path or has been heading towards a specific location rather than simply being within a location.For instance, a sequence and percentage crossed can be specified to trigger actions on devices moving in a northerly direction only if the devices crossed a specific number of Geofences, GEOLINE™ and Beacons specified as a % of them.
A Time Out Period should also be set within which the percentage of Geofences, GEOLINE™ or Beacons crossed is calculated e.g. 80% of Geofences crossed in a 2 minute period. If 80% of Geofences are crossed but in more than 2 minutes, the relevant Action will not trigger.
Example working of Sequence condition:
Considering a Zone containing 5 Geofences, GEOLINE™ or BLE Beacons sequenced as 1 → 2 → 3 → 4 → 5, the table below describes the sequence at which the Geofences crossed and whether the sequence will result in a trigger. The Zone also has a Custom Action with Sequential Condition with the Percentage Crossed value set to 60%, Time Out Period set to 00:05 and the Sequential checkbox selected. This means that at least 3 of the Geofences, GEOLINE™ or Beacons have to be crossed in the specified sequence within 5 minutes for the Custom Action to be triggered.
|Sequence crossed||Trigger / No Trigger||Comments|
|1 → 2 → 3||Trigger||Fence 3 will cause the Action to be triggered.|
|2 → 1 → 3||No Trigger||As the sequence specified is not met the Action will not be triggered.|
|2 → 3 → 5||Trigger||Fence 5 will cause the Action to be triggered.|
|2 → 1 → 3 → 4||Trigger||Fence 4 will cause the Action to be triggered.|
|4 → 5 → 1||No Trigger||As the sequence specified is not met the Action will not be triggered.|
Even if a Geofence is skipped but the order is maintained to cover the percentage crossed requirement then the condition is satisfied to generate a trigger. A circular sequence like 4 → 5 → 1 is not considered as a valid order.
Figure 3: Sequential Percentage crossed condition
Figure 4: Reorder the Geofences, GEOLINE™ or Beacons
The Date Range Condition ensures that Actions will only trigger when a device enters a Geofence, crosses a GEOLINE™ or enters the proximity of a beacon within a specific date range.
Select the desired dates from the calendar that appears when the Start Date and End Date fields are selected.
The relevant Actions will only be executed within this Date Range, subject to all the other specified Conditions also being satisfied.
If this Condition is not specified, the relevant Action will trigger on any date that an end-user enters a Geofence, crosses a GEOLINE™ or enters the configured proximity of a beacon.
Figure 5: Date range condition
The Time Active Condition ensures that actions will only trigger when a device enters a Geofence, crosses a GEOLINE™ or enters the proximity of a beacon within a specific time range or ranges within a day.
The relevant Actions will only be executed within this time period, subject to all other specified Conditions also being satisfied.
If this Condition is not specified, the relevant Action will trigger at any time during a given day.
Figure 6: Time active condition
The Bearing Condition ensures that actions will only trigger when a device enters a Geofence or crosses a GEOLINE™ in the desired direction or angle. This is really great for use cases where you may want to target users who enter the geofence using the north entrance of a venue.
The minimum value of From Angle and To Angle is 0° and the maximum value that can be set is 359°. The minimum difference between the angles should be 90°.
For example, if the From Angle is set to 0° and To Angle is set to 90°, then the device should enter the Geofence while moving towards the north east direction.
To set the Action to be triggered when the device enters a Geofence or crosses a GEOLINE™ while moving in the northerly direction then set the From Angle to 270° and To Angle to 90°. This will create a condition that will trigger the zone if the device moves in the following directions, north, north-west and north-east. To trigger devices that are just moving in the north direction set the From Angle to 315° and To Angle to 45°.
If this Condition is not specified, the relevant Action will trigger when the mobile device crosses the Geofence or crosses a GEOLINE™ in any direction.
|Direction||From Angle||To Angle||Heading (Direction the device should be moving to get a trigger)|
|North||315°||45°||The device should be moving North.|
|East||45°||135°||The device should be moving East.|
|South||135°||225°||The device should be moving South.|
|West||225°||315°||The device should be moving West.|
|North-east||0°||90°||The device should be moving North-east.|
|South-east||90°||180°||The device should be moving South-east.|
|South-west||180°||270°||The device should be moving South-west.|
|North-west||270°||0°||The device should be moving North-west.|
Figure 7: Bearing condition
The Speed Condition ensures that actions will only trigger when a device enters a Geofence or crosses a GEOLINE™ at a specific speed.This is particularly useful for use cases where triggering actions in automotive scenarios on devices that are traveling in a specific travel speed range.
Select the desired speed range from speed range slider. The minimum difference in minimum and maximum speed should have is 5 meters per second.
The relevant Actions will only be executed within this Speed range, subject to all the other specified Conditions also being satisfied.
If this Condition is not specified, the relevant Action will trigger if the user walks into the Geofence or crosses a GEOLINE™ for any speed.
Figure 8: Speed condition
iOS SDK version 15.1.2,