Tag
Contacts & dataAlso called: label, contact tag
A tag is a simple label attached to a contact that records a fact about them — a source, an interest, a state — and which automations can react to, branch on, and use as an exit condition.
Tags earn their place by being both data and control surface. Adding one records something; adding one can also start a sequence, stop a sequence, or change which path a contact takes. That dual role is why tags become the backbone of a CRM faster than any other object.
It is also why tag sprawl hurts. A workspace with 300 tags, forty of which mean roughly downloaded-something, cannot be branched on reliably by anyone who did not create them. Tags need a naming convention early, when it is still cheap.
The useful discipline is to distinguish state tags from event tags. A state tag describes what is true now (customer, unsubscribed, trial) and should be removed when it stops being true. An event tag records that something happened (attended-webinar-march) and should never be removed.
How it works in FrazzleCRM
- ✓Add Tag and Remove Tag are steps; tag added and tag removed are triggers; tags are branch conditions and goal events.
- ✓Stop tags are configured per automation and cancel active runs when applied.
- ✓The audit maps the full relationship graph of which automations add, remove and watch which tags — the fastest way to find out what a tag actually does before you rename it.
- ✓Tags are matched by name, so casing and spelling conventions are functional decisions, not cosmetic ones.
Where teams get this wrong
Using a tag both as a trigger for a flow and as something that flow applies creates a loop. It is the single most common way to accidentally send thousands of messages, and worth checking every time a tag appears in two places.
Common questions
Tags or custom fields?
Tags for yes/no facts you want to branch and trigger on. Custom fields for values you need to store and merge into a message — a renewal date, a plan name, a quoted price.
Should I remove tags when they stop being true?
For state tags, yes, or your branches drift out of date. For event tags recording that something happened, no — history should not be rewritten.
See it on a real map
Free templates where this shows up as an actual node. Clone one and the diagram runs as the automation.
Quiz Funnel + Segmentation
One quiz, three audiences — score the answers and send each segment a different email.
Lead genReferral & Partner Program
Onboard partners, track who sent whom, and pay out without chasing a spreadsheet.
EventsTrade Show Lead Follow-Up
Work the badge scans within 48 hours, while they still remember your booth.
Related terms
Custom field
A custom field stores a value on a contact that the standard fields do not cover — a renewal date, a plan name, a quoted price, an external system's id — for use in personalisation, branching and date-driven automation.
Stop tag
A stop tag is a tag that cancels a contact's active runs in an automation as soon as it is applied — the emergency brake that stops a sequence for someone who has unsubscribed, complained, bought, or otherwise stopped being the right audience.
Trigger
A trigger is the event that starts an automation for a contact — a tag being added, a form submitted, a link clicked, a date arriving — deciding both who enters the flow and when.
If/Else branch
An If/Else branch evaluates a set of rules about the contact at the moment the run reaches it and sends them down one of two paths, letting a single automation behave differently for different people.
Or browse all 24 terms — grouped by what part of the funnel they belong to.
Draw it once, and it runs
In FrazzleCRM the funnel map IS the automation — every node you draw is a real step, and every step you edit redraws the map. Free plan, no credit card.
Start free