Geotab data reference
A clear view of the fleet information our current Geotab connection imports, and what would need more work before it appears in EveryTrack.
The connection has been written to import these categories when a connected Geotab account supplies them. This is not a claim that a customer fleet is connected. Dashboard screens may show labelled demo data when the data connection is unavailable. Updates depend on the latest report and sync, not a guaranteed live feed. Fields vary by vehicle, fitted hardware, account permissions and configuration.
Current connection
Each line links to the manufacturer's data reference. A field appears only when the connected account returns it.
01 / IMPORTED BY CURRENT SYNC
Fields: Vehicle name, device serial, make, model and year when supplied.
Displayed as: Vehicle list and individual vehicle details.
A vehicle name is not necessarily its registration; some details may be missing.
02 / IMPORTED BY CURRENT SYNC
Fields: Most recent coordinates, reported speed, timestamp and associated driver when recorded.
Displayed as: Fleet map, vehicle location, driving/parked/offline status and last update.
Status is calculated from the age and speed of the latest record. The map shows the last reported position, not a guaranteed current location; street addresses are not populated by the current sync.
03 / IMPORTED BY CURRENT SYNC
Fields: Trip start/end time, distance, duration, average and maximum speed, stops and available start/end addresses.
Displayed as: Trip list, vehicle history, mileage summaries and driving-time reports.
The current sync imports trip summaries, not the detailed route line or journey replay.
04 / IMPORTED BY CURRENT SYNC
Fields: Driver name, assigned vehicle when identifiable from a recent report, and available trip totals.
Displayed as: Driver list, vehicle association and driving activity.
An association may be unavailable or out of date; it should not be treated as a confirmed current assignment.
05 / IMPORTED BY CURRENT SYNC
Fields: Reported odometer value; available fault code, description, controller and reported time.
Displayed as: Vehicle mileage, fault list and vehicle fault status.
Odometer uses one configured diagnostic; not all vehicles report it. Fault severity in EveryTrack is an indicative label derived from the fault description, not a manufacturer diagnosis.
06 / IMPORTED BY CURRENT SYNC
Fields: Rule name, vehicle, driver when identified, event time and available position; speed, braking, acceleration, cornering or idling when matched by a configured rule.
Displayed as: Driver-event feed and fleet alerts.
Only events produced by rules in the connected account can appear. An event is not proof of unsafe driving or a measure of a pupil's ability.
07 / IMPORTED BY CURRENT SYNC
Fields: Configured zone names and polygon boundaries, with a count based on vehicles' last reported positions.
Displayed as: Zone list and fleet map; configured zone events may appear among alerts.
The count uses last known positions. Zone entry/exit history is not separately imported.
Not imported yet
Geotab documentation describes more data than the current EveryTrack sync collects. These are possibilities, not active EveryTrack displays.
The current trip import stores an empty route path. A separate GPS-history import and route assembly would be needed before replay can be shown.
The sync does not import fitted-camera status, video clips or camera events. Access would need confirmed compatible hardware, permissions and a separate media integration. EveryTrack does not offer live video streaming.
Readings such as battery, fuel or engine measurements are not part of the current odometer-only status import. Availability varies by vehicle, device and enabled diagnostics.
Tracking, cameras, diagnostics and driver visibility that sit alongside the driving-school software you already use.
