You can trigger actions based on rules you define. This is done in a IFTTT (If This Than That) way. You can name the rule and assign it to asset groups.

1. Name & asset group assignment



Name your trigger.

Type / Priority

Event or episode where a episode has a begin and end. In contrast to a event that does not have a duration.

The priority determines how the notification will be labeled.

Minumum duration

Use this to disregards (too) short episodes. Below this threshold the episode will be ignored.

Asset groups

Select one or more asset groups the trigger applies to.


To start you have to define rules. You can pick from a list of rules, each of them having different paramaters to update the rule as per your requirements.

  • Tracker sensors outside specs

You can set sensor thresholds on devices. For instance you can create a frozen spec (< 0 degrees). When the sensors go outside this spec or have no value while a value is expected this sensor will be triggered.

  • Tracker status

This will look at the device state calculated in our backend. You can check on

  • Idling
  • Ignition on
  • Ignition off
  • External power lost
  • Buffered communication
  • GPS fix lost
Tracker status rule
  • Geofences

You can select outside all or inside any, or select a individual geofence to enable the trigger.

In a next release we will also add the option to work with geofence groups

Geofence rule
  • IO Port (Input / Output)

You can select physical IO ports that have to be enabled to trigger this rule. You can select the hardware ports for the device here. So for instance IO input 1 and condition ‘On’ or ‘Off’.

IO Port rule
  • IO Port (Logical)

Besides physical ports, you can also select the logical ‘mapped’ meaning regardsless on which physical input it’s connected. You can select the logical ports for the device. For instance ‘Ignition on’ or ‘Airconditioning on’. This will look for the mapping of the specific device

IO logical
  • Event

You can select a device event to look for. For instance a Cornering or Harsh acelleration event. These events are triggered by the device and are often not very long so work best when in event mode. They require the device configuration to be updated to trigger the chosen event as well.

Event rule
  • Schedule

You can define a schedule in the settings menu. Then you can add this rule and determine if the trigger should fire when in or outside this schedule.

Schedule rule
  • Speed

You can define a preset speed to check upon. When you select type ‘Roadspeed’, every location will be checked with our roadspeed database to make sure you are within the right speed limits. So it will use the speed limits relative to the road.

Speed rule
  • Temperature (degrees celcius)
  • Weight (kilograms)
  • Humidity (% humidity)
  • External power (voltage)
    You define a temperature/weight/humidity to trigger upon
Temperature/Weight/Humidity/External power rule
  • Avg Deviation Detection

Can be used to detect anomolies. The system will compute a running average and if the new sensor value deviates from this average by the given threshold it will trigger. Use a negative % to detect drops, use positive % to detect increase.

You can use it to detect loading/unloading events when using a weight sensor. Or to detect a sudden change in temperature.

Avg Deviation Detection


Now that we’ve set the conditions for the trigger to fire, we are ready to define actions. Actions can be:

  • Store event in database as episode
  • Notification message by email
  • Webhook


The message that will be sent when the trigger is fired can be fully customized. You can change the body and subject of the message and include {{variables}}.

Depending on the selected contact group the notification will be sent via email or sms.


Tip: you can test the output of a trigger by using the ‘Test’ button. You will receive a message as if all the conditions of the rules were met.


Seatbelt off while driving

– Speed > 20kmh for more than 30 seconds
– Logical Input ‘Seatbelt violation’ is True

Speeding over 130km/h after 7PM

– Speed > 130kmh
– Schedule ‘after 7PM’ active

Using the asset outside working hours

– DeviceState = Ignition On
– Schedule ‘weekend’ active

Using the asset outside allowed areas

– DeviceState = Igntion On
– Outside geofence groups ‘X, Y, Z’
Updated on July 12, 2022

Related Articles

Leave a Comment