Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Digital Matter Site
  • Contact Us

Telematics Guru - Alert Token Definitions

Written by Matthew Clark-Massera

Updated at July 17th, 2023

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Contact Support
  • Home
  • Telematics Guru
  • Alerts

Message Tokens are keywords that can be added to messages and are replaced by the appropriate, relevant text when the actual message is sent. For example: Adding the token {Event.Latitude} will result in the message containing the latitude of where the event occurred.

The tokens are not always available in every instance. The message sending service will attempt to replace the tokens as best it can, but all data is not always available. For example trip tokens for an alert that happens outside of a trip can not be replaced.

Token Name Example of Output/Notes
Asset: Name  All The 'Asset' Tokens can be activated and changed by editing the Asset details in Telematics Guru >> Manage Assets >> Edit Asset >> General & Info tabs
Asset: Description  
Asset: MSISDN  
Asset: ICCID  
Asset: Code  
Asset: Device Serial  
Asset: In Trip Verb  
Asset: Out of Trip Verb  
Asset: Asset Type  
Asset: Device Type  
Asset: Project You can assign Projects in Telematics Guru >> Assets >> Manage Assets >> Assign Asset to Project. to Create Project
Asset: Project Code  
Asset: Registration Number  
Asset: Year  
Asset: Engine Capacity  
Asset: Engine Number  
Asset: VIN  
Asset: Chassis Number  
Asset: Weight  
Asset: Colour  
Asset: Manufacturer  
Asset: Model  
Asset: Department  
Asset: Department Code  
Asset: Custom 1 These Custom fields are configurable in Telematics Guru >> Admin >> Organisation >> Edit
Asset: Custom 2  
Asset: Custom 3  
General Tokens  
General: Is Start Yes/No
General: Current Date/Current Date UTC 13/05/18
General: Current Time/Current Time UTC 13/05/18 
General: Current Date & Time/Current Date & Time UTC 13/05/18 
General: Duration (minutes) 3
General: Duration (seconds) 180
General: Analog Summary (visible on map) Whether the Analogs/Digital I/Os are visible on the Map is configurable in Manage Assets >> Edit Asset >> IO Mapping
General: Analog Summary (All) Battery Voltage: 3.4 V, External Voltage: 12.3 V
General: Digital Summary (visible on Map) Ignition: On, Door: Open
General: Digital Summary (All) Ignition: On, Door: Open, Idle Monitoring: Idle Active
Event Tokens To Enable an event, first create the event in TG >> Admin >> Events and assign to your asset in I/O Mapping tab of Edit Asset
Event: Google Maps Link  
Event: Bing Maps Link  
Event: Google Maps Image Link  
Event: Name During Office Hours Trip
Event: Altitude (feet) 114
Event: Date/ Event: Date (UTC)  01/12/2019
Event: Time/ Event: Time (UTC)  03:30
Event: Date & Time/ Event: Date & Time (UTC)  01/12/2019 12:40
Event: Date Received/ Event: Date Received (UTC)  01/12/2019 
Event: Time Received/ Event: Time Received (UTC)  01/12/2019 12:40
Event: Date & Time Received/ Event: Date & Time Received (UTC)  01/12/2019 12:40
Event: GPS Fix Yes/No
Event: Geofence Head Office
Event: Geofence Comment 123 Main Street, City
Event: Heading (degrees) 120
Event: Lattitude 34.12564
Event: Longitude 114.6589
Event: PDOP 10
Event: Position Accuracy (metres) 20
Event: Speed Accuracy (km/h) 3
Event: Speed Kmh 62
Event: Speed Mph 45
Trip Tokens  
Trip: Project Project Name & Codes are editable in Telematics Guru >> Admin >> Projects
Trip: Project Code  
Trip: Trip Type Trip types are configurable in Telematics Guru >> History >> Manage Trips >> Set Trip Type
Trip: Trip Type Code  
Trip: Driver Drivers and DriverIDs are configurable in Telematics Guru >> Admin >> Drivers
Trip: Driver Code  
Trip: Distance 67kms
Trip: Distance (miles) 110 miles
Trip: Duration 32 minutes
Trip: Duration (seconds) 1390 seconds
Trip: Start Date/Trip: Start Date (UTC)  01/12/2019 
Trip: Start Time/Trip: Start Time (utc)  12:40
Trip: Start Date & Time/Trip: Start Date & Time (UTC)  01/12/2019 12:40
Trip: Start Location  12 Main Street, Perth, Western Australia. (If inside Geofence, then Geofence will be named if Checkbox ticked in Admin >> Geofences)
Trip: Start Location Comment Head Office. Location Comment also configurable in Geofence settings
Trip: Start Latitude 34.12564
Trip: Start Longitude 114.6589
Trip: Start Odometer 56kms. Odometer settings are configurable in Telematics Guru >> Odo/Hours
Trip: Start Odometer (miles) 23 miles
Trip: Start Run Hours 13 hours. Run hours are configurable in Telematics Guru >> Odo/Hours
Trip: Start Run Hours (decimal) 321.6
Trip: Start Run Hours (seconds) 5410
Trip: Start Run Hours (time span)  2.15:01:07 
Trip: End Date/Trip: End Date (UTC)  01/12/2019 
Trip: End Time/Trip: End Time (UTC)  12:40
Trip: End Date & Time/Trip : End Date & Time (UTC)  01/12/2019 12:40
Trip: End Location 12 Main Street, Perth 
Trip: End Location Comment Head Office
Trip: End Latitude  
Trip: End Longitude  
Trip: End Odometer  
Trip: End Odometer (miles)  
Trip: End Run Hours  
Trip: End Run Hours (decimal)  
Trip: End Run Hours (seconds)  
Trip: End Run Hours (time span)  
alerts telematics

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Panic/Duress Alert on Telematics Guru
  • Telematics Guru - Alert Configuration Examples
  • How do I Activate a Movement Alert?

Subscribe to Partner News

Subscribe to our mailing list to receive Digital Matter news, product and tehnical updates, and more.

Subscribe

Copyright © Digital Matter . All Rights Reserved.

Privacy Contact Support

Knowledge Base Software powered by Helpjuice

Expand