How it connects
Renttix authenticates against Trackunit's Iris platform using OAuth2 client credentials. You create an application credential pair in Trackunit and enter it in the Renttix telematics settings, where it is held encrypted rather than in plain text. From there readings are pulled against your assets and stored with their source, provider and timestamp recorded. Because the same asset record carries both telematics and manual readings, a machine without a tracker fitted still works the same way — the difference is only in where the number came from, and that difference is visible.
Why it matters
Trackunit is heavily used across construction plant, which is exactly the fleet where hours matter most. Servicing on those machines is hours-based, and hire is often priced with a usage element, so the reading is both a maintenance trigger and a billing input. Without an integration, that data lives in a tracking portal that the workshop and the hire desk do not open. The information exists but does not reach the decisions it should inform — a machine goes out overdue for service because nobody checked the portal, or a usage charge goes unbilled because nobody reconciled it. Bringing readings into the asset record puts the number where the decision is made.
Key workflows
Hours-based service scheduling
Engine hours arrive from Trackunit against the asset, so service intervals trigger on actual running hours rather than on an estimate or a date.
Usage that reaches the invoice
Readings are recorded with the context they were taken in, including off-hire, so usage across a hire can be established from the record and billed rather than written off.
Credentials held encrypted
The OAuth2 client credential pair you create in Trackunit is stored encrypted, and Renttix obtains its own short-lived tokens from it rather than holding a long-lived secret in the open.
Trackunit is one of three telematics options in Renttix, alongside Samsara and the OEM-standard AEMP interface. Whichever you use, readings land on the same asset record and feed the same service, utilisation and billing logic.
Trackunit integration FAQ
An OAuth2 client credential pair created in Trackunit, entered in the Renttix telematics settings. Renttix exchanges it for short-lived access tokens; the credentials themselves are stored encrypted.
That is the normal case. Assets without telematics record readings manually against the same asset record, with the source marked as manual — so mixed fleets work consistently and you can always see which figures came from a machine.
It drives service scheduling, utilisation reporting and usage-based billing. The point of bringing readings out of the tracking portal is that they reach the decisions they should inform.
Ready to modernize your rental operations?
Payments + deposits enabled • Quick setup • No credit card trial