> For the complete documentation index, see [llms.txt](https://help.tahua.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tahua.io/knowledge-base/administrator-help-guides/applications/application-templates/personalisations-and-field-tags.md).

# Personalisations & Field Tags

Field Tags can be assigned to any field within your Registration, Application, Assessment, or Milestone templates. Once assigned, the data collected in that field becomes a **Personalisation** — allowing it to be pulled through automatically into templates and data reports.

**Creating a Field Tag**

1. Click on the field you want to tag to open the field focus menu.
2. Under **Field Tag**, click **Create new Tag**.
3. Enter a name for the tag and click the **green tick** to save.

Alternatively, if a tag already exists, select it from the **Select a Tag** dropdown instead.

**What are Personalisations?**

Once a field has a Field Tag assigned, the data collected from that field can be referenced elsewhere in the system as a Personalisation. This means you can automatically pull applicant-specific information through to:

* **Templates** — addressing applicants by name, referencing their application details, and so on.
* **Data reports** — surfacing tagged field data for reporting purposes.

<figure><img src="/files/e6qJIiRhSJJtIF8UbX68" alt=""><figcaption></figcaption></figure>

**Field Tags vs. Cell Tags**

If your form includes a table field, you have two different tagging options that look similar but behave differently — see [Creating Tables](/knowledge-base/administrator-help-guides/applications/application-templates/creating-tables.md):

* **Field Tag** — tags an entire field/question. This powers Data Reports and Data Tables, as described above.
* **Cell Tag** — tags a single cell within a table field (e.g. one column in a budget or schedule table), rather than the field as a whole. Cell Tags can be used for personalisations in Contract and Letter templates, and are also available as Data Report options — appearing under a **Tagged Form Cells** category — for both Application and Milestone/Deliverables templates.

If a tagged field isn't showing up as an option in a Data Report, check the field's type (some field types, such as labels/headers, can't be tagged for reporting) and confirm the tag is actually set — see [Milestones FAQs](/knowledge-base/administrator-help-guides/milestones/milestones-faqs.md) for more detail.

To rename or delete an existing Field Tag, and to understand what happens to your templates and reports when you do, see [Renaming & Deleting Field Tags](/knowledge-base/administrator-help-guides/contracts/contract-templates/renaming-and-deleting-field-tags.md).

**Duplicating pages, sections, fields or tables**

Field Tags and Cell Tags **are** carried over when you duplicate a page, section, field, or an entire table (including any Cell Tags on its columns) — but they're copied exactly as-is, tag name and all. This means the duplicate ends up sharing the same tag as the original, rather than starting untagged.

Since tag names are meant to uniquely identify one piece of reportable data, this is worth checking after any duplication: if you don't intend the copy to feed the same report column/personalisation as the original, remove or replace the tag on the duplicate (via the field's tag menu, or centrally under **Settings > Tags** — see [Renaming & Deleting Field Tags](/knowledge-base/administrator-help-guides/contracts/contract-templates/renaming-and-deleting-field-tags.md)) before publishing.