Tag
A Tag in Salesforce is a user-defined keyword or short phrase that you attach to a record.
Definition
A Tag in Salesforce is a user-defined keyword or short phrase that you attach to a record. It groups that record with others and lets you find it again through tag search. There are two kinds. Personal tags stay private to the person who applied them. Public tags are visible to everyone in the org once the feature is switched on.
Tagging is a Salesforce Classic surface. The tag section sits at the top of a record detail page, behind an Add Tags or Edit Tags link. Salesforce documents the whole Tags UI as Classic only.
That makes tags the older option for organizing records by keyword. Lightning Experience covers the same ground with Personal Labels for private sorting and Topics for a shared vocabulary. Tags still work wherever Classic works, and they are not on any published retirement list, but a new build should not start here.
In plain English
“Think of a sticky note with one word written on it. You stick it on a folder so you can find that folder again later. Some of these notes only you can see, and others the whole office can see. Salesforce tags work the same way, except they only appear in the older version of the screens.”
Worked example
Priya runs renewals at a 90-person logistics software company that still works in Salesforce Classic. Before her quarterly push she opens a dozen Accounts and clicks Edit Tags at the top of each record detail page. Into the Public Tags box she types renewal_Q4 and at_risk. Later she opens the Tags page and selects renewal_Q4 and at_risk together. Salesforce returns the six Accounts carrying both labels, because selecting more than one tag filters with AND rather than OR. Her teammates see those same public tags. The personal tag call_first she added stays visible to Priya alone.
How tagging works, and where it runs out
Free text by design, and that cuts both ways
Nobody predefines the allowed values. A user types a word into the Personal Tags or Public Tags box on a record detail page, saves, and the label exists. Salesforce accepts letters, numbers, spaces, dashes and underscores, and insists on at least one letter or number. So renewal_Q4 is valid and renewal/Q4 is not. You can enter up to 10 tags at a time, and auto-complete narrows a list of tags that already exist as you type. That suggestion list is the only nudge toward consistency the feature gives you. The upside and the downside arrive together. You can categorize forty Accounts in two minutes without filing a request for a custom field. Within a week you also have follow up, follow-up and followup sitting side by side. Tags are good at helping you find something again and bad at helping you count anything.
Personal tags and public tags are two different features
The split is about who can see a tag and who can clean it up. Personal tags are private. You see only the ones you created, and a colleague looking at the same Account sees nothing at all. Public tags appear to every user in the org, which turns tagging into a shared vocabulary the team can search against. Switching public tags on is where Salesforce's own documentation disagrees with itself. Tag Settings in Setup presents Enable Public Tags as an ordinary checkbox, and its help article lists four steps with no mention of Support. A separate knowledge article, Enable Public Tags in Salesforce Classic, says a system administrator has to submit an activation request with Salesforce Support first. Open Tag Settings in your own org before you promise anyone a date. Renaming or deleting a public tag needs the Tag Manager profile permission, because that edit lands on every user's screen rather than just yours.
The limits are lower than people assume
Each user gets 500 unique personal tags and 5,000 instances of personal tags applied to records. That second number counts applications, not distinct labels, so one popular tag stuck on 5,000 records burns the entire allowance by itself. Org-wide the ceilings are 1,000 unique public tags, 50,000 instances of public tags applied, and 5,000,000 instances of personal and public tags combined. The public tag numbers usually bite first, since a shared namespace fills up faster than any one person's private list. When you get close, the Personal Tag Cleanup page in Setup lets someone with Customize Application delete the personal tags left behind by deactivated users. There is no undo on that deletion, so check before you click.
Topics and public tags cannot share an object
This rule catches people out. Enabling topics for an object disables public tags on records of that object type, and personal tags are unaffected. So the moment an admin turns topics on for Accounts, the public tags already applied there stop being usable, with no automatic conversion. Salesforce made that call deliberately, because two overlapping keyword systems on the same record is a support case waiting to happen. The practical read is to decide per object which one you want. Topics have their own detail page, work in both Salesforce Classic and Lightning Experience, and cover Chatter posts as well. Public tags do none of that. Choosing today, topics is the safer bet.
Why tags are the legacy option now
The tag section on a record detail page never came across to Lightning Experience. Salesforce says so plainly in its own knowledge article: the Tag Manager permission and the Tags UI are available only in Salesforce Classic. Tags are not supported in Lightning Experience at all. Lightning answers the private half with Personal Labels. Each user gets 20 labels per object and 200 in total, with up to 500 records per label. Personal Labels covers a dozen-odd record types, Accounts, Contacts, Cases and custom objects among them. Topics answer the shared half. So the honest read is that tags are a maintenance surface rather than a build surface. If a Classic org already runs on them, leave them alone. If someone proposes tags for a new process, point at Topics and Personal Labels instead.
How organizations use Tag
Scopes tagging to Case page layouts only in Tag Settings. Support leads get a keyword surface for recurring policy-wording problems, and Accounts and Opportunities stay clean.
Audits public tag usage before the cutover. The tag section does not exist in Lightning, so anything built on tags has to be rebuilt with topics, list views or reports.
Trust & references
Cross-checked against the following references.
- Tag Settings (opens in new tab)Salesforce
- Salesforce Professional Edition Allocations (opens in new tab)Salesforce
- Enable Public Tags in Salesforce Classic (opens in new tab)Salesforce
- Enable Tag Manager Permission in Salesforce Profiles (opens in new tab)Salesforce
- Organize and Find Records Easily with Personal Labels (opens in new tab)Salesforce
Straight from the source - Salesforce's reference material on Tag.
Hands-on resources to go deeper on Tag.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He writes and edits salesforcedictionary.com, published by KineticBit Inc., to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
+5 pts / dayQ1. An admin enables Topics for the Account object in an org that already uses public tagging. What happens to public tags on Accounts?
Q2. What are the per-user tag allocations in Salesforce?
Q3. A rep in a Lightning Experience only org wants a private way to flag records and pull them back up later. What do you point them at?
Discussion
Loading discussion…