Geofencing
Alert Rules
Alert rules define what happens when an asset interacts with a geofence. Configure entry, exit, dwell, and speed triggers to monitor your assets and receive timely notifications.
Standard triggers
Standard triggers are available on all plans and cover the most common geofencing scenarios.
| Trigger | Fires when | Configuration |
|---|---|---|
| Entry | An asset enters the geofence boundary | Immediate on crossing |
| Exit | An asset leaves the geofence boundary | Immediate on crossing |
| Dwell | An asset stays inside the geofence for too long | Set dwell time in minutes |
| Speed | An asset exceeds a speed limit within the geofence | Set speed threshold in km/h |
Entry and exit triggers
Entry and exit triggers fire the moment an asset crosses the geofence boundary. Each trigger is independent -- you can enable entry alerts without exit alerts, or both.
Dwell trigger
The dwell trigger fires when an asset remains inside a geofence for longer than a configured duration. Set the dwell time in minutes (e.g., 30 minutes). The alert fires once when the threshold is reached. If the asset leaves and re-enters, the dwell timer resets.
Speed trigger
The speed trigger fires when an asset exceeds a configured speed limit while inside the geofence. Set the threshold in km/h. The alert fires each time the speed is exceeded, subject to cooldown settings.
Corridor triggers (Enterprise)
Corridor geofences (RouteGuard) support additional triggers designed for route compliance monitoring.
Enterprise feature
Corridor triggers are available exclusively on the Enterprise plan. Standard geofence triggers (entry, exit, dwell, speed) work on all plan types.
| Trigger | Fires when | Configuration |
|---|---|---|
| Deviation | Asset leaves the corridor boundary | Set deviation distance in meters |
| Checkpoint arrival | Asset arrives at a checkpoint | Automatic on proximity |
| Checkpoint missed | Asset skips a checkpoint | Fires after passing the checkpoint zone |
| Checkpoint sequence | Asset visits checkpoints out of order | Compares actual vs expected sequence |
| Checkpoint time window | Asset arrives outside the expected time | Set earliest and latest arrival times |
| Progress | Asset reaches milestone percentages | Default milestones: 25%, 50%, 75% |
| Direction | Asset travels the wrong way | Fires when direction opposes the defined route |
| Route speed | Asset exceeds a segment speed limit | Set speed limits per route segment |
| Stalled | Asset stops moving for too long | Set stall time in minutes |
Deviation trigger
The deviation trigger fires when an asset moves outside the corridor boundary by more than the configured distance. For example, if the corridor width is 100 meters and the deviation threshold is 50 meters, the alert fires when the asset is more than 150 meters from the route center line.
Checkpoint triggers
Checkpoints are named points along a corridor route. You can monitor:
- Arrival: Confirm that an asset reached a checkpoint
- Missed: Detect when an asset bypasses a checkpoint entirely
- Sequence violation: Detect when an asset visits checkpoints in the wrong order
- Time window: Detect early or late arrivals at checkpoints (set expected arrival windows)
Progress milestones
Progress alerts fire when an asset completes 25%, 50%, and 75% of the route. Milestones are calculated based on distance along the corridor path.
Stalled trigger
The stalled trigger fires when an asset stops moving for longer than a configured duration while inside the corridor. Set the stall time in minutes. This is useful for detecting breakdowns or unplanned stops on a route.
Debounce settings
GPS signals can jitter near geofence boundaries, causing rapid entry/exit toggles. Debounce settings prevent false triggers.
- Entry debounce: The asset must remain inside the geofence for this many seconds before an entry alert fires. Default: 10 seconds
- Exit debounce: The asset must remain outside the geofence for this many seconds before an exit alert fires. Default: 30 seconds
Tip
Increase the exit debounce for geofences near roads or parking areas where GPS accuracy may fluctuate. A 60-second exit debounce eliminates most false triggers.
Alert severity
Each alert rule can be assigned a severity level that determines how the alert is displayed and prioritized:
| Severity | Color | Use case |
|---|---|---|
| Info | Blue | Routine events (e.g., arrival at checkpoint) |
| Warning | Yellow | Situations that need attention (e.g., approaching dwell limit) |
| Critical | Red | Urgent events requiring immediate action (e.g., unauthorized zone entry) |
Severity affects the visual presentation of alerts in the dashboard and can be used to filter the alert list. Critical alerts also display a persistent badge in the navigation bar until acknowledged.
Cooldown periods
Cooldown periods prevent alert spam by enforcing a minimum time between repeated alerts of the same type for the same asset and geofence combination.
- Set the cooldown in minutes (e.g., 15 minutes)
- During cooldown, subsequent trigger events are logged but do not fire new alerts
- Cooldown applies per asset, per geofence, per trigger type
For example, a speed alert with a 5-minute cooldown will fire at most once every 5 minutes per asset, even if the asset repeatedly exceeds the speed limit.
Target filtering
By default, alert rules apply to all assets that interact with the geofence. You can narrow the scope:
- Specific assets: Select individual assets from the list
- Categories: Apply the rule to all assets in one or more categories (e.g., "Delivery Vans")
- All assets: Monitor every asset in the organization (default)
When filtering by category, any asset added to the category in the future will automatically be covered by the rule.
Managing alerts
Viewing alerts
Open the Alerts page from the sidebar to see all fired alerts. The list shows:
- Alert type and severity
- Geofence name and asset name
- Timestamp of when the alert fired
- Current status (active, acknowledged, resolved)
Use the filters at the top to narrow by severity, type, geofence, asset, or date range.
Alert actions
| Action | Description |
|---|---|
| Acknowledge | Mark the alert as seen. Stops the persistent badge for critical alerts |
| Resolve | Mark the alert as handled. Moves it to the resolved list |
| Mute | Temporarily suppress future alerts for this asset/geofence combination |
| Unmute | Re-enable alerts for a previously muted combination |
Bulk operations
Select multiple alerts using the checkboxes and apply bulk actions: acknowledge all, resolve all, or mute/unmute selected combinations.
Alert history
Pointeron maintains a full audit trail of all fired alerts. The alert history includes:
- The trigger type and configured parameters
- The asset position at the time of the alert
- Timestamps for when the alert was fired, acknowledged, and resolved
- The user who acknowledged or resolved the alert
Alert history is retained for the duration of your subscription. Export alert history as CSV from the Alerts page for external reporting.