Motive

Motive, formerly KeepTruckin, is an ELD and fleet management platform with a public REST API for truck location, hours of service, telematics and freight visibility. Connected to Cargofy, every load on a Motive-equipped truck shows a live position, an ETA based on the driver's available hours, and statuses that update at the gate. The dispatch manager of a shipper with its own fleet, or with a carrier base on Motive, usually switches it on.

What teams use it for

Status updates without calling the driver

A flatbed loads in Omaha for Denver. The dispatcher used to call the driver at pickup and again at delivery to confirm times. Motive sends geofence entry and exit events over company webhooks, Cargofy matches them to the active load, and the status moves from loading to en route to delivered. The dispatcher follows it in Tracking, and the customer gets each update as it happens.

An ETA the driver can legally make

Past North Platte, the driver's available hours drop below what the remaining distance needs. Cargofy reads HOS and available hours from Motive and moves the ETA to the next morning. A digital worker tells the Denver receiver before the slot is missed. The ETA the planner sees in Tracking accounts for the rest break.

Track a load on another fleet's Motive truck

Procurement hands a lane to a small carrier that also runs Motive. For that load, Cargofy creates a Freight Visibility subscription in Motive. After the carrier gives consent, the truck's position shows on the load in Tracking like an owned truck. The subscription ends when the load closes, so the carrier shares only that one load.

Detention risk before dwell eats the day

A truck enters the delivery geofence at 08:10 and is still inside at 10:00. Cargofy checks dwell time against the driver's remaining hours and flags the load: another hour of unloading means the next pickup is lost. A digital worker raises it to the dispatcher with the numbers. At geofence exit the dwell goes onto the load in Tracking as the detention record, ready for billing.

Reefer temperature and fault codes as exceptions

A reefer temperature reading leaves the set range, or an engine fault code fires, on a loaded truck. Cargofy reads the event from Motive, matches it to the active load and opens an exception in Tracking with the truck's position and distance to the next stop. The dispatcher decides whether to reroute or warn the receiver. The reading stays on the load, so if a claim follows, customer service has the time, value and position without asking the driver.

How it fits your stack

Your TMS stays the system of record for orders. Driver logs and HOS records stay in Motive; Cargofy reads them and never edits them. Cargofy reads locations, HOS, geofence and fault events, dispatch records and reefer temperature. It writes only Freight Visibility subscriptions for specific loads. Setup is OAuth: your Motive admin approves the scopes in Cargofy settings, and tracking is active the same day. IFTA mileage and fuel transactions exist in the Motive API but are not part of this integration.

Who it is for

North American shippers with a private fleet on Motive, or a carrier base that runs Motive ELDs and will consent to Freight Visibility. Dispatchers watch positions and exceptions, transport planners use HOS-aware ETAs, and the IT admin approves the OAuth connection.