Segment Naming: The Taxonomy Mistake That Breaks Every Report
You have three segments called VIP, two called Engaged, and one called Test_FINAL_v2. Nobody knows which one the report used, and the campaign went to the wrong 40,000 people because the name lied.
Segment naming is a taxonomy problem, and the mistake is treating the name as a label instead of a contract. A good name identifies who is included and what action the segment exists for, in a controlled vocabulary, with no version suffixes. LiveRamp's structure is seller, category, category, segment, with five or fewer categories and under 100 characters. Lexer's rule is simpler: the name says who is included and the desired action, and the description carries the rule.
The name is a contract, not a label
A segment name is the only thing most people ever read. The campaign manager reads the name, the analyst reads the name, the report reads the name. If the name does not say who is in the segment, the reader guesses, and the guess is usually wrong. VIP could mean top 10 percent by spend, or three or more orders, or anyone who has ever bought twice. Three segments called VIP, built on three different rules, will produce three different campaigns, and the report will not say which one it used.
The fix is a naming convention that is boring on purpose. The name identifies who is included and the desired action, and the description carries the rule. A segment called VIP_Winback_90d tells the reader who is in it, what to do with them, and how long they have been quiet. A segment called VIP tells the reader nothing, and the campaign that uses it is a gamble.
Related reading on this site: SegmentMuse and Cohort Segments: What the Month a Buyer Arrived Predicts cover the neighbouring problems in more depth.
No version suffixes, ever
The most common taxonomy failure is the version suffix. _v2, _new, _copy, _FINAL, _FINAL_v2: each one is a segment that was edited, copied, or replaced, and the suffix is the only record of which one is current. The suffixes accumulate until the list contains five versions of the same segment and nobody knows which one the report used. The rule is simple: no version suffixes. When a segment changes, edit it in place and document the change in the description, or retire it and create a new one with a new name.
The same rule applies to the naming of the rule itself. A segment built on a rule that says purchased in the last 90 days should not be named Loyal, because loyalty is a judgment and the rule is a fact. Name the fact. The judgment belongs in the campaign brief, not in the segment list.
The controlled vocabulary that keeps it working
A controlled vocabulary is a short list of approved terms, and it is what keeps a naming convention from drifting. Country codes follow ISO 3166, so US means United States and GB means United Kingdom, not UK or England. Time windows use the same units everywhere, so 90d means 90 days in every segment. Actions use the same verbs, so winback means the same thing in every campaign. LiveRamp's structure makes the same point at scale: seller, category, category, segment, with five or fewer categories and under 100 characters, hard limit 254.
The cost of getting this wrong is not theoretical. Gartner's 2020 estimate, widely cited in data quality write-ups, puts the cost of poor data quality at 12.9 million dollars a year per organization. That figure covers the whole data estate, not just segment names, but the segment list is where the cost shows up first: a campaign sent to the wrong 40,000 people, a report that compares two different VIP definitions, a win-back that targeted the customers who had already left. The taxonomy is the cheapest fix in the data stack, and it is the one most teams skip.
Frequently asked questions
What makes a good segment name?
A name that identifies who is included and what action the segment exists for, in a controlled vocabulary, with no version suffixes. The name says who is in it, and the description carries the rule.
Why are version suffixes bad in segment names?
Because _v2, _new, _copy, and _FINAL accumulate until the list contains five versions of the same segment and nobody knows which one the report used. Edit the segment in place and document the change in the description, or retire it and create a new one with a new name.
What is LiveRamp's segment naming structure?
Seller, category, category, segment, with five or fewer categories and under 100 characters, hard limit 254. The structure keeps names consistent at scale and makes them searchable across a marketplace.
What is a controlled vocabulary for segments?
A short list of approved terms: ISO 3166 country codes, the same time units everywhere, and the same action verbs in every campaign. It keeps a naming convention from drifting as the list grows.