> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/health/ph-v1.8/access/public-health-product-suite/health-campaign-management-hcm/device-tracking-user-manual.md). # Device Tracking User Manual A step-by-step guide for device tracking ## Overview The device tracking feature in the app enables the user to store the location(coordinates) of the device. ## Key Features It can be used to: * Track the device path. * Display data in dashboards to visualise the user’s movement. * Identify areas where the user spends more time (multiple coordinates captured for the same location indicate ongoing activity) * Verify whether a distributor has stayed within the assigned area or deviated from it. * Fraud Detection: Detect potential fraud by monitoring unusual or inconsistent movement patterns This helps in understanding user behaviour and activity patterns in specific areas. ## Steps 1. Coordinates will be captured automatically after a specific time interval as soon as the user selects the project. 2. Users will receive notifications about the location captured. 3. Then it will be shown as the unsynced records in the app, which can be synced to the server by clicking on the sync data button or by auto-syncing. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.digit.org/health/ph-v1.8/access/public-health-product-suite/health-campaign-management-hcm/device-tracking-user-manual.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.