What Does the Geotab GO Device Actually Track?

The GO device combines a GNSS receiver, an accelerometer, and a connection to the vehicle's onboard diagnostics. Each produces a different kind of data. The receiver gives position, speed and heading. The accelerometer gives motion — braking, acceleration, cornering, impacts — independent of the engine. The diagnostic connection gives what the vehicle itself knows: engine on and off, RPM, odometer, fuel, fault codes, and hundreds of other parameters depending on the make. Most of what a fleet uses is one of these three, or a rule combining them.

The core data points, and the job each one does.

The GO device has no microphone and no camera. It does not record audio, video or anything said in the cab; video comes only from a separate camera connected through the IOX port, and that camera's recording rules are configured by the fleet. It does not read the driver's phone. It does not track a person when they are not in the vehicle. And during personal conveyance, the ELD record stores location at reduced precision, though the fleet's own map still shows the vehicle.

It also only knows what the vehicle tells it. Fuel level, seat belt and some engine parameters depend on the make and model exposing them; an older or unusual vehicle may report fewer of them, which is worth checking for a specific vehicle before promising a specific report.

The device does not log at a fixed interval. It records a point whenever the vehicle's motion changes enough for a straight line between points to misrepresent the path — Geotab's curve-based logging — which keeps the trip shape accurate on corners without flooding the record with identical highway points. Position accuracy is the receiver's, typically within a few metres in open sky and worse in dense urban canyons or under cover. Data reaches the platform over cellular in near real time and is buffered on the device when there is no signal, then sent when it returns.

Two fleets with the same devices can get very different value from them, and the difference is which data they act on. Position alone answers 'where is it'. Engine hours and fault codes answer 'when will it break'. Idle time answers 'where is the fuel going'. Accelerometer events answer 'who needs coaching'. The device records all of it from the day it is installed; a fleet that starts with the map and never opens the rest is using a fraction of what it paid for.