How Optional GPS Tracking and Route History Work
Optional GPS tracking adds route history for selected users alongside normal check-in records. An administrator enables it separately for each user. It is distinct from GPS Point proximity validation.
Requirements
Enable GPS tracking only for users who need route history.
The user must be signed in to the mobile app and have a current Location selected.
Location services must be enabled and TARGPatrol must have device location permission.
Enable GPS tracking for a user
Open Users, edit the required user account, turn on “Enable GPS tracking,” and save the changes.
When coordinates are recorded
After it starts, the mobile app records an initial position and then periodically records additional coordinates while the app is open and in use. This is not continuous live or background tracking, and it does not record positions after the app is closed.
Without an internet connection, supported location records can be stored locally on the device and synchronized after connectivity returns.
Review route history on the map
Authorized managers open Site Views → Maps, select a Location and date, and then review the user history. The map can show saved positions, the resulting route, and the latest available position.
GPS Point validation and GPS tracking are different
A GPS Point validates proximity to saved coordinates only when a check-in is attempted. Optional GPS tracking periodically records location for a selected user while the app is in use. Learn more in How GPS Point Proximity Validation Works.
Privacy and permissions
Enable this feature only for users who need it for their work. Provide appropriate notice to personnel, manage device permissions, and follow applicable laws and internal policies.
Using GPS samples for Location geofencing
Location geofencing is an additional opt-in, not another name for route history. With both user switches enabled and a saved, enabled Location boundary, newly synchronized GPS samples can record outside and return events on Base and Enterprise. Review these in the User or Location Geofence tab, not in route history.
English interface: GPS tracking and Geofence tracking are separate options. Monitoring also requires Location access and an enabled Location boundary.
Geofence tracking is a separate, per-organization opt-in. Existing users are not enrolled automatically. Turning GPS tracking off also disables geofence tracking; turning GPS back on does not re-enable it. A Location boundary alone is not enough to monitor a user.
Supported offline samples can synchronize later. Events use the phone measurement time, while server detection may happen after reconnection. Duplicate or older out-of-order samples do not rebuild event history. Do not treat the latest recorded event as a guarantee of someone’s current position.
Newly processed samples use the latest saved boundary, including delayed offline samples. Editing a boundary does not recalculate old events and can affect how the next sample is classified, even without movement. Switching the selected Location resets the observation baseline; it is not a confirmed return to the previous Location.
Location geofencing: setup and event history