What's new 
We have some enrolled mobile devices that are used almost only for Hexnode UEM with location tracking enabled. There are no app updates or other major activity on these devices, but the Hexnode app seems to consume close to 1 GB of mobile data per month. Location tracking is set to run frequently, around every 15 minutes. Is there a way to reduce the data usage without turning location tracking off completely? I also saw mentions of Time-Based Policies and was wondering if location tracking can be limited to business hours only.
23 Views
Replies (3)
Marked SolutionPending Review
Hexnode Expert
1 day ago
Sep 02, 2026
Marked SolutionPending Review
Yes. For devices that do not need to be tracked 24/7, the recommended approach is to use Time-Based Management so location tracking is active only during the required time window. You can configure this from:
- Go to Policies > General Settings > Time Based Management.
- Create or edit a schedule for the required tracking window, such as business hours.
- Configure the location tracking settings within the policy that should apply during that schedule.
- Associate the policy with the required devices or device groups.
This helps reduce total monthly data usage because the device does not need to send location updates throughout the entire day. Also make sure the Hexnode agent on the device is updated, as recent versions include location tracking optimizations such as reduced payload size and more efficient background syncing.
Marked SolutionPending Review
Participant
17 hours ago
Sep 02, 2026
Marked SolutionPending Review
So if the interval is still 15 minutes, but the schedule is only 8 AM to 6 PM, it should stop using data for location pings outside that window? We don’t really need overnight tracking.
Marked SolutionPending Review
Hexnode Expert
18 minutes ago
Sep 03, 2026
Marked SolutionPending Review
Correct. If location tracking is configured through a time-based policy, it will apply only during the active schedule. Outside that scheduled window, those location tracking settings will not keep running from that policy. For best results, keep only the settings that must always remain active in a regular baseline policy. Then use a separate time-based policy for location tracking during business hours. This avoids unnecessary location syncs outside the required period.
Save