Using ELD Location Data for Carrier Matching: What the APIs Give You and What They Don't

ELD mandates created a side effect that's useful for freight brokers: a significant portion of the commercial truck fleet now generates regular location updates as a byproduct of HOS compliance logging. Visibility platforms like Macropoint, Fourkites, and project44 aggregate these signals and expose them via API. The promise is that you can identify available carriers near your load origins and improve carrier matching efficiency. The reality is more constrained than the marketing suggests — but it's still worth understanding what the data actually provides.

How ELD Location Data Flows to Visibility Platforms

ELD location data originates at the device level — Samsara, KeepTruckin (now Motive), Omnitracs, PeopleNet, and dozens of other ELD providers — and flows through multiple intermediary layers before it reaches a broker API. The carrier's ELD provider aggregates the device data and may share it with visibility platforms that have commercial data-sharing agreements. The carrier must also consent to share location data for specific loads or relationships.

The consent model varies significantly by ELD provider and visibility platform. Macropoint, which originated as a GPS tracking broker tool before being acquired by Descartes, has deep integration with carrier ELD providers and a large opt-in carrier network. Fourkites operates a shipper-centric visibility model where shippers subscribe and carriers agree to share location as a condition of working with those shippers. Project44 focuses on enterprise shipper connectivity and has broader multimodal coverage but may have lower carrier penetration in the small-carrier segment that dominates mid-market brokerage.

The practical implication is that no single visibility platform has universal coverage. A carrier who uses KeepTruckin ELD and participates in Fourkites but not Macropoint will be visible in one system but not the other. For a broker trying to use location data for carrier matching, the platform coverage gaps matter as much as the data quality within each platform.

What "Available" Means in Carrier Location Data

Carrier location APIs typically tell you where a carrier's trucks have been recently, not whether they're available for a load. This is the most significant gap between the promise of ELD-based carrier matching and the operational reality. A truck appearing in a location feed may be:

Currently empty and actively looking for a load in that area. Currently delivering a load and not available. En route to a scheduled pickup and not taking new tenders. Completing a mandatory break period before their next available hours window. Or simply generating a background ELD ping that doesn't reflect the driver's current availability or intent.

Distinguishing between these states requires additional data beyond location — carrier dispatch status, HOS remaining hours from the ELD system, and ideally some form of capacity availability signal from the carrier. Some visibility platforms surface HOS remaining hours alongside location data for carriers who've consented to share it. This is more useful than bare location data, but it still doesn't tell you whether the carrier is actively looking for a load or already committed to their next move.

The most actionable carrier location signals are "truck recently completed delivery in city X with no outbound load assigned." This state — post-delivery, no return commitment — is where a carrier is genuinely in repositioning mode and most likely to accept an outbound load from that market. Identifying this state requires correlating location data with delivery completion events from the TMS or visibility platform, not just raw location pings.

Coverage Gaps by Carrier Segment

ELD-based location visibility has systematically different coverage rates across carrier segments. The coverage gap is directly relevant to mid-market brokers because the carriers who dominate spot market coverage — small fleets and owner-operators with 1–5 trucks — are exactly the carriers with the worst location data availability.

Large asset carriers (500+ trucks) almost universally have robust ELD systems and visibility platform integrations because enterprise shippers require it as a condition of their freight programs. Mid-size carriers (50–500 trucks) have good coverage on loads from shippers who mandate tracking but may have gaps for spot loads from smaller brokers who haven't established a tracking relationship. Small carriers and owner-operators have the most variable coverage — some are fully visible on Macropoint or project44; many generate location data only when actively tracked on a specific load, not as a persistent background feed.

This means that for the small-carrier pool that mid-market brokers rely on for spot market coverage, ELD location data is useful but not comprehensive. A carrier matching model that only activates on carriers with active location signals will systematically miss a significant portion of the available small-carrier capacity pool. Location data needs to be combined with other signals — historical load patterns, carrier zone preferences from past tender behavior, capacity posting activity on load boards — to have adequate coverage for mid-market brokerage operations.

Latency: How Fresh Is the Data?

ELD devices log location updates at configurable intervals — typically every 1 to 15 minutes depending on device settings and carrier preference. The data then traverses multiple systems: ELD device → carrier's ELD platform → visibility API → your carrier matching system. Each step in that chain adds latency. In practice, the location data you query from a visibility API may be 15 to 30 minutes old for well-connected carriers, and significantly older for carriers on less frequent update intervals or with intermittent cellular coverage.

A 15-minute-old location signal is sufficient to identify that a carrier is in the general vicinity of your load origin — the carrier hasn't moved 200 miles in 15 minutes. But it's not sufficient for precise arrival time estimation or for distinguishing between a carrier who's parked near your shipper's facility versus one who's 45 miles away on a different highway. For carrier matching purposes, this level of precision is adequate. For shipment visibility and ETA prediction, it requires more sophisticated position extrapolation using speed, road network, and HOS remaining hours.

The latency question becomes more significant during high-demand periods when carriers are moving quickly between loads. In a busy Friday afternoon market, a carrier's "current" position may have changed significantly by the time your matching system queries it and routes a tender. This doesn't make ELD data useless for carrier matching, but it argues for treating it as a prior probability signal rather than a definitive position — "this carrier was likely near Chicago 20 minutes ago" rather than "this carrier is at this coordinate right now."

Integrating Location Data Into Carrier Scoring

The most effective use of ELD location data in carrier matching is as an additive signal that modifies base carrier scores, rather than as the primary matching criterion. A carrier with a strong lane-level acceptance rate and favorable historical performance on Chicago-originating loads, who happens to have a current location signal showing a truck near Chicago, should be ranked higher than the same carrier without a location signal. The location signal is a positive modifier, not the foundation of the recommendation.

Building this correctly requires a carrier scoring model that can ingest location events as they arrive and update carrier rankings dynamically, rather than batch-updating once per day. A carrier's position at 2 PM is not the same as their position at 8 AM. The matching relevance of location signals decays as the load's pickup time approaches — a carrier who's 300 miles away when the load is ready in 2 hours is not a viable match regardless of their location signal.

As we discussed in our analysis of Midwest corridor backhaul patterns, the intersection of historical backhaul pattern data and real-time location signals is where the highest-quality carrier matches come from. A carrier who historically repositions from Indianapolis to Chicago on Wednesday mornings, and whose location signal shows them in Indianapolis on a Tuesday evening, is a high-probability match for a Wednesday Chicago-origin load. That insight requires both the historical pattern data and the current location signal; either alone produces a less accurate prediction.

Privacy and Permission Considerations

Carrier location data carries privacy implications that are often underweighted in discussions of carrier matching technology. Drivers are aware that ELD devices track their movements — that's a condition of HOS compliance — but the secondary use of that location data for broker carrier matching is a different use case than compliance logging. Some carriers are specifically opposed to sharing location data with brokers outside of active load tracking, and they've configured their ELD visibility settings accordingly.

Respecting carrier consent boundaries in location data usage isn't just an ethical consideration — it has practical implications for carrier relationships. A carrier who discovers that a broker has been tracking their position without an active load relationship may choose to stop working with that broker. In a market where carrier relationships have meaningful value, eroding carrier trust through intrusive data practices carries a real cost. The permissioning model you use for carrier location data should match what carriers have agreed to, not just what the API technically allows.

HaulCortex's carrier matching uses location data only for carriers who have active relationships with our customers and have consented to location data sharing through their ELD provider's permission settings. We don't use ambient tracking of non-consenting carriers and don't retain location data beyond the operational matching window.