--- title: "Spring '26 Project44 Truckload Tracking" slug: "spring-26-project44-truckload-tracking" tags: ["Compiled from User Guide", "Load Tracking", "Project44 - Load Tracking", "Spring '26"] updated: 2026-09-02T14:20:04Z published: 2026-09-02T14:20:04Z canonical: "documents.revenova.com/spring-26-project44-truckload-tracking" --- > ## Documentation Index > Fetch the complete documentation index at: https://documents.revenova.com/llms.txt > Use this file to discover all available pages before exploring further. # Spring '26 Project44 Truckload Tracking Project44 Tracking provides GPS/Cell-based tracking of loads via the driver’s (smart) phone or in-cab ELD. The Revenova TMS integration with Project44 Tracking provides Carrier load tracking and status updates sent from Project44 Tracking and received in the TMS. Project44 Tracking is a Load Tracking API service. For LTL quoting, tendering, tracking, and document retrieval, see the [Project44 LTL Carrier Aggregator API](/previous-releases/docs/spring-26-project44-carrier-aggregator) Service article. Project44 Tracking provides “push” status updates to the TMS via a sites-based web service. Inbound load status packets are processed as Platform Events. ## Setup ### **Enter Credentials** Enable the Project44 integration by completing the following steps. 1. Navigate to **TMS Admin**. 2. Select **Credentials**. 3. Select the **Global Services** tab. 4. Find Project44 Tracking in the list and open the card. 5. Check the **Enabled** and **Receive Updates** boxes. 6. Enter the **User ID** and **Password 1** into the text fields. 7. Click the **Save** button when finished. Valid credentials are required from a Project44 Tracking subscription. See examples in the table below. | User ID | Password 1 | Password 2 | Customer Number | | --- | --- | --- | --- | | Username in email address format | Required | | | ### **Remote Site Settings** Upgrading from previous versions of the TMS may have outdated information. Check that the Remote Site Settings for the Project44 integration URL are up to date. > [!NOTE] > There are TWO remote site settings required. One for the API and one for the BOL document URL. 1. Click the **Setup** gear icon in the top right corner. 2. From the drop-down, click **Setup**. 3. In the Quick Find Toolbar type *Remote Site Settings* and click the link. 4. From the list of remote sites find *Project44* and click the **Edit** link. 5. Update the Remote Site URLs to match the following. 1. Project44 (Service URL): https://na12.api.project44.com 2. Project44 BOL (BOL Document URL): https://s3-us-west-2.amazonaws.com 3. Project44 Test (Test URL): https://na12.api.sandbox.p-44.com ### **Experience Cloud Site Setup** Project44 relies on a “push” approach to event processing and requires a webhook to send information to the TMS. Create an API Site to accept inbound API traffic. 1. Create a Salesforce Site for API Guest User Access. 2. Set the public access for the Site. 3. Activate and Publish the Site. 4. Enter the API URL into the field for **Inbound API Community URL** under TMS Admin, in the Configuration section. 5. Add the following extension to the end of the URL to match the example below: /services/apexrest/rtms/tmslistener?org=00D180000008oA9EAI&source=Project44Tracking&pwd=4wGFDgnT950Ovg1 6. Send the post-back URL, the customer company name, and contact info to support.americas@project44.com. **{API Experience Cloud Site** **URL}** /services/apexrest/rtms/tmslistener?org= {18-character org id}&source=Project44Tracking&pwd= {credentials code field} **Example:** https://revenova.my.site.com/api/services/apexrest/rtms/tmslistener?org=00D180000008oA9EAI&source=Project44Tracking&pwd=4wGFDgnT950Ovg1 > [!WARNING] > The Salesforce-generated API [Experience Cloud](https://help.salesforce.com/s/articleView?id=experience.networks_overview.htm&type=5) Site URL is case sensitive. ### **Project44 Reference Data Keys** > [!CAUTION] > Warning: > > **These steps must be completed for TMS release versions 7.9.7, 7.10.3, 7.11, and forward.** Navigate to the [Project44 website](https://movement.project44.com/login) and log in. 1. Click the **9-dot square** to the left of your profile avatar. 2. Choose **Settings**. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Reference%20Data%20Keys%20-%201.png?sv=2026-02-06&spr=https&st=2026-07-29T01%3A30%3A42Z&se=2026-07-29T01%3A45%3A42Z&sr=c&sp=r&sig=ddftNvG9wajOq9talDk1RfrLUgFHcFNcFzcWGRjOJQo%3D) 3. Select Reference Data Keys. 4. In the **Keys** field, enter ***Carrier Sales Rep***, and then click **+Create**. 5. Repeat step 4 for ***Load ID***, and then ***Customer***. > [!NOTE] > The LoadId, Customer, and Carrier Sales Rep attribute 'predefined' is set to true. This attribute allows the filters in the Project44 web portal to work as intended. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Reference%20Data%20Keys%20-%202.png?sv=2026-02-06&spr=https&st=2026-07-29T01%3A30%3A42Z&se=2026-07-29T01%3A45%3A42Z&sr=c&sp=r&sig=ddftNvG9wajOq9talDk1RfrLUgFHcFNcFzcWGRjOJQo%3D) After creating the three **Reference Data Keys**, they are available in the **Tracking > Shipments** page to filter the Shipments Dashboard. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Reference%20Data%20Keys%20-%203.png?sv=2026-02-06&spr=https&st=2026-07-29T01%3A30%3A42Z&se=2026-07-29T01%3A45%3A42Z&sr=c&sp=r&sig=ddftNvG9wajOq9talDk1RfrLUgFHcFNcFzcWGRjOJQo%3D) > [!NOTE] > **Note**: > > Receiving "push" updates from Project44 does not require a listener URL. The URL is created automatically via the API when tracking is initiated. The webhook '**configName**' for tracking is: > > - Unified tracking: "unified-" + 18-character org ID > - Truckload tracking: "truckload-" + 18-character org ID ### **Transportation Profile** It is possible to set a default Tracking Provider for each Carrier on their **Transportation Profile**. **Tracking Provider**: The default selection in the Load Tracking Admin LWC of tracking information for a load. ## **Carrier Load Tracking** Carrier load tracking is initiated on the [Carrier Banner LWC](/previous-releases/docs/spring-26-carrier-banner). Click the antenna button to open the Load Tracking Administration LWC to begin tracking the load. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Carrier%20Banner%20LWC%20-%20In%20Transit%20(Load%20Tracking)(1).png?sv=2026-02-06&spr=https&st=2026-07-29T01%3A30%3A42Z&se=2026-07-29T01%3A45%3A42Z&sr=c&sp=r&sig=ddftNvG9wajOq9talDk1RfrLUgFHcFNcFzcWGRjOJQo%3D) Start and stop a tracking session by clicking the **On** and **Off** buttons. Active tracking sessions may be updated by changing load information and then click **Update Tracking**. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Load%20Tracking%20Administration%20LWC.png?sv=2026-02-06&spr=https&st=2026-07-29T01%3A30%3A42Z&se=2026-07-29T01%3A45%3A42Z&sr=c&sp=r&sig=ddftNvG9wajOq9talDk1RfrLUgFHcFNcFzcWGRjOJQo%3D) 1. Initiating the Load Tracking Administration LWC calls to Project44 with one of the Carrier TP identifiers: SCAC, DOT, or MC. 2. Project44 responds with the available methods for the Carrier. If they have ELD enabled in the Project44 system, they provide the **Truck Number** field, etc.. 3. If they do not have ELD, only the **Driver Phone** field populates. The TMS waits to hear from Project44 to know what fields are supported and then displayed. > [!NOTE] > - The default Tracking Provider for a Carrier is selected on the Carrier’s Transportation Profile on the *Settings* tab. > - Only tracking integrations with credentials display as possible options in the Tracking Provider picklist. > - Select Project44 Tracking for tracking Truckload Mode Loads. > [!WARNING] > The Project44 Truckload tracking integration supports multiple stops for the same Account location.