Segment naming conventions: the unglamorous practice that saves your team hours
Somewhere in your ESP there is a segment called 'Q3 test FINAL v2' that half the company is afraid to touch. Naming is infrastructure, and yours is crumbling.
Why segment names are load-bearing
Segment names are the interface between the people who build audiences and the people who use them. When the names are cryptic, every campaign starts with archaeology: opening the segment, reading the rules, guessing the intent. Multiply that by every campaign and the cost is enormous.
Bad names also cause real errors. 'High value' in one team's segment means top spenders; in another's it means high margin. A campaign targeting the wrong 'high value' segment sends luxury offers to discount buyers or vice versa. The name was the only documentation, and it lied.
The chaos compounds over time. Segments get cloned, renamed casually, and abandoned. After two years, the library is a graveyard of 'test,' 'final,' and 'do not use' segments, and nobody can tell which ones are safe to delete. A convention prevents the graveyard; nothing else does.
A naming taxonomy that actually works
The convention needs four elements: the segment's purpose, its defining criteria, its refresh behavior, and its owner. A workable pattern is PURPOSE_CRITERIA_REFRESH_OWNER: for example, WINBACK_90D_NO_PURCHASE_DAILY_CRM. Anyone reading it knows what it is, who it covers, how fresh it is, and who to ask about it.
Keep the vocabulary controlled. Maintain a short list of approved purpose codes, WINBACK, ACQUISITION, RETENTION, SUPPRESSION, TEST, and require new codes to be proposed, not invented. The moment someone creates WIN-BACK2, the convention is dead.
Include the refresh behavior because staleness is the silent killer. A segment named with DAILY tells the campaign manager it is current; one named STATIC warns them to check the build date. This single element prevents more errors than any other part of the name.
Handling the dimensions that do not fit
Not every attribute belongs in the name. The name should carry identity and freshness; the description field should carry the full rule logic in plain language. Require a description on every segment: who is in it, why it exists, and when it was last reviewed.
Versioning needs a rule too. When segment logic changes, the version goes in the description and the name stays stable, unless the meaning changed enough that old references would mislead. Renaming breaks every campaign that references the segment; versioning in place preserves continuity.
Date-stamped segments deserve special handling. Campaign-specific segments like HOLIDAY_2026_GIFT_BUYERS should include their season and be archived, not deleted, when the season ends. Archived segments with clear names become templates for next year instead of mysteries.
Migrating a messy library without breaking campaigns
Do not rename everything at once. Start by freezing new segment creation under the old chaos: every new segment follows the convention from today forward. The mess stops growing, which is half the battle.
Then work backward by usage. Rename the segments attached to active campaigns first, coordinating with the campaign owners, and leave the abandoned ones for a dedicated cleanup sprint. Renaming an unused segment risks nothing; renaming a live one without telling its owner risks everything.
For the truly abandoned segments, archive rather than delete. Move them to an archive folder with their last-used date. After a year of disuse, delete them. The archive is the safety net that makes the cleanup politically possible.
Enforcing the convention after the cleanup
Conventions die without enforcement. Assign one person as the segment librarian with the authority to reject non-conforming names. This sounds bureaucratic; it is the difference between a convention and a suggestion.
Build the convention into the creation flow. A segment builder template with required fields for purpose, criteria, refresh, and owner makes compliance the path of least resistance. People follow conventions that are easier than the alternative.
Audit quarterly. Pull the full segment list, flag the non-conforming names, and review the abandoned ones. Fifteen minutes a quarter keeps the library clean; skipping it rebuilds the graveyard within a year.
Frequently asked questions
What should a segment name actually contain?
Purpose, criteria, refresh cadence, and owner. Full logic belongs in the description field.
How do we migrate hundreds of badly named segments?
Freeze new segments first, rename active ones with owner coordination, archive the rest.
Who enforces the naming convention?
A designated librarian plus creation-flow templates that make compliance the easy path.
Should we delete old test segments?
Archive with last-used dates; delete only after a year of disuse.