Analytics already shows whether transports were allocated, tracked, and visited. Two columns on the Transports table now show how that visibility was produced:
Allocation source — how the vehicle / license plate was assigned to the transport
Location data source — which tracking connection actually provided the location data
You no longer need to open every transport to see whether allocation was manual or automated, or whether tracking came from GPS, an API, or the mobile app.
Where to find these columns
Open Analytics → Tracking Performance.
Apply your usual filters (time range, carrier/customer, lane, and so on).
Scroll to the Transports table.
Allocation source sits directly after Allocated.
Location data source sits directly after License plate.
Allocation source
Definition: How the vehicle was allocated to this transport.
Allocation is the step that links a license plate (or equivalent asset) to a transport so Visibility can start tracking. See How to allocate a vehicle to a transport
Value | What it means |
UI | Someone allocated the vehicle in the Transporeon Platform user interface (for example Transport Assignment or Time Slot Management). This is manual work. |
Visibility UI | Someone allocated the vehicle in Transporeon Visibility (for example the Allocate action in the Visibility Control Center). This is also manual work. |
Carrier API | The allocation was sent from the carrier’s in-house system through a Visibility / carrier interface. This is automated. |
Platform API | The allocation arrived via the Transporeon Platform, without a more specific UI vs API distinction. |
GPS | The allocation is tied to a telematics / GPS connection. |
TBS | The allocation was created automatically from the tour-based data stream (transport data driving the allocation, rather than a separate manual action). |
TTC | The allocation came from Trimble Transportation Cloud. |
Autonomous Allocation | Automatically assigned allocation |
- | No usable allocation source. Typical when the transport was never allocated, the allocation was cleared, or the transport is no longer available. |
Location data source
Definition: The tracking source that actually provided the last location signal for this transport.
This is same as Last signal on the transport details page. If more than one visibility source is connected, Analytics still shows only the source that was used.
Value | What it means |
GPS | Location came from a telematics / GPS provider connected to Visibility. |
Carrier API | Location (or tracking events that include position) came from the carrier’s in-house system through a Visibility / carrier interface. |
Platform API | Location came through a Transporeon Platform API connection. |
Mobile app | Location came from the driver app (Transporeon Trucker, or the Visibility Drive app where that applies). |
TTC | Location came from Trimble Transportation Cloud. |
TTC mobile | Location came from the Trimble / TTC mobile app. |
- | No last signal. Typical when the transport received no GPS or equivalent location data, or the transport is no longer available. |
