# project44 integration: location and predictive ETAs

> project44 feeds Roadmark real-time location and predictive ETAs for carriers already sharing through its network, keeping tracking and the portal current.

URL: https://roadmark.ai/integrations/project44
Language: en
Last updated: 2026-10-01

**TL;DR:** Roadmark reads real-time location and predictive ETAs from project44 for any carrier already sharing through its network. 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 | project44 to Roadmark | As project44's network reports it |
| Predictive ETA | project44 to Roadmark | Recalculated as conditions change |

## Setting up project44

1. **Register a client application in project44 Movement:** A Movement Customer Admin creates a client application, gives it the roles and access groups it needs, and Roadmark uses it to request an access token.
2. **Confirm which carriers are connected:** project44 tracks a carrier once it's connected through its ELD or telematics, project44's DriveView app or an API, and turned on sharing with you. If a carrier isn't yet, they connect on project44's side first.
3. **Test with a real load:** Run one load through it and check that the location and ETA match what project44's own dashboard shows, before turning it on for everything.

### Before you start

- A project44 Movement account with a Customer Admin who can register a client application.

Some of the carriers on your board already share their location with
shippers through a visibility network instead of, or alongside, an ELD
connection. project44 is one of those networks, and Roadmark reads the
location and predictive ETA it reports for any carrier that's already
sharing with you 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 project44's network

project44 runs its own onboarding for carriers. As its
[carrier FAQ](https://www.project44.com/carriers/faqs/) describes, a carrier connects
through its ELD or telematics provider, project44's DriveView app on a
driver's phone, or an API, and then decides which of its customers can see
that data, with the option to stop sharing with any of them at any time. So
a carrier's trucks show up for you once that carrier is sharing with you
through project44.
Roadmark doesn't do that onboarding: it reads from carriers already
connected on project44's side.

## Connecting Roadmark to project44

project44's [Movement platform authenticates API
clients](https://developers.project44.com/api-reference/authentication)
with the OAuth 2.0 client credentials grant. An admin with the Movement
[Customer Admin](https://developers.project44.com/api-reference/authentication)
role registers a client application, assigns it the roles and access
groups covering the data Roadmark should read, and Roadmark uses that
client's credentials to request an access token from project44's OAuth
token endpoint. Nothing about how a carrier connects to project44 changes.

## What a predictive ETA adds

project44 describes its ETA as recalculated continuously from a truck's
current position along with conditions such as traffic and how that
carrier has historically performed on that lane, rather than an ETA that
only updates when a status message arrives. 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

On Tuesday's board, load 48219 is covered by Northline Freight, an outside
carrier, at $1,655.00 in US dollars. Ashgrove Logistics doesn't run that truck, so there's
no ELD connection to read from directly. If Northline Freight already
shares its location through project44, Roadmark reads that feed instead:
[tracking](https://roadmark.ai/tracking) gets an ETA for 48219 the same way it would from a
connected ELD, and Prairie Foods or whichever customer is waiting on that
load sees the same ETA in their own [portal](https://roadmark.ai/portals), without Ashgrove
Logistics calling Northline Freight to ask where the truck is.

## 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 its own ELD in someone else's truck.
project44 is built for exactly that gap: it tracks the carrier, not the
freight's owner, so a broker gets the same current ETA on a purchased-power
load that a carrier gets on its own trucks. That's what feeds the same
customer portal either way.

For a broker or carrier already working with project44-connected carriers,
the change is mostly that the board and the customer portal catch up to
what project44 has been reporting the whole time, instead of a dispatcher
copying an ETA across from a separate dashboard.

## Questions about project44 and Roadmark

### What does Roadmark read from project44?

Real-time location and predictive ETAs, the same two the project44 integration is listed for in the directory.

### Does a carrier need new hardware to show up in project44?

No. project44 tracks a carrier once it's connected its own ELD, GPS or telematics data to project44's network; Roadmark then reads what's already flowing, without a carrier installing anything for Roadmark specifically.

### How is project44's predictive ETA different from an ELD's own ETA math?

project44 recalculates its ETA continuously from current position plus conditions such as traffic and historical performance on that lane, rather than only the truck's speed and remaining distance. Roadmark reads whichever ETA the connected source, ELD or visibility network, is reporting for that load.

### Does connecting project44 change how detention is billed?

No. Detention is billed from dock arrival and departure times against the free time in the rate confirmation. A visibility network's location feed is one of the sources those times can come from when a load isn't on a connected ELD.

### Can I connect both an ELD and project44?

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 project44, 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
- [FourKites integration: location and Dynamic ETA](https://roadmark.ai/integrations/fourkites): FourKites feeds Roadmark real-time location and predictive ETAs for carriers connected through FourKites Connect, 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.