FAQs: Truckload Tracking Methods
Utilize the GET Tracking Method API. Information provided in the API response to the GET Tracking Method API request will indicate which tracking method a carrier is using. For an explanation of how responses indicate tracking methods, see table below:
|
Mode |
API Response |
|
Mobile Response (SCAC: ACME) |
{
"trackingMethods": [
{
"equipmentIdentifier": {
"type": "MOBILE_PHONE_NUMBER",
"value": "XXXXXXXXXX"
},
"infoMessages": [
{
"severity": "INFO",
"message": "For 'MOBILE_PHONE_NUMBER', provide the mobile phone number of the driver of the truck tendering the shipment.",
"source": "SYSTEM"
}
]
}
]
}
|
|
EquipID type = MOBILE_PHONE_NUMBER, therefore this shipment is being tracked by mobile phone.
|
|
|
ELD (US) Response (SCAC: MSLV) |
{
"trackingMethods": [
{
"equipmentIdentifier": {
"type": "VEHICLE_ID",
"value": "XXXXXXXXXX"
},
"infoMessages": [
{
"severity": "INFO",
"message": "For 'VEHICLE_ID', provide the carrier's vehicle id of the truck tendering the shipment.",
"source": "SYSTEM"
}
]
},
{
"equipmentIdentifier": {
"type": "MOBILE_PHONE_NUMBER",
"value": "XXXXXXXXXX"
},
"infoMessages": [
{
"severity": "INFO",
"message": "For 'MOBILE_PHONE_NUMBER', provide the mobile phone number of the driver of the truck tendering the shipment.",
"source": "SYSTEM"
}
]
}
]
}
|
|
The two equipID types in response are "VEHICLE_ID" (for tracking in North America) and "MOBILE_PHONE_NUMBER." This indicates that the tracking method is with an ELD if the vehicle ID is valid. Otherwise, this shipment will be tracked by mobile phone.
|
|
|
ELD (EU) Response (SCAC: MSLV)
|
{
"trackingMethods": [
{
"equipmentIdentifier": {
"type": "LICENSE_PLATE",
"value": "XXXXXXXXXX"
},
"infoMessages": [
{
"severity": "INFO",
"message": " For 'LICENSE_PLATE', provide the carrier's license plate of the truck tendering the shipment.",
"source": "SYSTEM"
}
]
},
{
"equipmentIdentifier": {
"type": "MOBILE_PHONE_NUMBER",
"value": "XXXXXXXXXX"
},
"infoMessages": [
{
"severity": "INFO",
"message": "For 'MOBILE_PHONE_NUMBER', provide the mobile phone number of the driver of the truck tendering the shipment.",
"source": "SYSTEM"
}
]
}
]
}
|
|
The two equipID types in response are "LICENSE_PLATE" (for tracking in Europe) and "MOBILE_PHONE_NUMBER." This indicates that the tracking method is with an ELD if the license plate is valid. Otherwise, this shipment will be tracked by mobile phone. |
|
|
PUSH API Response (SCAC: CRPS) |
{
"trackingMethods": [
{
"shipmentIdentifier": {
"type": "BILL_OF_LADING",
"value": "XXXXXXXXXX"
},
"infoMessages": []
},
{
"shipmentIdentifier": {
"type": "ORDER",
"value": "XXXXXXXXXX"
},
"infoMessages": []
},
{
"equipmentIdentifier": {
"type": "MOBILE_PHONE_NUMBER",
"value": "XXXXXXXXXX"
},
"infoMessages": [
{
"severity": "INFO",
"message": "For 'MOBILE_PHONE_NUMBER', provide the mobile phone number of the driver of the truck tendering the shipment.",
"source": "SYSTEM"
}
]
}
]
}
|
|
The shipmentID type, either "BILL_OF_LADING" or "ORDER,” indicates that the shipment is being tracked through API.
|
|
|
PULL API Response (SCAC: SCNN) |
{
"trackingMethods": [
{
"shipmentIdentifier": {
"type": "ORDER",
"value": "XXXXXXXXXX"
},
"capacityProviderAccount": {
"code": "XXXXXXXXXX"
},
"infoMessages": []
},
{
"shipmentIdentifier": {
"type": "BILL_OF_LADING",
"value": "XXXXXXXXXX"
},
"capacityProviderAccount": {
"code": "XXXXXXXXXX"
},
"infoMessages": []
},
{
"equipmentIdentifier": {
"type": "MOBILE_PHONE_NUMBER",
"value": "XXXXXXXXXX"
},
"infoMessages": [
{
"severity": "INFO",
"message": "For 'MOBILE_PHONE_NUMBER', provide the mobile phone number of the driver of the truck tendering the shipment.",
"source": "SYSTEM"
}
]
}
]
}
|
|
There are two shipmentID types, either "BILL_OF_LADING" or "ORDER,” that indicate the shipment is being tracked through API.
|
project44 supports three methods for tracking shipments: API, ELD, and mobile app tracking:
API Tracking: project44 connects directly to the carrier’s API in order to obtain data through:
-
An inbound API connection(recommended) where carriers PUSH position updates of the shipment to one of project44’s endpoints, or
-
An outbound (direct) API connection where project44 uses credentials to go directly to the carrier API and PULL updates.
ELD Tracking: ELD tracking collects data transmitted from a telematics hardware (e.g., GPS) device in the truck that connects to carrier and ELD provider APIs. Data is accessed through PUSH updates from the carrier to the project44 endpoint. Or the data can be accessed through a PULL request from the carrier’s endpoint by the carrier PUSHing updates to the project44 endpoint or the customer PULLing requests from the carrier’s endpoint depending on the ELD provider. There are many ELD providers and resellers. By connecting with the Asset ID on the ELD, project44 can track a truck in transit.
DriveView Mobile App: DriveView is an intuitive, free mobile application designed to provide real-time location visibility for active truckload shipments. The DriveView app captures location when tracking is “on” but does not have any of the TL tracking service logic built in, so any events/ETA/status updates are calculated in a TL tracking service. DriveView captures phone location information, sends this information to project44, then “hits” TL tracking service where logic is derived.
The tracking method informs how project44 receives information about a shipment from the carrier. Users can track shipments through multiple tracking methods. Each method of tracking requires different information to be provided when creating shipments in project44’s system in order to connect properly to receive accurate data. Note that not all carriers will support all tracking methods. To check which methods a carrier supports, use: GET: Get available shipment tracking methods for a carrier.
Potential Reason: If a shipment was not successfully initialized to project44, it will not be visible within the VOC.
Solution: Verify shipment was created. If the shipment was not correctly initialized, add shipment again. (How to create a truckload shipment)
Yes. Deleting a shipment will remove it from VOC and remove analytics counts for that shipment. In order to keep analytics counts accurate, only delete shipments that are not relevant or not supposed to be tracked any longer.
If tracking has not startedShipments with a status of “Unknown” in the VOC reflect an actual status of DISPATCHED - PENDING EQUIPMENT IDENTIFIER. This means that your shipment does not have a valid equipment identifier associated with it.
To resolve, under the Shipment Details page, select the ADD NEW EQUIPMENT IDENTIFIER link and follow the instructions.
If tracking has started:
Shipments with a status of “Unknown” reflect no recent update from the inside/outside Geofence. Please await an update.
This message indicates that a shipment was initialized in p44 after the pickup window had already passed. Since tracking began after the first appointment window, it is possible p44 is missing data around the pickup. No action needs to be taken with this info message.
This can be done at any time before shipment starts. Please note, if sent in advance, the PUT API can be used to update any relevant details before the shipment changes. If a shipment is created after the first appointment window has ended, we will start tracking the shipment immediately and will not be able to retrieve any historical details.
Do I need an equipment identifier, like a vehicle ID or license plate, in order to create a shipment?
The shipment will not track until an equipment identifier is applied.
project44 admin can enable a setting to make this optional in your request. That will allow you to create a shipment without the truck number or license plate, and then you can add those in once they’ve been acquired. If the tenant has the flag TRUCKLOAD_PENDING_SHIPMENT_TRACKING_ENABLED set to TRUE, shipments can be created without an equipment identifier.
Utilize the GET Tracking Method API to determine which tracking method a carrier is using to track your shipment. The tracking method will determine which equipment identifier(s) are necessary to track your shipment.
Tracking by license plate is specific to EU customers.
Yes, the Equipment Identifier part of our API is an array which accepts multiple plates. If more than one is submitted, project44 will intelligently select which one to track based on the likelihood of tracking. If all plates are equally valid, the first license plate in the array is prioritized. For most use cases, we recommend trailers to be the top priority.
This depends on the tracking method, but you will always need to include:
-
a shipmentIdentifier
-
carrierIdentifier
-
at least 2 stops (location, date, appointment window).
If the carrier is tracked via ELD you will need to submit a LICENSE_PLATE (EU tracking) or VEHICLE_ID (NA tracking) as the equipment identifier.
If the carrier is tracking via mobile, you will need to submit a mobile phone number.
No, the SCAC submitted must be the official SCAC of the carrier. You can also utilize DOT Number or MC Number instead.
No – this is only required for PULL API carriers.
This can be determined by the information about the carrier that is stored in the project44 portal.
Yes, shipment appointment windows must be sequential. At least one appointment windows must be in the future.
Here are examples of appointment windows overlapping possibilities:
|
Scenario |
Type |
Description |
Status |
|
1 |
No overlap. |
Normal appointment windows, not overlapping |
HTTP 201. Shipment successfully created. |
|
2 |
Overlapping start stop 2 with end stop 1. |
AppointmentWindow.startdatetime on stop 2 overlaps with AppointmentWindow.enddatetime end for stop 1. |
HTTP 201. Shipment successfully created. |
|
3 |
Equal start and end on both stop. |
Appointment window are equal for each stop. |
HTTP 201. Shipment successfully created. |
|
4 |
Same start but stop2 ends before stop1 |
AppointmentWindow.startdatetime is equal for both stop 1 and 2 and AppointmentWindow.enddatetime for stop 2 ends before stop 1. |
HTTP 201 Shipment successfully created. |
|
5 |
Stop 2 start before stop 1 |
AppointmentWindow.startdatetime for stop 2 start before stop 1 and ends at the same time. |
HTTP 201 Shipment successfully created. |
|
6 |
Stop 2 ends before stop 1 starts |
AppointmentWindow.startdatetime for stop 2 start before stop 1 and ends at the same time. |
The final stop's appointment end time must be after the first stop's appointment start time
|
I don’t have a range for my appointment windows – just a set time. Can I submit the same value in both appointment window start and end times?
The appointment window range is used to calculate Early, Late, and On Time indications. A few options are listed below for the appointment windows:
-
If there are ranges in your system, send the range (e.g., 10am – 12pm)
-
If there is one set time, send the set time for both (e.g., 10am-10am)
-
Please note you’ll most likely never receive an On-Time indication if this is utilized unless we receive a geo-coordinate ping at the exact time of the appointment window.
-
If you have one time a truck must arrive by, you can hard code the appointment window range in the API call to start one hour before the time (e.g., 9am – 10am for instance).
What time zone will be used if I don’t provide a time zone for the appointment windows in my request?
The time zone of the stop location will be used if one is not specified.
Geo-coordinates.
Each shipment can have one BOL and one order number associated at the shipment level. However, we do support custom attributes and additional BOLs and order numbers can be stored as a custom attribute. Additionally, our Order Inventory service supports multiple order numbers. Contact your project44 Executive or Customer Service Manager for more information and to see if this option is a fit for your organization.
Are any of the settings for shipment creation configurable for all my loads (e.g., tracking end date / time logic)?
The settings that can be configured for all loads are:
-
Tracking start time:
-
Default is 90 minutes before appointment window – this can be configured as a tenant wide setting, but it is not recommended to go above 3 hours before the appointment window.
-
Types of geofences:
-
Default is to utilize the time based geofences for all shipments. This can be adjusted to distance based geofences for all shipments.
-
The time or distance can be configured (default is 15 minutes or 4000 meters).
-
Individual locations can also have custom geofences, overriding default settings.
-
Arrived Final Stop Configuration
-
Default is to complete tracking on a shipment 3 hours after truck arrives at final stop.
-
The time can be adjusted.
When creating or updating a shipment, the TL tracking system does not validate on the state field. This means that any state value can be used, and the shipment should track if a city and zip code are provided.
Via truck number, the unique identifier that indicates which truck in a carrier's fleet is moving a particular shipment. Truck number is defined within the carrier’s online ELD portal and must match exactly what is in the ELD. The carrier must have their ELD’s correctly mapped to the truck numbers.