# FourKites integration: location and Dynamic ETA > FourKites feeds Roadmark real-time location and predictive ETAs for carriers connected through FourKites Connect, keeping tracking and the portal current. URL: https://roadmark.ai/integrations/fourkites Language: en Last updated: 2026-10-01 **TL;DR:** Roadmark reads real-time location and predictive ETAs from FourKites for any carrier already connected through FourKites Connect. That feed is what tracking turns into a load's ETA, and what a customer sees in their own portal, without a carrier installing anything new. ## What syncs One row for each kind of record: which way it moves, and when. | What | Direction | When | | --- | --- | --- | | Location | FourKites to Roadmark | As FourKites' network reports it | | Predictive ETA | FourKites to Roadmark | Recalculated as conditions change | ## Setting up FourKites 1. **Get API access from FourKites:** An admin on your FourKites account sets up API access for Roadmark, so it can read location and predictive ETAs for the loads you're tracking. 2. **Confirm which carriers are connected:** FourKites tracks a carrier once it's connected its ELD or GPS provider through FourKites Connect. If a carrier isn't yet, they connect there first. 3. **Test with a real load:** Run one load through it and check that the location and ETA match what FourKites' own dashboard shows, before turning it on for everything. ### Before you start - A FourKites account with an admin who can set up API access. Some of the carriers on your board already share their location with shippers through a visibility network instead of, or alongside, an ELD connection. FourKites is one of those networks, and Roadmark reads the location and predictive ETA it reports for any carrier that's already connected through it, so [tracking](https://roadmark.ai/tracking) has a current ETA without that carrier installing anything new for Roadmark specifically. ## How a carrier gets into FourKites' network FourKites runs its own onboarding for carriers through [FourKites Connect](https://www.fourkites.ai/carrier-network/fourkites-connect), a self-service dashboard where a carrier enters credentials for its ELD or GPS provider once, FourKites says covering more than 900 providers, and manages every connection from one place: which providers are connected, updating credentials when they expire, and which shipper customers it's being tracked for. Roadmark doesn't do that onboarding: it reads from carriers already connected on FourKites' side. ## Connecting Roadmark to FourKites FourKites issues API access to customers through its own account setup rather than an open self-service signup; an admin on your FourKites account sets up that access so Roadmark can read location and ETA data for the loads you're tracking. Nothing about how a carrier connects through FourKites Connect changes. ## What Dynamic ETA adds FourKites calls its predictive ETA [Dynamic ETA](https://www.fourkites.ai/press/fourkites-fine-tunes-predictions-for-shipment-arrivals-2), calculated from a carrier's current signals rather than only the last status update, so it updates continuously as a load moves instead of jumping between check-ins. Roadmark reads that ETA the same way it reads an ELD's: as one of five sources feeding a load's status, alongside the [driver app](https://roadmark.ai/driver-app), a carrier's own app or an EDI 214, other visibility networks, and a check call when nothing else is reporting. The same ETA that shows up on the load board is what a customer sees in their own [portal](https://roadmark.ai/portals). ## A worked example Load 48237 is billed to Harrow Lane Trucking, an outside carrier tendered the load rather than one of Ashgrove's own units. There's no Roadmark-side ELD connection to a truck that isn't yours, so if Harrow Lane Trucking has already connected through FourKites Connect, Roadmark reads its location from FourKites instead: [tracking](https://roadmark.ai/tracking) gets an ETA for 48237 the same way it would from a connected ELD, and the customer waiting on that load sees it in their own [portal](https://roadmark.ai/portals), without dispatch calling Harrow Lane Trucking to check. ## Why this matters for brokers A [broker](https://roadmark.ai/brokers) or a group's brokerage arm tenders loads to carriers it doesn't operate, so it can't put an ELD connection in a truck it doesn't run. FourKites is built for that gap: it's the carrier, through FourKites Connect, that shares its position, not the freight's owner, so a broker gets a current ETA on a purchased-power load the same way a carrier gets one on its own trucks. That's what reaches the customer portal either way. For a broker or carrier already working with FourKites-connected carriers, the change is mostly that the board and the customer portal catch up to what FourKites has been reporting the whole time, instead of a dispatcher copying an ETA across from a separate dashboard. ## Questions about FourKites and Roadmark ### What does Roadmark read from FourKites? Real-time location and predictive ETAs, the same two the FourKites integration is listed for in the directory. ### Does a carrier need new hardware to show up in FourKites? No. A carrier connects its existing ELD or GPS provider through FourKites Connect, FourKites' own self-service tool; Roadmark then reads what's already flowing, without a carrier installing anything for Roadmark specifically. ### How many ELD and GPS providers does FourKites Connect support? FourKites says it supports over 900 ELD and GPS providers through FourKites Connect, so most carriers already running one can connect without a custom integration. ### What is FourKites' Dynamic ETA? FourKites' own name for its predictive ETA, calculated from a carrier's current signals rather than only the last status update. Roadmark reads whichever ETA the connected source, ELD or visibility network, is reporting for that load. ### Can I connect both an ELD and FourKites? Yes. Roadmark checks five sources for a load's status, the ELD, the driver app, a carrier's own app or an EDI 214, visibility networks such as FourKites, and a check call when nothing else is reporting, and knows which one is reporting for each load. ## Related pages - [Tracking](https://roadmark.ai/tracking): The few loads that need you, with reasons - [Asset carriers](https://roadmark.ai/carriers): Fleets that plan, dispatch and settle - [Customer and carrier portals](https://roadmark.ai/portals): Each side sees only its part - [Brokers and 3PLs](https://roadmark.ai/brokers): Quote, cover, track and bill - [project44 integration: location and predictive ETAs](https://roadmark.ai/integrations/project44): project44 feeds Roadmark real-time location and predictive ETAs for carriers already sharing through its network, keeping tracking and the portal current. - [EDI X12 integration: 204, 990, 214 and 210 explained](https://roadmark.ai/integrations/edi): What EDI 204, 990, 214 and 210 mean, which way each goes and when it's sent, how trading partners are set up, and how tracking status becomes 214s. Companies, people and shipment figures in product examples are fictional. They illustrate workflows and are not customer testimonials or measured results.