Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.tread.ai/llms.txt

Use this file to discover all available pages before exploring further.

​
What you’ll do

Connect the two integrations that change how Tread captures truck and paving data: telematics and paver tracking. Accounting integrations come after billing is live.

​
Before you start

  • Admin credentials for your telematics provider (Samsara, Geotab, or another supported system).
  • Admin credentials for your paver tracker, if you pave.
  • Equipment loaded so trucks can match telematics asset IDs.
  • Sites loaded so geofences line up with telematics events.

​
Walkthrough

1

Connect Telematics

Settings → Integrations → Telematics. Pick your provider and paste the API token from your provider’s admin console. Tread starts pulling GPS and engine data within minutes. See Telematics.
2

Match telematics assets to Tread equipment

Tread shows each detected asset next to a dropdown of your equipment. Match each one. Unmatched assets won’t post tickets to the right truck.
3

Connect Paver Tracker

If you pave, Settings → Integrations → Paver Tracker. Paste credentials. Paver telemetry feeds paving stats and moving geofences. See Paver Tracker and Paving & Moving Geofences.
4

Verify data is flowing

Open the dispatch board. Active trucks show live GPS pins. Open a recent ticket — engine hours and idle time are populated.

​
Verify

Settings → Integrations shows each connected system as Connected with a recent Last sync timestamp. The dispatch board shows live truck pins.

​
Common mistakes

Skipping the asset-match step. Tread can’t post a ticket to a truck it can’t identify. Unmatched assets fall into a bucket no dispatcher checks. Walk through every detected asset before moving on.