> For the complete documentation index, see [llms.txt](https://docs.g-iot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.g-iot.io/journey-to-getting-started-with-giot/10.-tracking-a-device.md).
# 10. Tracking a Device
Learn how to configure your device's location type to **Dynamic** or **Static**. This setting ensures optimal functionality tailored to your device's intended use case, whether for tracking moving assets or monitoring stationary objects.
{% hint style="success" %}
Location Type\
[https://app.gitbook.com/o/DKrl40rifuf7Bl8WIqXK/s/fEQ6KpTjmszWVWQqgcEa/\~/changes/202/low-cost-tracker-full-device-guide-book/low-cost-tracker-greater-than-giots-functions/lct-device-properties/lct-details-page/location-type ](/low-cost-tracker-full-device-guide-book/low-cost-tracker-greater-than-giots-functions/lct-device-properties/lct-details-page/location-type.md)
{% endhint %}
{% hint style="warning" %}
Only when the device is set to Dynamic it will be possible to generate the history locations of the device.
{% endhint %}
### Track Last position or
To visualize the last position of the **device**, simply add the **Map Widget** to the device dashboard. This will display the most recently updated position of the device.
{% hint style="success" %}
Widget- LCT Map [https://app.gitbook.com/o/DKrl40rifuf7Bl8WIqXK/s/fEQ6KpTjmszWVWQqgcEa/\~/changes/203/low-cost-tracker-full-device-guide-book/low-cost-tracker-greater-than-giots-functions/lct-device-dashboard/lct-add-widgets/lct-map-widget ](/low-cost-tracker-full-device-guide-book/low-cost-tracker-greater-than-giots-functions/lct-device-dashboard/lct-add-widgets/lct-map-widget.md)
{% endhint %}
### See positions within specific Timeframe
To view the **position history** of the **device** within a specific timeframe, ensure that the **Position Type** is set to **Dynamic**. Then, configure the **Map Widget** settings to define the desired timeframe. It is also possible to see the **Events time** directly on the **Map Widget side**
{% hint style="success" %}
Set location Type\
[https://app.gitbook.com/o/DKrl40rifuf7Bl8WIqXK/s/fEQ6KpTjmszWVWQqgcEa/\~/changes/202/low-cost-tracker-full-device-guide-book/low-cost-tracker-greater-than-giots-functions/lct-device-properties/lct-details-page/location-type ](/low-cost-tracker-full-device-guide-book/low-cost-tracker-greater-than-giots-functions/lct-device-properties/lct-details-page/location-type.md)
{% endhint %}
---
# 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.g-iot.io/journey-to-getting-started-with-giot/10.-tracking-a-device.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.
