Tags

Tags are a single workspace-wide vocabulary used to label and filter campaigns, journeys, segments, templates, Asset Library files, Content Blocks, and other taggable entities. Type a tag once and it appears in the picker for every entity that supports tagging - no more typo-divergence between "promo", "Promo", and "promotion".

Every tag belongs to the workspace's shared pool. Attaching a tag to a campaign and later typing the same name on a segment reuses the same tag - renaming it once renames it everywhere.

Where tags appear

You can attach tags to:

• Campaigns (including in-app campaigns)
• Journeys
• Segments
• Email templates
• In-app templates
• Wallet pass templates
• Content Blocks
• Asset Library files
• AI agents

Each of these has a Tags field on its create/edit form and a tag filter on its list view.

Tagging an entity

Tagging happens right where you already work: the create or edit form of each entity carries the same Tags field. Type or pick tags, then save the entity - tags are stored together with the rest of the form, so there's no separate "save tags" step. Editing later works the same way: open the entity, adjust its pills, save.

Because the picker draws from the shared workspace pool, tagging a brand-new campaign with an established tag like winback immediately connects it to every dashboard filter, list filter, and usage report that tag already appears in.

The tag picker

The tag picker is the same component everywhere:

• Type to search. Matching tags from the workspace pool appear as suggestions; click one to attach it. With an empty query, the picker lists the pool alphabetically.
• Create inline. Press Enter (or click the create row) on a query that doesn't match anything to create a new tag - it's added to the workspace pool immediately and becomes available to every other entity type.
• Selected tags render as removable pills above the input; click the x on a pill to detach it.
• An entity can carry up to 50 tags, which is far more than you should ever need.

Some surfaces use the same picker in filter mode - same search and pills, but selection filters a list instead of tagging an entity, and nothing is created on the fly.

Tag management

Open Data → Tags in the sidebar (at /data/tags) to see the full tag pool for the workspace. The management page gives you:

• Search and pagination over the pool, with sorting by name or by total usage.
• Create - add a tag ahead of time, optionally with a color. The color is used for the tag's swatch wherever it renders, so families of tags (say, all lifecycle-stage tags in one hue) are recognizable at a glance.
• Rename - changes propagate to every entity using that tag. The edit dialog shows how many entities the rename will touch before you confirm.
• Recolor - update the swatch without touching the name or attachments.
• Delete - removes the tag from every entity that carries it (the entities themselves are untouched, they just lose the label).
• View usage - opens a breakdown of exactly which entities carry the tag, grouped by type (campaigns, canvases, segments, email templates, in-app templates, wallet templates, content blocks, assets, AI agents) with per-type counts. Check this before renaming or deleting so you know which tags are load-bearing.

Filtering by tag on list views

List views that support tagging (campaigns, journeys, segments, templates, and so on) have a tag filter above the table. Selecting one or more tags narrows the list to entities that carry any of the selected tags - selecting promo and q3 shows everything tagged with either.

The filter combines with the view's other filters (status, channel, search) as you'd expect: an item must match the tag filter and every other active filter to appear.

A worked convention

Here's a small, battle-tested taxonomy for an e-commerce workspace - three orthogonal dimensions, one color each:

Dimension	Tags	Color
Lifecycle	acquisition, activation, retention, winback	teal
Season / moment	q3, black-friday, summer-sale	amber
Owner	team-growth, team-crm	lavender

With this in place, "everything the CRM team ran for Black Friday" is a two-tag filter away, and every new campaign takes about five seconds to file correctly.

Common workflows

• Assemble a launch. Tag the campaign, its journey, the segments it targets, the email template, and the hero images in the Asset Library with the same launch tag (spring-launch). During and after the launch, one filter on each list view pulls up the entire footprint.
• Season cleanup. After a seasonal push, open Data → Tags, find the season's tag, and use View usage to walk through everything it touches - archive what's done, keep what's reusable, then delete the tag itself if it won't come back.
• Audit before deleting. A tag with a large usage count is load-bearing. View usage shows exactly which campaigns, journeys, segments, and templates would lose the label, per type, before you commit.
• Rename with confidence. Renaming bf to black-friday updates every attachment at once - the edit dialog tells you how many entities are affected, so a typo fix never requires touching entities one by one.

How tags stay consistent

A few behaviors worth knowing, all consequences of the single shared pool:

• Names are matched case-insensitively. Typing "Promo" where "promo" already exists attaches the existing tag rather than creating a duplicate.
• Tags are workspace-scoped. Each workspace has its own pool; tags don't leak between workspaces. (Org-global wallet pass templates are the one nuance - their tags are visible wherever the template is.)
• Deleting an entity never deletes its tags from the pool - only that entity's attachments. A tag with zero usage stays available in the picker until you delete it from the management page.

FAQ

Are tag names case-sensitive? No. "Promo", "promo", and "PROMO" resolve to the same tag; the pool keeps one canonical spelling (the one it was created with - rename it if you'd like a different casing).

Is there a limit on tags per entity? Yes, 50 per entity - generous enough that hitting it is a sign to prune, not to raise it.

Do tags carry over between workspaces? No. The pool is per workspace. If two workspaces need the same taxonomy, create it in each (the tag manager makes that a two-minute job).

What happens to a tag when I delete the last entity using it? Nothing - the tag stays in the pool with a usage count of zero, still available in every picker, until you delete it from Data → Tags.

Can I merge two tags? Not in one click. Filter each list view by the tag you want to retire, re-tag those entities with the surviving tag, then delete the retired one - View usage gives you the checklist.

Tips

• Keep tag names short and lowercase. "promo" beats "Promotion - End of Quarter Push" - long tags clutter the pills and filter rows. Use the entity's name or description for context.
• Establish a small shared convention. Tags shine when the whole team uses the same handful: a lifecycle dimension (acquisition, retention, winback), a seasonal dimension (q3, black-friday), maybe an owner dimension. Two or three orthogonal dimensions cover most filtering needs.
• Avoid tag soup. A handful of well-curated tags (5–20 per workspace) is far more useful than hundreds of one-off labels. Open Data → Tags every quarter, sort by usage, and prune the zero- and one-use stragglers.
• Use colors for families. Give all tags in the same dimension the same color so a pill row reads like a legend.
• Tags are labels, not folders or permissions. An entity can carry many tags and a tag implies no access control. For team-level access scoping, use Roles & Permissions.