Alert rules
Stop checking dashboards and start getting told. Alert rules continuously monitor your assets and automatically raise the alarm when something needs attention — a vehicle hasn't returned, equipment has left a restricted area, or a zone is over capacity. Define the conditions once, and Track watches 24/7.
How alert rules work
You define a rule with a type, parameters, and severity. The system continuously evaluates device positions against your rules. When a condition is met — a device enters a restricted zone, stays too long in one place, or fails to return by a deadline — the rule triggers a violation.
Violations persist until the condition resolves. You can also configure webhook notifications to alert your team in real time.
Common properties
Every alert rule has these properties:
| Property | Description |
|---|---|
| Rule name | A human-readable name for the rule |
| Rule type | The type of condition to monitor (see below) |
| Severity | low, medium, high, or critical |
| Apply to | All devices, or a specific list of device IDs |
| Enabled | Whether the rule is actively being evaluated |
Rule types
| Rule type | What it monitors |
|---|---|
| Geofence entry and exit | Device enters or leaves a zone |
| Geofence containment | Device is outside all allowed locations during specified hours |
| Return to base | Device hasn't returned to its base location within a time limit |
| Scheduled return | Device hasn't returned to base by a specific time of day |
| Inactivity | Device hasn't reported a position for too long |
| Dwell time | Device stays in a location longer than expected |
| Movement detection | Device moves from where it should be staying |
| Minimum visit frequency | Device hasn't visited a required location within a time window |
| Unknown location | Device is at an unregistered location |
| Zone asset count | Too many or too few assets in a zone |
| Proximity association | Devices associate or disassociate based on proximity |
Location types
Alert rules work with both zone types:
- Network zones — Proximity-based zones defined by hotspot or reference beacon assignments. A device is "in" the zone when detected by a hotspot assigned to that zone. Best for indoor environments.
- Coordinate zones — Geographic boundaries drawn on the map (polygons or bounding boxes). A device is "in" the zone when its GPS coordinates fall within the boundary. Best for outdoor environments.
Both zone types use the same location_id parameter in alert rules. The system handles the different zone types automatically.
Zone tags
Many rules accept zone_tags as an alternative to listing specific zone IDs. Tag your zones (e.g., parking, storage) and reference the tags in rules. The system resolves the tags to matching zones automatically. See Use zone tags to manage rules at scale.