Carrier and trucking TMS · Getting started
ELD integration: connect Samsara, Motive or PeopleNet
Open Settings, then Connections, pick your ELD card and paste the API key or token. Press Test, then Sync. Trucks match by unit number, and positions, hours and state miles start to flow in.
What an ELD is, and what Tezify does with it
An ELD (electronic logging device) records a driver's hours of service in place of a paper logbook. The FMCSA ELD rule in 49 CFR Part 395 requires most drivers who must keep a record of duty status to use one. The driver's e-log lives on the ELD, and it stays the legal record.
Tezify does not replace the ELD. It reads from it. Dispatch then sees where each truck is and how many hours each driver has left before the next load goes out, and IFTA can use measured miles instead of estimates.
Connect it
- Open Settings, then Connections (Integrations).
- Find your ELD card: Samsara, Motive or PeopleNet.
- Enter the credentials. Samsara needs an API token. Motive needs an API key. PeopleNet needs the API URL, Customer ID and API password.
- Press Test to check the connection.
- Press Sync to pull data now. After that it refreshes on its own.
- Check the unmatched vehicles and link or create each one.
What each ELD sends
| ELD | Positions | Hours of service | IFTA miles |
|---|---|---|---|
| Samsara | Yes | Yes | Yes, once the token has the Read IFTA (US) scope |
| Motive | Yes | Yes, as Motive reports them | Yes |
| PeopleNet | Yes, hourly and on Sync | No, PeopleNet does not publish them | No |
Samsara also sends fuel and odometer readings, engine fault codes and harsh-driving events. Motive syncs every hour by itself, and Sync pulls positions and clocks at once. If Motive has not synced for 5 hours, its clocks show as stale on the dispatch board.
How matching works
- Trucks match when the vehicle number in the ELD equals the unit number in Tezify.
- Motive drivers match by exact full name. A name shared by two Tezify drivers is skipped and named so you can fix it.
- Samsara drivers can be linked on the Samsara mapping page under Drivers.
Where the data shows up
- Live map: each truck's last position and speed.
- Dispatch planner: drive, shift and cycle time left next to each driver.
- IFTA: measured miles by state from Samsara or Motive.
Common questions
My truck is not on the map after connecting.
Check that the ELD vehicle number matches the unit number exactly. Unmatched vehicles are listed so you can link them.
Is the driver e-log in Tezify the legal record?
No. The ELD stays the official record of duty status. Tezify reads its clocks so dispatch can plan, and the driver app's duty taps are not a logbook.
What happens with no ELD connected?
The map uses the driver app's phone location when the driver shares it. The planner shows no hours, and IFTA estimates miles from each load's route and says so.
Samsara is connected but IFTA miles are missing.
Give the Samsara API token the Read IFTA (US) scope, then press Sync again.
Ready to do it? This lives at /admin/integrations in Tezify.
Related articles
- Carrier and trucking TMSHow to see your trucks on the live fleet map
- Carrier and trucking TMSHours of service tracking: live ELD clocks for dispatch
- Carrier and trucking TMSIFTA reporting in Tezify: automate your quarterly fuel tax
- Carrier and trucking TMSCarrier TMS software: what Tezify runs for your fleet
- Carrier and trucking TMSHow to set up your company profile, MC and DOT
- Carrier and trucking TMSHow to import your drivers, trucks and customers