Sometimes you want to spot something about a record at a glance — a high-priority deal, a strategic account, a record that needs attention — without opening it and reading fields. Color-coded object tags give records a visual label so your team can scan a list and instantly see what matters, instead of clicking into each one. They're a small usability feature, but used with discipline they make a busy CRM faster to work in. Used carelessly, they become a rainbow of meaningless stickers. Here's the practitioner's read on creating and using them well.
What are color-coded object tags, and what are they for?
They're visual labels you attach to records so a category or status shows up at a glance in list and board views. Where a property holds data, a tag is about quick visual recognition — a colored marker that says "this one's different" without the reader parsing a field. They suit a small set of high-signal states: priority level, account tier, a record that needs review. The key word is small. A tag's value comes from instant recognition, and instant recognition collapses the moment there are twenty colors meaning twenty things. Worked example: tagging your top 50 strategic accounts gold lets a rep scanning the company list see them immediately — useful precisely because it's one tag with one clear meaning, not one of dozens.
How do you create them?
Set them up in HubSpot's settings for the object, defining each tag's label, color, and the rule or manual action that applies it. Tagging capabilities live in your object and record settings (availability depends on your edition). You define each tag — its name and its color — and decide how records get it: manually by reps, or automatically based on a property or a workflow. Automatic tagging is usually cleaner because it stays consistent; manual tagging relies on every rep remembering the convention. Before you create a single tag, agree on what each one means and write it down, because a tag system without a shared definition drifts within weeks. Worked example: a tag that auto-applies "At risk" to any customer whose renewal is under 60 days away and whose health score dropped stays accurate on its own — far more reliable than asking reps to remember to flag at-risk accounts by hand.
When do tags help, and when do they hurt?
They help when there are a few clear, agreed-on states; they hurt when they multiply into a system nobody remembers. The failure pattern is always the same: tags feel free to create, so everyone adds their own, and within a quarter records carry five colors whose meanings no one agrees on. The discipline is to keep the set short, give each tag a single owner-approved meaning, and prefer automation so application stays consistent. Also remember tags are for visual scanning, not analysis — if you need to filter, segment, or report on something, that belongs in a property or a list, not a tag. Worked example: "high-value deal" as a tag helps a rep eyeball the board; but if you want to report on high-value deals, that should be a property-driven view, because you can't reliably report on a manually applied sticker.
How do you keep the tag system clean over time?
Limit who can create tags, review them periodically, and retire any that have lost a clear meaning. Like every flexible feature in a CRM, tags decay without governance. Restrict tag creation to admins or a small group, keep a short documented list of approved tags and what they mean, and do a periodic cleanup — merge duplicates, delete the orphans, confirm the automation still applies them correctly. This is exactly the order we follow with clients: define the small set of meaningful tags first, automate their application where possible, then govern them so the system stays legible. A handful of well-maintained tags is genuinely useful; an ungoverned pile is just noise with colors.
The IV-Lead take
Color-coded tags are a usability tool, not a data tool — they make a record's status legible at a glance, and that's their whole job. Their value is entirely a function of restraint: a few tags with agreed meanings, applied consistently (ideally by automation), governed so they don't multiply. Anything you need to filter or report on belongs in a property, not a tag. Keep the set small and the meanings shared, and tags speed your team up instead of cluttering the screen.
Is your CRM cluttered with tags, fields, and labels nobody agrees on? Book a 30-minute portal audit — we'll show you what to keep, what to automate, and what to retire. For the bigger picture, see how we keep HubSpot clean and usable through HubSpot implementation and optimization.
Frequently asked questions
What's the difference between a tag and a property?
A property holds data you can filter, segment, and report on; a tag is a visual label for quick recognition in a view. Use a tag when you want to spot something at a glance, and a property when you need to analyze or automate on it.
Should tags be applied manually or automatically?
Automatically wherever possible, because automation keeps them consistent across the whole team. Manual tagging works for small teams with discipline, but it drifts as soon as reps forget the convention — so tie tags to a property or workflow when you can.
How many tags is too many?
If your team can't recite what each color means without looking it up, you have too many. A short list of high-signal tags beats a large palette, because the whole value of a tag is instant recognition that breaks down once the set grows.
Can I report on tagged records?
Tags are built for visual scanning, not analysis, so anything you need to report on reliably should live in a property instead. If you find yourself wanting to filter or segment by a tag, that's a signal it should have been a property all along.
