Deep Linking into Manager

Trackunit Manager exposes a /goto/ redirect endpoint that lets you link users directly to a specific resource. Use deep links from external systems such as emails, notifications, dashboards, ERP integrations, or support tools to send users straight to the right context.

How it works

Deep links follow this pattern:

https://new.manager.trackunit.com/goto/{domain}?id={id}&search={search}

Manager validates the parameters, resolves the resource, and redirects the user to the correct page. If the user is not authenticated, they are sent to the login page first and forwarded to the destination after signing in.

Supported domains

asset

Link directly to an asset in Manager. You can identify the asset either by its UUID or by a search term such as a serial number.

By asset ID (UUID):

https://new.manager.trackunit.com/goto/asset?id={assetId}

Parameter	Description
id	The Trackunit asset ID. Must be a valid UUID.

Example:

https://new.manager.trackunit.com/goto/asset?id=0b1f5a80-6f5f-4a5c-9e1a-8b9c3d4e5f6a

By search term:

If you don't have the asset UUID but know a machine serial number or other identifier, use the search parameter. Manager will attempt to resolve it to an asset.

https://new.manager.trackunit.com/goto/asset?search={searchTerm}

Parameter	Description
search	A search term to find the asset, for example a serial number.

Example:

https://new.manager.trackunit.com/goto/asset?search=SN-12345678

If the search term cannot be resolved to a single asset, the user is shown an error state.

iris-app-dev

Link directly to the developer settings page.

https://new.manager.trackunit.com/goto/iris-app-dev

This redirects to the developer account preferences and is useful for onboarding flows or documentation that guides users to enable developer mode.

Error handling

If a deep link targets an invalid or unresolvable resource — for example an id that is not a valid UUID or a search that matches no asset — Manager displays an error state instead of redirecting. Build your integrations to use known-good identifiers whenever possible.

Authentication

Deep links require the user to be authenticated. If the user is not logged in, Manager redirects to the login page and then forwards to the deep link destination after successful authentication.

In-app navigation with the SDK

If you are building an IrisX App and need to navigate within Manager programmatically — for example, linking from one extension to an asset page — use the useNavigateInHost hook instead of constructing URLs manually.

import { useNavigateInHost } from "@trackunit/react-core-hooks";

const { gotoAssetHome, gotoSiteHome, gotoFleetApp, gotoMarketplace } = useNavigateInHost();

// Navigate to an asset's movement tab
gotoAssetHome(assetId, { page: "movement" });

// Navigate to a specific app extension on an asset
gotoAssetHome(assetId, { irisAppId: "my-app-id", extensionId: "my-extension" });

// Navigate to a site
gotoSiteHome(siteId);

The SDK approach is preferred over URL construction because it handles routing internally and stays resilient to URL structure changes.

Use cases

Scenario	Deep link
Email alert links to the asset that triggered it	/goto/asset?id={assetId}
ERP system opens an asset by serial number	/goto/asset?search={serialNumber}
Onboarding guide sends users to developer settings	/goto/iris-app-dev
Support ticket links to a known asset	/goto/asset?id={assetId}