The text is used for the following notification actions: notify by SMS or email, register event for unit, display online notification in pop-up window.
The text of a notification can be written in any language, contain any characters, words, and phrases, and be of any size. In addition, you can use tags, that is, parameters encrypted with special characters. In a message, such characters will be replaced with real values. If you want to receive a notification by SMS, do not write long messages.
The text «'%UNIT%' violated speed limitations. At '%POS_TIME%' it moved %SPEED% near '%LOCATION%'» can be transformed to «'Rover-119' violated speed limitations. At '2000-01-01 12:01:37' it moved 136 km/h near 'KU 8, Thurnau, DE'».
The units of measurement (kilometers or miles) used to decrypt the tags depend on the resource settings to which the notification belongs. The date and time format is taken from the settings of the creator of this resource.
In the text of the notification with the Send a request action type, enter the parameters of the request. When composing the text of the notification yourself, use URL encoding. Note that when using this type of notification action together with others (such as Notify by email, Notify by SMS, and so on), the same text is created for all notifications.
Below is the list of tags applicable to most types of notifications.
Internal unit ID in the system.
Current date and time.
Unit location at the moment when notification triggered.
Last known unit location. This information may be useful if there is no location information in the triggered message.
Create a locator link for the triggered unit (in parentheses indicate its lifespan in minutes, the T and G parameters to show tracks and geofences).
The smallest of the geofences where the unit is located at the moment when the notification is triggered. The tag is replaced by the name of the geofence only if the geofence and the notification have been created in the same resource.
All the geofences in which the unit is located at the moment when the notification is triggered.
Speed registered at the moment when notification triggered (is not applicable to fuel fillings or thefts).
Date and time of the triggered message, or the last message with the position (in case the triggered message has no information about the position).
Date and time of the message that triggered.
Driver's name (can be displayed only if the driver belongs to the same resource as the notification).
Trailer's name (can be displayed only if the trailer belongs to the same resource as the notification).
Unit sensors and their values (indicate a sensor mask in parentheses).
Engine hours at the moment the notification triggered.
Mileage at the moment the notification triggered.
Latitude at the moment the notification triggered (for example, N 55° 45.7530').
Longitude at the moment the notification triggered (for example, E 37° 35.2068').
Latitude without formatting.
Longitude without formatting.
Link to Google Maps with the position at the moment the notification triggered
Custom fields from the unit properties. If you leave the asterisk in parentheses, all available custom fields (including administrative ones) are shown with their values and names. To get the value of a certain field, specify its exact name in parentheses. In this case, the resulting notification text contains only the value of the specified field (without the field name).
There are also tags that are applied only to specific types of notifications.
The name of the geofence for which the notification triggered (for the notifications of the Geofence type). In the text of the Outside geofence notification, the %ZONE% tag is replaced with the names of the geofences (separated by a comma) which the unit entered at the time of the previous message and already left. If there is no previous positional message or there are no geofences that satisfy the condition described above, the text of the notification shows only the name of there tag (that is, %ZONE%).
The description of the geofence (for the Geofence notification) taken from its properties.
Name of the triggered sensor (used in notifications of various types).
Value of triggered sensor.
Name of service interval (used in maintenance notifications).
State of service interval — left/expired value (used in maintenance notifications).
All triggered sensors and their values (used in maintenance notifications).
Connection loss/Connection restored (used in connection loss notifications).
Parameter name (used in parameter control notifications).
Parameter value (used in parameter control notifications).
Text from SMS message (used in SMS control notifications).
The volume of the fuel filling or theft (for the fuel filling or fuel theft notifications).
The fuel level at the moment when the filling or theft began.
The fuel level at the moment when the filling or theft finished.
The time when the fuel filling or theft began.
The time when the fuel filling or theft finished.
The duration of the fuel filling or theft (in minutes).
Driver's code (used in notifications about drivers).
Driver's name (used in notifications about drivers).
|%DRIVER_PHONE%||Driver’s phone number (used in notifications about drivers).|
Trailer's code (used in notifications about trailers).
Trailer's name (used in notifications about trailers).
Name of another unit (used in notifications about interposition of units).
Route name (used route control notifications).
Ride execution status (used in route control notifications).
Name of the check point (used in route control notifications).
Schedule name (used in route control notifications).
Ride name (used in route control notifications).
Region (state, etc.).
City (town, etc.).
If the data is unknown, the tags are displayed as they are (not substituted with any values). The exceptions are the following tags which do not appear in the notification text when there is no data: %UNIT%, %USER%, %CURR_TIME%, %LOCATION%, %LAST_LOCATION%, %SPEED%, %POS_TIME%, %MSG_TIME%, %UNIT_GROUP%, %ENGINE_HOURS%, %MILEAGE%, %LAT%, %LON%, %LATD%, %LOND%, %GOOGLE_LINK%, %INSURANCE_CASE%, %ZONES_ALL%, %ZONE_MIN%, %UNIT_ID%, %MSG_TIME_INT%, %NOTIFICATION%, %TAG_NAME%, %TAG_ID%, %LOSE_RESTORE%, %LOCATOR_LINK%.
A tag must be marked with a percent sign on both sides. Otherwise, it is considered as plain text and is not substituted with real values.