Live delivery tracking on top of Motive

What Motive shows about a delivery today

Motive covers the fleet-operator’s view of the vehicle well. The gap shows up when delivery is on your own fleet and the end customer wants to see where the truck is right now.

• Fleet Dashboard and live map. Internal-facing. Dispatchers and fleet ops see where every vehicle is right now, geofence alerts, exception rules. Not a per-customer link, not branded for the end customer.
• Geofence ETAs and alerts. Motive can fire an alert when a vehicle enters or leaves a geofence, useful for depot and yard ops. It is not a per-stop ETA recalculated against a route plan.
• Webhooks for vehicle events. Vehicle locations, ignition, fuel and safety events can be subscribed via the Fleet API. Customers can consume them in their own systems, but Motive itself doesn’t ship a customer-facing tracking page.

All of that is fleet-operator visibility into the vehicle. It is not an end-customer delivery tracking experience.

What live delivery tracking actually means

For own-fleet operations, the customer-facing tracking experience that drives repeat orders and reduces support load looks like this:

• Live driver GPS on a map. The customer sees where the truck is right now and what stop number they are on the route.
• Real-time ETA. Recalculated as the driver moves and as the plan changes; not a static morning estimate that’s out of date by lunchtime.
• Driver name and contact. Customer knows who’s coming and can call if access changes.
• Branded. The page carries the operator’s branding (logo, colors, layout), not a generic delivery widget. Multi-brand support for operators running multiple consumer brands.
• Embedded content. NPS micro-survey at the end. Safety briefings before a hazmat delivery. Access codes for a gated community. Care instructions for a piece of equipment.
• Self-service rescheduling. If the customer can’t take the delivery, the page offers a route-aware reschedule that already fits the optimized plan.

This is a separate surface from the fleet-operator map Motive ships natively. The two complement each other.

Where Motive users land today

Three patterns are common before a live-tracking layer is added.

• Customer support absorbs the “where’s my order” calls. The customer phones in. The CSR opens the fleet map, sees a vehicle in roughly the right area, calls the driver, calls back the customer. Cycle time per call: 4 to 8 minutes. Aggregate cost at scale: significant.
• Generic SMS templates. Driver sends a manual SMS at start of day with an estimated window. No live tracking, no map, no self-reschedule. Works until a customer asks a follow-up.
• Third-party tracking widget, no eLogii. A basic tracking widget is bolted onto the storefront, but it has no real connection to the live driver position or to the optimized plan. The ETA is a guess.

The fix is a tracking page driven by the same live GPS and route data the dispatcher is looking at, branded to match the operator, surfaced wherever the customer expects to find it.

How eLogii’s live tracking works

The driver app streams GPS as the driver moves. eLogii recalculates ETAs continuously as drivers progress and as the plan changes. The customer-facing tracking page shows the live state.

• Live driver GPS stream. From the driver app to eLogii in real time.
• Real-time ETA. Recalculated against the current plan and current driver position.
• Branded tracking pages. Configurable logo, colors and layout per brand. Multi-brand support for operators running several consumer brands from one fleet.
• Embedded content. NPS, safety briefings, access codes, care instructions, treatment notes – configured per task type or per customer segment.
• Self-service rescheduling. Customer can pick a route-aware slot if they can’t take the delivery. Around 70% of reschedule requests get handled without coordinator involvement.
• Notification triggers. SMS or email when the driver is N minutes out, when arrival is imminent, when the delivery is complete.

How live tracking fits alongside Motive

The customer-facing tracking page is served by eLogii. Motive remains the telematics system of record on its side of the stack. Three display shapes are common, and the choice depends on where you want the customer to land.

1. SMS / email link. Customer gets a link via SMS or email at key moments (booked, driver en route, N minutes out). Link opens the eLogii tracking page directly. Simplest integration; no portal work required.
2. Embedded in your customer portal. The eLogii tracking page embeds via iframe in your existing customer portal, so customers logging in to check an order see the live tracking inside their familiar portal.
3. Embedded in your storefront. Same iframe pattern but inside your e-commerce storefront on the order details page.

Each is display-side: where the customer sees the page. eLogii reads vehicle position and driver state from the Motive Fleet API; the customer-facing tracking page is generated and served by eLogii from that data plus the route plan.

Frequently asked questions

Does Motive have live delivery tracking for end customers?

Motive’s Fleet Dashboard shows live vehicle GPS to the fleet operator on a map (the dispatcher view), with geofence alerts and exception rules. It does not ship a branded end-customer delivery tracking page, a real-time route ETA that recalculates as the driver moves, or embedded content like NPS, access codes or safety briefings. That layer is what eLogii adds on top.

Why doesn’t Motive show live ETAs to the end customer?

Because Motive is a fleet telematics platform, not a customer-experience platform. The live vehicle position is exposed to the fleet operator, not to the shipper’s end customer. There is no built-in branded tracking page, no per-customer link, and no route plan against which to recalculate an ETA — the route plan lives in the routing layer above Motive.

How does eLogii’s live tracking work?

The eLogii driver app streams live GPS coordinates as the driver moves. eLogii recalculates route ETAs in real time as drivers progress and as the plan changes. Customer-facing tracking pages, branded per customer, show the live map, the next-stop ETA, the driver name and contact, and any embedded content the operator configured (NPS, access codes, safety briefings, treatment notes). Pages can be embedded in your customer portal or storefront via iframe, or sent to end customers via SMS / email links.

How does the live state get back to Motive?

Via webhooks. eLogii’s Driver/Task Tracking Update webhook fires with live driver coordinates and updated ETAs; the integration layer can route those events to Motive (typically the assigned vehicle, current stop and route progress, written against the vehicle record), to your own dispatch screens, or directly to a customer-facing endpoint. No polling, no cron jobs, no manual sync.

Can the tracking page be branded per customer?

Yes. Multi-brand tracking is supported. Run three brands from one dispatch desk, each with its own logo, colors, layout and embedded content. Useful for operators running multiple consumer brands off a single own fleet.