Integrating Geotab devices with Telematics Guru
Written by Iman Kareem
Updated at October 19th, 2026
Table of Contents
Integrating Geotab devices with Telematics Guru
Geotab GO device data, including the GO9, can be viewed on the Telematics Guru platform, with data pulled directly from Geotab's servers. This article explains what the integration does, how to set it up, how trips are handled, and how to troubleshoot common issues.
One-way, read-only integration
Telematics Guru imports data from Geotab but never writes anything back to the Geotab platform.
What data is received
Not all features or records have been integrated in the TG platform. Only the LogRecord and DeviceStatusInfo data payloads are received by TG.
The fields imported are time, latitude, longitude, and speed. Heading is calculated by Telematics Guru from successive positions rather than imported. No engine diagnostics or driver ID data is received. All data records appear as Heartbeats on the TG platform (log reason type 11).
What you need
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
We recommend using a dedicated, read-only Geotab service account for the integration rather than a personal login.
Setup steps
1) Enable 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 enable the Geotab Device Type. Optionally, you can change the name from "Geotab" to "GO". Going forward the "GO" device type is shown on the TG interface and reports.
2) Configure an External Device Service
Under the Admin tab, head to External (AEMP 2.0) Device Services. Then click Add External Device Service and select the Geotab provider type.
3) Configure the Geotab External Device Service
Edit the Geotab External Device Service created in Step 2, then click 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) Create new Assets
Head to Assets tab > Manage Assets and create new assets using the Geotab Device Serial numbers. Make sure the asset serial number matches the serial in Geotab, and that the Device Type is set to Geotab (or the custom name like GO if you changed the device name in step 1). See Creating Assets in Telematics Guru.
6) All done
Now that your assets exist, information starts coming through the connection to Geotab. This is a maximum of every 30 seconds. Information received from Geotab is treated like any other telemetry data, but the log reason is always Heartbeat.
How data is collected
Telematics Guru polls Geotab's GetFeed endpoint incrementally, roughly every 30 seconds, telling Geotab the last record it received so only new data is returned. New data typically appears in TG within about a minute. If the connection drops, TG automatically re-logs in and resumes from where it left off, so no data is lost.
How trips are detected
Trip detection is speed-based. A trip starts at the first record with a speed greater than 0, and ends after the asset has been stationary for 200 seconds. That trailing 200 seconds of stationary time is trimmed off the end of the trip. The 200-second value is fixed and is not configurable.
Automatic stale trip closure (optional)
An optional checkbox enables automatic closure of stale trips. When enabled, a trip is closed automatically when all of the following conditions are met: the asset is currently in a trip, no new data has been received for more than 5 minutes, and no data has arrived in the current processing cycle. This improves trip-closure behaviour when a device stops reporting, at the cost of some coverage, since a genuine gap in data can end a trip earlier than it otherwise would.
Troubleshooting
The integration works via a regular poll to a Geotab endpoint. We tell it the last record we received and it returns any new data between that point and the present. If we fail to receive valid telemetry, a reason is stated in the logs, accessible under the External Device Service area under View Logs. If the error is due to credentials or intermittency from Geotab, we automatically disable the integration to protect our systems from excessive error messages. Please contact support if you see multiple consecutive failures in the logs.
| Symptom | Likely cause |
|---|---|
| Authentication error on the service | Wrong server, database, username or password, or the account lost access. |
| An asset shows no data | The asset's serial number doesn't match Geotab, or the asset isn't set to the Geotab device type. |
| Trips stay "in trip" for a long time after the vehicle stops | Geotab stopped sending data for that vehicle. Check the device in MyGeotab, or enable automatic stale trip closure. |
| Trips end earlier than expected during a journey | Stale trip closure is on and the vehicle lost connectivity. |
| Data looks delayed | Telematics Guru checks Geotab about every 30 seconds, so the delay is usually on the Geotab side. Check when the device last reported in MyGeotab. |
Next Steps
- Creating Assets in Telematics Guru to finish adding your Geotab-backed assets.
- Review the LogRecord and DeviceStatusInfo references to confirm which data Geotab sends for your devices.
- Confirm each device is reporting in MyGeotab if data looks delayed or missing in Telematics Guru.
