Technical · Course T6Lesson 1 of 4
WeTrack: location intelligence in operation
8 min read- Enable and tune tracking at the policy level for each platform
- Use the WeTrack tab's analysis tools — snap to road, grouping, exports
- Explain why a stationary device posting nothing is correct behavior
WeTrack turns the fleet into a live map: where every device is now, where it has been, and how long it sat at each stop. It's the We-suite product operations teams open every morning — which means you need to configure it well and explain its behavior precisely.
Turning it on: the policy Track tab
No data flows until tracking is enabled on the policy (Policy Groups → policy → Track tab). Three settings define the telemetry:
- Location Post Frequency — how often the device reports, from 30 seconds to 1 hour. Faster reporting means fresher maps and hungrier batteries.
- Displacement — post only after moving a set distance. Android lets you tune it; iOS and Windows are fixed at 100 m by the OS, which is the answer to a common "why can't I change this?" ticket.
- Backup Sync Frequency — how often locally-buffered data syncs to the cloud, typically 30 minutes or 1 hour.
Two requirements make or break the deployment: location services must be on at the device, and the policy's restrictions should prevent users from turning them off — otherwise your tracking program depends on end-user goodwill.
The subtlety worth internalizing: a ping requires both the interval to pass and the displacement to be crossed. A parked van posts nothing all weekend, and that silence is correct behavior, not an outage.
Reading the map
Per device, the story lives in Devices → device → WeTrack tab:
- Snap to Road aligns raw GPS points to the road network — trails become routes.
- Grouped Location clusters dense ping fields so high-activity zones read clearly instead of as noise.
- Time selection filters the trail (last 24 hours by default); clicking any point reveals speed and GPS accuracy.
- A red dot marks a device in motion (under a minute at that spot); a stationary icon marks five-plus minutes in place — dwell time at a glance.
The Download icon exports the analysis — timestamps, coordinates, speed, and time-at-location — as CSV or PDF, which is exactly what fleet customers want for job-site verification.
For the whole-fleet view, the sidebar's WeTrack entry maps last-known locations across policies, filterable by policy group, tag, or IMEI.
Where geofencing plugs in
Geofences ride on WeTrack's location stream: boundaries drawn in the policy's Geofence section trigger entry/exit alerts and in-fence restrictions, and an inactive fence keeps its coordinates while pausing enforcement — handy for holidays. The full geofence build-out (zones, alerts, restrictions, check intervals) lives in the Policy Mastery course; operationally, remember the diagnosis order for "alerts aren't firing": fence active → device online → location services on.