Tags
Manual labels you assign to users by hand, for the judgments no system holds. Create and manage them here; select them everywhere else.
Dashboard path: Users & Segments > Data Management > 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.
When to use a tag versus a custom attribute is covered once, on the Data Management group page. Short version: tags for manual judgments, attributes for data your systems push.
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, in a user's profile, or in the segment 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
Name
The tag, with its colored icon
Amount of users
How many users currently carry it
Author
The teammate who created it
Managing tags, top-right, links to this documentation.
Create a tag
+ New Tag opens the creation modal.
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.
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.
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.
Deleting a tag removes it from every user who carried it. If a tag is used as a condition in a segment, 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.
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, 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 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, 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.
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, not in a tag.
Related pages
Data Management: when to use a tag versus an attribute
Users: apply a tag from the list
User details: apply a tag from a profile
Segments: use a tag as a targeting condition
Attributes: the other kind of user data
Last updated