> 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/command-centre-client/using-command-centre/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 Gallagher Command Centre Client.

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

### Licensing

Tag Tracking is a licensable feature. Your Command Centre licence file must contain the following option:

`[Limits]`\
`TrackingTags=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.

<details>

<summary>Assigning Tag Tracking tags in Command Centre</summary>

### Introduction

After the Tracking Tag Type has been configured in Gallagher Configuration Client, tracking tags can be assigned to Cardholders in Gallagher Command Centre Client.

**Note:** Tracking tags can only be assigned to Cardholders in Gallagher Command Centre (not in Configuration Client).

### Configuration

To assign and activate a Cardholder tracking tag, perform the following procedure in Gallagher Command Centre:

1. From the Cardholder Viewer, locate the Cardholder you want to assign a tracking tag to.
2. On the Cardholder Cards tile, click the **Assign Card** button.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-b3b3405a2b7748c20a32dc1250b0c2eef849f555%2Fcardholdercards_cardinfo2.png?alt=media)

   The Assign Card pop-up displays.
3. From the **Card Type** drop-down list, select a Tracking Tag Type.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-359db54b6b0ceeb97f6f1411f39c2198ba5760b8%2Fassigncard_trackingtag.png?alt=media)
4. From the **State** drop-down list, select a state for this tracking tag.
5. In the **Number** field, enter the unique tracking tag number.

   **The tracking tag number:**

   * For iBeacon tags, the tag Number is made by joining the tag's MAC Address (6 bytes) with the tag's configured Major number (2 bytes) and its Minor number (2 bytes), in that order. The total length is 20 hexadecimal characters (10 bytes). For example: '3ec9bfecfc428adc7eda'.
   * For Eddystone tags, the tag Number is the tag's Instance ID. The total length is 12 hexadecimal characters (6 bytes). For example: 'e4d7f38f9e96'.

   **Note:** If required, you may find a tracking tag's details by finding and using an appropriate mobile device app.
6. In the **From** field, select the date and time from which this tracking tag will be activated. If the Tracking Tag Type has Card Defaults configured, you may leave this field as the default.
7. In the **Until** field, select the date and time at which this tracking tag will expire. If the Tracking Tag Type has Card Defaults configured, you may leave this field as the default.
8. Select the **Resident** check box if you require the details of this Cardholder to be stored (resident) at the Controller. This is unchecked by default.
9. Click the **OK** button.

   If valid, the **Assign Card** pop-up will close and the tracking tag will appear in the grid in the Cardholder Cards tile.

   **Note:** If you want to cancel your changes before saving, click the **Revert to Saved** button.
10. Click the **Save** button.

</details>


---

# 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/command-centre-client/using-command-centre/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.
