Skip to content

add docs for wrong destination detection #537

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions docs/trip-tracking.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -411,6 +411,12 @@ Delay detection identifies trips at risk of being delayed or incomplete. To enab

If `scheduledArrivalAt` is set for a trip, delay information is captured in the trip's `delay` field. The `scheduledArrivalTimeDelay` is the predicted arrival delay from the `scheduledArrivalAt` time in minutes. The `delayed` flag is `true` when `scheduledArrivalTimeDelay` exceeds the delay threshold.

## Wrong destination detection

Wrong destination detection identifies the risk of the user traveling to a wrong destination. To enable this feature, turn on the `user.arrived_at_wrong_trip_destination` event on the [Settings page](https://radar.com/dashboard/settings#trips-settings) under *Trips*.

If the `user.arrived_at_wrong_trip_destination` event is enabled, an event will be triggered when the user enters a geofence with the same tag as the destination geofence but a different external id. For example, this may occur if the user accidentally goes to the wrong store of a franchise.

## Display live trips and ETAs

### In the Radar trip tracking dashboard
Expand Down
Loading