How GPS Tracking Works

iso.me is the current recommendation for drivers setting up fresh. OsmAnd and Traccar Client remain supported, OwnTracks remains supported, and real Traccar hardware devices work the same way — all of them land in the same feed, so a fleet running a mix does not end up with a split map.

Supporting several sources is deliberate rather than indecisive. A driver who already has a working setup has no reason to be forced onto a different app for the sake of one shipper's platform, and a fleet part way through a hardware rollout should not have to finish it before anyone can see a truck.

What matters for the shipper is that the distinction is invisible on their end. A phone-sourced ping and a hardware-sourced ping produce the same live position on the same map.

Opt-in-per-load tracking fails in an entirely predictable way. The driver forgets, usually on the morning that everything else is going wrong, and the first anyone notices is when a shipper opens the link and finds nothing on it. Then the check-in calls start, which is the situation tracking existed to remove.

Running for the duration of the active booking removes the step that gets forgotten. Tracking is tied to the state of the work rather than to somebody's memory, and when the booking is done, it is done.

It also makes what is shared legible in a way a toggle never is. The answer to what the shipper can see is the same every time: this load, for as long as it is active, and not after.

A driver can set a radius around a sensitive location — home being the obvious case. Inside that radius, dispatch and shippers are shown the zone's center point instead of the driver's exact live position.

Blurring rather than hiding is the important design choice. If position simply disappeared inside the zone, the gap would be the signal: a shipper would learn there is a sensitive location around here, and roughly where the truck disappears every night. Showing a center point keeps the line continuous and gives up nothing.

The shipper still gets what they actually need, which is whether the load is moving and where it is on the route. Where a driver sleeps is not part of that and it does not need to be broadcast to establish it.

A tracking link is scoped to a single shipment. It opens a live map and a chat thread with the carrier, so a question about an arrival window goes to the person hauling the load instead of through a dispatcher relay.

The link expires roughly 48 hours after delivery. That is the part that matters for a carrier: the visibility is for the duration of the job and a little after, not a standing window into the truck for whoever was forwarded the URL.

Multi-stop loads additionally get a lighter, no-login view per stop showing arrival status. A receiver at stop four gets what they need — is it coming, has it arrived — without an account and without the full picture of everything the truck is doing.

These get conflated constantly, so it is worth separating. An electronic logging device exists to record hours of service under 49 CFR part 395: it is tied to the vehicle's engine, it records duty status, and its audience is enforcement and compliance.

Shipment tracking is a location feed scoped to a booking, and its audience is the shipper and receiver of that load. It records where the freight is, not whether a driver is in compliance with their clock.

The practical consequence: nothing here relieves a carrier of any ELD obligation, and a tracking link is not a log. They answer different questions for different people, and a fleet needs both for the reasons each exists.

Phone-sourced tracking depends on two things the trucking industry has no control over: cell coverage and battery. Stretches of the mountain west, long tunnels, and plenty of rural interstate have neither consistently, and a driver on a twelve-hour day is not going to keep a phone alive on its own charge.

A missing stretch on the map is therefore usually a coverage gap rather than a stopped truck. The useful habit for a shipper reading the line is to check whether the resumed position is consistent with continued movement before treating a gap as a problem.

For drivers the fix is dull and effective: hardwired power rather than a cable to a cigarette lighter that works loose, and leaving the tracking app out of whatever aggressive battery optimisation the phone applies by default. Most reliability complaints about phone-based tracking come down to one of those two.