> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/tag-tracking/configuring-the-tag-tracking-feature/tag-tracking-reader-settings.md).

# Tag Tracking Reader settings

**The Minimum accepted signal strength**

The 'Minimum accepted signal strength' provides an approximate control for the distance from the Reader within which a tracking tag will be read. A lower minimum accepted signal strength allows the Reader to read tracking tags that are farther away.

1. Click **Configure** from the menu bar, then **Hardware**.

   The Hardware List Window opens.
2. Right-click the Gallagher T-Series Readers for which you want to set the 'Minimum accepted signal strength', and select **Properties**.
3. Click the **Tag Tracking Settings** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-6174f10e5bcf68d0a5c25e40cc1f33e7b6c27661%2Freader_tagtrackingsettings.png?alt=media)
4. In the **Minimum accepted signal strength** field, enter the signal strength (in dBm) that this Reader will require for it to read a tracking tag. Received signal strengths less than this value will be ignored.

   **Recommendation:** To give the Reader the best chance of receiving advertisements from a tag that passes it, Gallagher recommends leaving the 'Minimum accepted signal strength' as the default value (-127).

   This will best counter the factors that can impact the received signal strength, including:

   * Transmission strength configured within the tag
   * Tag low battery
   * Objects that may alter the radio path loss between the tag and the reader
   * Atmospheric conditions.
5. Click **OK** to close and save your changes.

   Click **Cancel** to close without saving your changes.

   Click **Apply** to save your changes and stay in this window.


---

# 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://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/tag-tracking/configuring-the-tag-tracking-feature/tag-tracking-reader-settings.md?ask=<question>&goal=<user_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.
