Anti-tamper function of trackers

Explanation on the physical and virtual anti-tamper function of the trackers.

Physical anti-tamper functionality

TRACK 1020 and TRACK 1030 have a physical button that detects when someone is removing the tracker from its asset to tamper with the tracking of the asset.

It is very important to correctly mount the tracker on its asset, as the anti-tamper function works with a real button. The tracker must be installed on its asset in such way that it the button is physically constantly pressed. This works well on hard surfaces such as metal, but is not recommended on softer surfaces. The tamper is detected when the button is no longer pressed. It is important to carefully read and follow the instructions of the installation and activation manuals.

Note: The tamper detection push API notification is different from how you collect other API events. To get tamper detection notifications via API, you should configure an alert rule instead of a Webhook. The alert rule type to use is: Physical tamper alert.

Virtual anti-tamper functionality

When talking about virtual anti-tamper functionality, the orientation sensor embedded in the tracker is used to detect the tamper. This approach can be used when the orientation of the tracker on its asset never changes during normal operations of the asset (for example the tracker is always positioned vertically). Whenever the tracker detects an unexpected change in orientation (for example the tracker is removed from its asset and suddenly is upside down), the tracker sends an orientation event to the platform and an alert is raised to warn about the tamper attempt.

This approach is only recommended for assets where the tracker can be installed in a way that it remains in the same orientation during all normally expected operations with the asset.

Note: If you want to receive the virtual anti-tamper events via API, you have to create a Webhook of data type orientation_event.