> 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.md).

# Tag Tracking

### Introduction

The Tag Tracking feature is intended for tracking the location of participating Cardholders. Tag Tracking has not been designed for anti-theft functionality, or for scenarios where the tag holder may attempt to obscure their location.

The Tag Tracking feature allows you to assign iBeacon and Eddystone Bluetooth™ 'tracking tags' to Cardholders. A Cardholder's Bluetooth™ tracking tag can be read by Gallagher T-Series Bluetooth™-capable Readers to update the Cardholder's location when they pass near a Reader. Command Centre Tracking Tag Types (like Card Types) are required for you to assign new tracking tags to Cardholders. Tracking tags can only be assigned to Cardholders in the Command Centre Client.

**Warning:** Gallagher recommends you do **not** use tracking tags for physical access into secure areas because tags can be easily copied, and the communication from tags to Readers is not encrypted, authenticated, or guaranteed.

***

### Licensing

Tag Tracking is a licensable feature. You must purchase the following licence to configure tracking tags in Gallagher Command Centre:

`[Limits]`\
`Tracking Tags=X`

Where `X` is the maximum number of tracking tags that can be assigned across your Command Centre system. Once the maximum has been reached, no more tracking tags can be assigned until one or more are removed.

***

### Considerations

<table><thead><tr><th width="186">Item</th><th>Consideration</th></tr></thead><tbody><tr><td><strong>Access Control</strong></td><td>Gallagher recommends you do <strong>not</strong> use tracking tags for access control or for any security purposes.</td></tr><tr><td><strong>Surrounding environment</strong></td><td>Environments with metal obstructions or high amounts of Bluetooth™ noise can impact how efficiently tracking tag advertisements are received by Readers.</td></tr><tr><td><strong>Reader positioning</strong></td><td>Readers must be positioned far enough apart that a tag is read by the correct reader (i.e. the reader that will update the Cardholder's location to the zone they are entering).</td></tr><tr><td><strong>Access Decisions</strong></td><td>When a Cardholder's tracking tag is read at a Reader, an access decision is made and the Cardholder's location is updated.</td></tr><tr><td><strong>Supported Access Modes</strong></td><td><p>Tracking tags require the Access Mode of the entry zone to be 'Secure - No PIN', 'Code or Card - No PIN', or 'Free - No PIN'. PIN and Dual Auth Access Modes are not supported.</p><p>In 'Secure - No PIN' and 'Code or Card - No PIN' modes, a Cardholder's location is only updated if access is granted. In 'Free - No PIN' mode, an access granted decision is not required for the Cardholder's location to be updated; Access Group membership, Competencies, and tracking tag status are ignored.</p></td></tr><tr><td><strong>Unlocking Doors with tracking tags</strong></td><td><p>If using tracking tags to unlock physical doors (not recommended), note that:</p><ul><li>Cardholders may unlock Doors from a considerable distance without realising.</li><li>A Door may be unlocked by one of a group of Cardholders, and it is not clear to the group which one of them was granted access.</li><li>If a Cardholder unlocks a Door but does not enter before the Door re-locks, the Cardholder needs to move outside the range of the Door's Readers before they can unlock it again. Or, the Cardholder can unlock the Door with a different credential (e.g. a card).</li></ul></td></tr><tr><td><strong>Enabling/disabling tracking tags for Doors</strong></td><td>You can disable a Reader from letting tracking tags unlock a Door - while still tracking their location - by not assigning an ‘Unlock output’ to the Reader’s Door. However, this will disable all credential types (e.g. cards, Mobile Credentials) from unlocking that Door. You cannot disable tracking tags from unlocking a Door while allowing other credential types to unlock that Door.</td></tr></tbody></table>

***

### Card expiry

The 'card expiry' feature allows the life of a tracking tag to be specified by defining a 'From' time and date as well as an 'Until' time and date. Tracking tags with these defined are therefore enabled between those two points in time. When that time has passed, they are expired due to 'Scheduled Card Expiry'.

The 'Inactive Card Expiry' feature provides an additional way that tracking tag expiry can be defined. Inactive Card Expiry enables the automatic disabling of tracking tags, invoked after a period of tracking tag inactivity, within a Command Centre controlled site. The period of inactivity is configured on the Tracking Tag Type item.

***

Select the item below that you require further detail on:

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Configuring the Tag Tracking feature](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/tag-tracking/configuring-the-tag-tracking-feature.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Setting up Tracking Tag Types](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/tag-tracking/setting-up-tracking-tag-types.md)

**Note:** Tracking tags can only be assigned to Cardholders in Gallagher Command Centre Client. Refer to the topic *"Tag Tracking tags in Command Centre"* in the Gallagher Command Centre Online Help.


---

# 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.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.
