Integrating Geotab devices with Telematics Guru
Table of Contents
Geotab GO device data, including the GO9, can be viewed on our Telematics Guru platform, with data being pulled directly from Geotab’s servers.
Not all features or records have been integrated in the TG platform. Only the LogRecord and DeviceStatusInfo data payloads are being received by TG.
All data records will appear as Heartbeats on the TG platform.
Critical Alerts like Accident and Rollover Notifications must be configured and sent out directly from the Geotab platform, as the accident/rollover detection data is not received by TG.
The following information is required to configure the Geotab Integration:
- Geotab Server (default is my.geotab.com)
- Geotab Database Name
- Geotab Account Username
- Geotab Account Password
Here are the steps to get started:
1) Enabling the “Geotab” Device Type:
Under the Admin tab, head to ‘Custom Device Names’. You can access this from your Partner HOME org. only.

Scroll down the list and then, enable the Geotab Device Type.
Optionally, you can change the name from “Geotab” to “GO”. Going forward the “GO” device type will be shown on the TG interface and reports.

2) Configuring an External Device Service:
Under the Admin tab, head to External (AEMP 2.0) Device Services.
Then, click “Add External Device Service”. Select and the “Geotab” provider type.
3) Configuring the Geotab External Device Service:
Edit the Geotab External Device Service created in Step 2, then click on Add Credentials.

4) Import the Geotab Assets:
Click Import Now. If all went well, you should see the 'Status' column change from "Awaiting Authentication" to “Authenticated. Active.”

5) Creating new Assets:
Head to Assets tab -> Manage Assets, create new assets using the Geotab Device Serial numbers.
Make sure that the Device Type is set to Geotab (or the custom name like GO if you change the device name in step 1)
Creating Assets in Telematics Guru - Digital Matter

6) All Done!
Now that you have made your assets, information will start coming through the connection that you created to Geotab. Please bear in mind that this is a maximum of every 30 seconds. Information received from Geotab will be treated like any other telemetry data, but the “log reason” will always be Heartbeat.
Troubleshooting
The integration works via a regular poll to a Geotab endpoint, we tell it the last record we received and then it will give us any new data between that point and the present. If we fail to receive valid telemetry, a reason will be stated in the logs. This is accessible under the External Device Service area under “View Logs”. If the error is due to credentials or intermittency from Geotab for whatever reason, we will automatically disable the integration to protect our systems from excessive error messages. Please contact support if you see multiple consecutive failures in the logs.