> For the complete documentation index, see [llms.txt](https://docs.motus.org/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.motus.org/en/tags/appendix/tag-retrieval.md). # Retrieving lost tags ## Manual tracking basics Coming soon... ## Retrieving lost tags Lotek NanoTags can be retrieved by manually tracking the tag with a Lotek handheld receiver. Since these receivers have a long range at full gain, it can take a long time to locate a tag that has been lost, but manual tracking is still routine for researchers . When touching the ground, the tag signal is modulated enough that a trained ear can actually identify the tag as being detached just by the quality of the audio signal the receiver emits. Without a Lotek receiver you can use the open-source SensorGnome receivers instead, but they are much more difficult to use in this way since there is a longer time delay between when a detection occurs and when it shows up on the receiver’s display. Further, SensorGnome receivers do not offer a real-time gain adjustment, whereas Lotek receivers do. \[Insert information on CTT Tags] \[Insert methods for retrieving tags] --- # 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.motus.org/en/tags/appendix/tag-retrieval.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.