Personyze Wiki Personyze Wiki docs
Open Personyze
Docs/ Campaigns/ Tags — Labelling Campaigns, Actions, Goals and Knowledge
Campaigns

Tags — Labelling Campaigns, Actions, Goals and Knowledge

Free labels you put on campaigns, actions, placeholders, goals and chat knowledge sources — to filter the panel, scope a dashboard, and narrow what the AI assistant answers from.

3 min read Updated 10 hours ago

A tag is a label you invent and stick on things: campaigns, actions, placeholders, goals, and
the knowledge sources behind the AI assistant. Create one once and it is available everywhere —
“Black Friday” means the same thing on a campaign as it does on a goal.

Tags exist because an account with two hundred campaigns cannot be read by scrolling. They are also the only way to
say “these things, whichever ones they turn out to be” to two features that need exactly
that.

Making one

The tag control sits on the item itself — a campaign, an action, a placeholder. Add tag opens
a picker with two halves: Pick existing, showing every tag on the account with how many items already
carry it, and Create new.

A tag has three things:

  • A name. Names are unique — a second Black Friday is refused rather than quietly
    created.
  • A colour, from fourteen swatches. Colour is what makes a list scannable.
  • A description, optional: “What this tag is used for…”. Worth filling in
    — it is the difference between a colleague using your tag and inventing a near-duplicate.
Tagging publishes nothing. An assignment is panel metadata, exactly like editing a description
— it does not touch the item’s version, does not go through staging, and changes nothing a visitor sees.
Tag a live campaign without a second thought.

A tag also survives a new version of whatever carries it: assignments are keyed to the item, not to the version, so
editing and republishing a campaign does not strip its tags.

Using them to find things

Every list screen that supports tags carries a Tags: filter with the account’s tags and their
counts, and a Clear tags to drop back to everything. Chips appear on the rows themselves, so a filtered
list still shows what else each item is.

The two places a tag does more than filter

Scoping the AI assistant

A chat or ask-box placement can answer from one tag’s sources rather than the whole knowledge
base — a box beside one product line reading a different shelf from the one on your support pages. Tags are put on
sources under AI Chat → Settings → Knowledge and chosen per placement.

Scoping a dashboard

A dashboard can be pointed at every campaign carrying a tag. This is
the one that pays for itself: new campaigns join the dashboard as they are tagged, with nothing to update. Tag your
Black Friday campaigns and the Black Friday dashboard is permanently correct.

Because both of these resolve a tag by name at the moment somebody reads them, renaming or deleting
a tag quietly changes what they cover. A chat placement scoped to a deleted tag widens to the whole knowledge base; a
dashboard scoped to one empties. Neither fails loudly. Rename a tag only when you mean to change what it
selects.

Deleting one

Delete tag says what it is about to do — “It will be removed from {n}
items”
— and removes the label from all of them. Nothing else is deleted: the campaigns, actions and
sources are untouched.

What to tag

Tags earn their keep when they name something the platform does not already know:

  • A season or moment — Black Friday, summer sale, Q3 launch.
  • A team or owner — who to ask about this.
  • A market — DACH, Nordics, LATAM.
  • A subject, for knowledge sources — shipping, returns, pricing.

Tagging by type — “popup”, “email” — is usually wasted, because the
list screens already filter on that.

Related

  • Dashboards — scope one to a tag and it stays current on its own.
  • Knowledge — tagging sources so a placement can read a narrower shelf.
  • Page groups — the same idea for URLs, used in targeting rather than in
    filing.
Did this page answer your question?
Thank you — that goes to whoever maintains this page.