Tracker switched ON


This rule is used to notify users when the tracker is powered on. The event simply indicates that the tracker was switched on. Different tracker manufacturers may implement this event differently, so in order to stay with the exact interpretation - you should take this event as an event related just to device power-on feature indication.

In a business setting, this rule proves valuable for monitoring the tracker's operational patterns. For instance, it aids in tracking instances where the tracker has remained inactive or switched off for an extended duration. Receiving notifications about power-on events and, subsequently, generating reports based on this data offer essential insights. These insights can be utilized for analyzing work schedules, evaluating tasks conducted on the tracker or associated vehicle during periods of inactivity, work performed on the tracker or the vehicle (when it is off), and facilitating assessments of data consumption upon tracker power-on events.

There is a difference between the "Tracker switch ON/OFF," "Tracker switched ON," and "Tracker switched OFF or lost connection" rules.

  • "Tracker switch ON/OFF" encompasses the core essence of two hardware events that are tracked and provided to the platform. It is based on the hardware logic of paired ON or OFF events triggered by pressing the ON/OFF button.
  • "Tracker switched ON" (currently reviewed rule) is a separate rule that captures events only when the device is turned on. It does not provide information about turning off.
  • "Tracker switched OFF or lost connection" is a rule where the event is generated on the platform side. The tracker is either turned off or has lost connection with the platform for an unspecified reason, whether it's an unexpected or anticipated scenario. Usually, this event is associated with a connection timeout and, as a result, a red status of the tracker.


As this rule is based on hardware configurations, there is not much to configure in the rule itself.

Bind zone to rule:

Enables geofence rule binding.


Fill out the section if the rule needs to work only inside/outside of the selected geofences.

Map button:

Shows bound geofences on the map.


Emergency notification:

is used for important events. A message on the screen and the sound signal can only be disabled by clicking on the notification. Please note, some browsers can block notification sound until user activity is recorded on the page.

Push notifications:

Receive push notifications on the mobile app and web interface.

Add geofence name to the notification:

Adds names of the specified geofences to the notification text. This option is available only when the "Inside" geofence binding radio button is selected on the "Settings" tab.

SMS notifications:

List of recipients for SMS notifications when the event occurs.

Email notifications:

List of recipients for email notifications when the event occurs.


Set a schedule for when the rule will run. If your schedule indicates that the event should not run some day or time period, it will not appear as a notification in the user interface, and notifications via SMS or email will not be sent. Additionally, you can choose a default template for quick scheduling.

The platform specifics:

  • The "Tracker switched ON" alert has a 1-minute reset timer, meaning the alert event will not occur more often than once every 1 minute. If this type of event occurs in time the rule has been waiting for the reset, this event will be omitted by the platform, including the reports.
  • In this rule type, users have the flexibility to select multiple trackers which they wish to receive notifications from. The only requirement is that the selected trackers must support Tracker switched ON events and the feature must be integrated on the platform for given trackers. This means that users can choose multiple compatible trackers to receive notifications from, allowing them to monitor harsh driving events across various vehicles or devices in a convenient way.
  • Whenever the platform identifies a hardware event of this type from a packet of tracker data with no valid coordinates in it, the platform counts the event as a valid one and displays it regardless of whether the event occurred within or outside the bound geofences. The logic of the Inside/Outside radio buttons is also ignored in this case. This behaviour is due to the fact that showing a controversial event once more is better than omitting it.

Event reports

To view the dates when the events were received, you can build the "Report on all events" report.

Tracker switched ON
Tracker switched ON
Video Telematics NEW
Video Telematics NEW
Review incidents
Determine liability
Coach drivers
Learn more >

This website uses cookies.
See our Privacy Policy to learn more.