> For the complete documentation index, see [llms.txt](https://help.usejimo.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.usejimo.com/docs/analyze/users-and-segments/data-management/tags.md).
# Tags
**Dashboard path:** [Users & Segments > Data Management > Tags](https://i.usejimo.com/data/tags)
Tags are manual labels you assign to users. Use them for one-off categorization, flagging a user after a support call, marking someone as a beta tester, without setting up a custom attribute.
{% hint style="info" %}
When to use a tag versus a [custom attribute](/docs/analyze/users-and-segments/data-management/attributes/create-a-custom-attribute.md) is covered once, on the [Data Management](/docs/analyze/users-and-segments/data-management.md) group page. Short version: tags for manual judgments, attributes for data your systems push.
{% endhint %}
***
### This page is the only place tags are created
A tag has a lifecycle: it is **created and edited here**, and **selected everywhere else**.
That split is deliberate. On the [Users list](/docs/analyze/users-and-segments/audience/users.md#the-user-list), in a [user's profile](/docs/analyze/users-and-segments/audience/users/user-details.md), or in the [segment builder](/docs/analyze/users-and-segments/audience/segments/create-a-segment.md#the-condition-builder), you pick from tags that already exist. You cannot invent one on the spot. This keeps your tag list from filling up with near-duplicates typed in a hurry.
***
### The tag list
| Column | What it shows |
| ------------------- | --------------------------------- |
| **Name** | The tag, with its colored icon |
| **Amount of users** | How many users currently carry it |
| **Author** | The teammate who created it |
{% hint style="info" %}
**Managing tags**, top-right, links to this documentation.
{% endhint %}
***
### Create a tag
**+ New Tag** opens the creation modal.
| Field | |
| -------------------------- | --------------------------------------------------------------------------------------- |
| **Color** | Seven presets. The icon takes the color, and so does the pill wherever the tag appears. |
| **Name** | Required. **Save stays disabled until you enter one.** |
| **Description** (optional) | A short note on what the tag means, so the next person understands it. |
{% hint style="success" %}
**Name a tag for the whole team, not for today.** `Beta Testeur`, `Nocontact` and `Internal` read clearly six months later. A tag called `tmp` or `test` does not. Use the description if the name alone is not obvious.
{% endhint %}
***
### Edit or delete a tag
The **...** menu at the end of each row offers two actions.
**Edit preferences** reopens the modal with the color, name and description pre-filled. Everything is editable, including the name: unlike an attribute's code name, a tag name is not a contract with your code, so renaming it is safe. The change applies everywhere the tag is used.
{% hint style="danger" %}
**Deleting a tag removes it from every user who carried it.** If a tag is used as a condition in a [segment](/docs/analyze/users-and-segments/audience/segments.md), deleting it changes that segment's audience, and therefore who any experience targeting that segment reaches. Check where a tag is used before deleting it.
{% endhint %}
***
### Where tags are used
Once a tag exists, you apply or leverage it from three places. None of them can create a tag, only set or view existing ones.
#### **On the Users list**
From the [global user list](/docs/analyze/users-and-segments/audience/users.md#the-user-list), click **+ Add tag...** in the Tags column of any row. A dropdown lists your existing tags with checkboxes: tick to apply, untick to remove. You can apply several at once.
#### **On a user's profile**
The **Tag user** button in the [user profile](/docs/analyze/users-and-segments/audience/users/user-details.md) header opens the same checkbox dropdown. Applied tags show as colored pills next to the user's name.
#### **As a segment condition**
In the [segment builder](/docs/analyze/users-and-segments/audience/segments/create-a-segment.md#the-condition-builder), the attribute picker has a **Tags** category. Pick a tag to build a rule like *has the tag Beta Testeur*, and target every user who carries it.
{% hint style="info" %}
This is what makes tags more than a note: because they are filterable, a handful of manual labels turns into a targetable audience. But if you find yourself tagging dozens of users on a rule you could write in words, that rule belongs in a [segment](/docs/analyze/users-and-segments/audience/segments.md), not in a tag.
{% endhint %}
***
### Related pages
* [Data Management](/docs/analyze/users-and-segments/data-management.md): when to use a tag versus an attribute
* [Users](/docs/analyze/users-and-segments/audience/users.md): apply a tag from the list
* [User details](/docs/analyze/users-and-segments/audience/users/user-details.md): apply a tag from a profile
* [Segments](/docs/analyze/users-and-segments/audience/segments.md): use a tag as a targeting condition
* [Attributes](/docs/analyze/users-and-segments/data-management/attributes.md): the other kind of user data