Event Notifications Reference
Conditions
Emergency
When the device emergency state changes
Triggers when the device enters an emergency state or when an emergency is cancelled.
Receiving a man-down alert will also cause a device to enter an emergency state.
When the device sends an emergency message
Triggers every time an emergency message is received.
As many devices send repeated emergency messages, event notifications set up using this condition will result in multiple e-mails being sent.
When the device sends an emergency cancel message
Triggers every time an emergency cancel message is received.
When the device is in emergency mode
Typically used in conjunction with another criteria, to form a notification that only fires when the device is in emergency mode.
When an emergency is unacknowledged
Triggers when an emergency hasn't been acknowledged for the specified period.
When the device activates man down mode
Triggers when the user turns on man down detection.
Only available for devices with man-down support (i.e. the GAP Guardian app).
To raise a notification when a man-down alert occurs, use the "When the device emergency state changes" or "When the device sends an emergency message" conditions.
When the device deactivates man down mode
Triggers when the user turns off man down detection.
Only available for devices with man-down support (i.e. the GAP Guardian app)
To raise a notification when a man-down alert is cancelled, use the "When the device emergency state changes" or "When the device sends an emergency cancel message" conditions.
Check-In
When the device checks-in
Triggers every time a message deemed to constitute a check-in is received.
Every message that requires user interaction on a device is considered to be a check-in.
For example, a text message is considered a check-in.
A position report that required the device user to send via an interaction of their own making would also be considered a check-in.
An automated position report that did not require the user to interact with the device would not be considered a check-in.
Capabilities vary by device.
When the device becomes overdue
Triggers when a device enters an overdue state having previously not been overdue.
When the device becomes not overdue
Triggers when a device enters a not overdue state having previously been overdue.
When the device is overdue
Typically used in conjunction with another criteria, to form a notification that only fires when the device is overdue.
When the device starts monitoring mode
Triggers when a device enters the monitored state (having previously been not monitored).
When the device stops monitoring or checks out
Triggers when leaves the monitored state (having previously been monitored).
When the check-in schedule is disabled for the device
Triggers when monitoring (a.k.a. Monitor Me) ends (based on a check-in schedule defined via the Portal).
When a check-in request is sent to the device
Triggers when a check-in is requested via the GAP Portal.
Message
When the message text
Performs a text match on the message text.
When the message type
Performs a text match on the message type.
When the message recipients
Performs a text match on the message recipients.
When the message property
Performs a text match or numeric comparison on a specific message property.
When address
Performs a text match on the reverse geocoded address.
Requires reverse geocoding to be turned on for the tenant in question.
When speed
Performs a numeric comparison on the speed property.
When position accuracy
Triggers when the accuracy of the position supplied in the message is either high, medium or low
When altitude
Triggers when the altitude (derived from the location data) matches certain criteria (i.e. "When altitude < 50M")
When the device sends a position message
Triggers when a position report message is received.
When the device sends a message with no position
Triggers when a message is received which does not contain position data.
When the device starts moving
Triggers when a "started moving" message is received from a device.
Requires device support for sending a message when motion is detected.
This capability is currently limited to the Queclink GL300, GV500, Prime AT, PT and SPOT Trace devices.
When the device stops moving
Triggers when a "stopped moving" message is received from a device.
Requires device support for sending a message when motion is no longer detected.
This capability is currently limited to the Queclink GL300, GV500, Prime AT, PT and SPOT Trace devices.
When the device battery becomes low
Triggers when the device battery level drops below 20%.
Requires that battery data be included in the message data sent from the device.
When the device hasn't sent any message
Triggers when the device has not sent any messages within the configured period (i.e. 1 hour, 24 hours, 1 week, etc.).
Geofence
When the device enters a geofence
Triggers when a device's position indicates that it has entered a geofence (i.e. gone from outside it to inside it).
When the device leaves a geofence
Triggers when the device's position indicates that it has left a geofence (i.e. gone from inside it to outside it).
When the device crosses a geofence
Triggers when the device's position indicates that it has crossed a geofence (i.e. gone from inside it to outside it or vice versa).
Checking the "Including Possible Pass-Through" option will cause the event notification to be raised if a geofence may have been crossed based on a straight line drawn between the current and previous positions (even if no report was received within or without the geofence).
When the device is inside geofence
Typically used in conjunction with another criteria, to form a notification that only fires when the device is inside a given geofence.
When the device is outside geofence
Typically used in conjunction with another criteria, to form a notification that only fires when the device is outside a given geofence.
When the distance from point of interest
Triggers when the device is within a specific distance of a point of interest.
In the context of this rule, a point of interest is set up under Options > Points of Interest in the GAP Portal.
When the device crosses country border
Triggers when a message arrives with a different "country" value in its address data (requires reverse geocoding to be enabled).
Time
When the day is
Used in conjunction with other criteria (i.e. "When the device crosses any geofence and the day is a Saturday or Sunday...")
Ensure you set the appropriate time zone to base this calculation upon via the "Time Zone" drop-down list.
When the date is
Used in conjunction with other criteria (i.e. "When the device enters any geofence and the date is 01 September 2026...")
Ensure you set the appropriate time zone to base this calculation upon via the "Time Zone" drop-down list.
When the date is between
Used in conjunction with other criteria (i.e. "When the device is overdue and the date is between 01 January 2027 and 31 January 2027...")
Ensure you set the appropriate time zone to base this calculation upon via the "Time Zone" drop-down list.
When the time of day is
Used in conjunction with other criteria to perform a check at a set time (i.e. "When the time of day is 18:00 and the device is in any geofence...")
Ensure you set the appropriate time zone to base this calculation upon via the "Time Zone" drop-down list.
When the time of day is between
Used in conjunction with other criteria (i.e. "When the devices enters any geofence and the time of day is between 06:00 and 21:00...")
Ensure you set the appropriate time zone to base this calculation upon via the "Time Zone" drop-down list.
Last updated