Understand the tracker behavior

The asset trackers can be configured for a specific behavior that is appropriate for the specific asset type or for the use case at hand. This page explains different configuration options.

View the tracker's configuration

The applied configuration settings for a particular tracker can be found by following the steps described in this task.

Applied configuration profile

The behavior of a tracker is controlled by a large number of configurable configuration settings.

Tracker configuration profiles specify the appropriate values for the vast majority of the configurable settings, and allow the user to specify custom values for some particular settings.

The idea is that each tracker product type, use case or asset type will have its own tracker configuration profile.

The first line in the Tracker configuration page shows which profile is applied to this tracker (1), and specifies between brackets what values are applied to the configurable settings in the profile (2):



Supported services

The configuration of a tracker defines its behavior in the scope of a number of services it supports. Each supported service can be tuned by specifying the values of its particular settings.

The Tracker configuration page explains the behavior for each service in details and specifies which values are applied for the configurable settings.

The following services are often available for many tracker product types:

  • Location service
  • User data service
  • Battery service
  • Data communication service
  • Environmental sensing service
  • Tamper alert service
  • One or more analytics services

A number of services are explained in more details below.

Location service

The location service dictates when the tracker should determine its location and send location updates, and which Localization technologies to use.

The Location service widget summarizes how the tracker is configured and how it will behave in the context of the location service:



User data service

The user data service explains which types of third party data properties are available for this particular tracker. This explains which addition information can be managed for the asset that is tracked with this tracker.



Battery service

The Battery service explains whether or not the system predicts the remaining battery autonomy based on battery properties and historical tracker behavior.



Data communication service

The Data communication service specifies which rules apply for the tracker when it comes to sending data to the Internet.

This comprises for example:

  • How many messages the tracker is allowed to send in a given time period.
  • Whether or not the tracker will try to send data while it is moving.
  • Whether and how the tracker will try to recover from data loss.


Environmental sensing service

The Environmental sensing service specifies whether the given tracker is monitoring environmental conditions through a Bluetooth Low Energy (BLE) connection with external sensors.

In addition, the service specifies how frequently the tracker reads sensor data from these sensors, whether any aggregation function is applied on the measured values, and how frequently this data is updated to the platform.



Tamper alert service

The tamper alert service specifies whether the tracker should send an alert when it is detached from its asset or not.