A tag naming scheme for GoHighLevel that survives three years
Tag sprawl is the single most common reason a GoHighLevel account becomes unusable. Four categories, one format, and a migration that doesn't break your workflows.
6 min read
Why tags rot
Tags rot because every person who touches the account invents one. Someone types podium, someone else Podium 2024, a workflow adds podium-lead. Six months later a filter returns a third of the people it should, and nobody notices until a campaign underperforms for reasons that have nothing to do with the campaign.
The fix is not discipline. It is a format narrow enough that there is only one obvious way to write any given tag.
The four categories
Every tag belongs to exactly one of four categories, written as a prefix. If a tag doesn't fit one, it probably shouldn't be a tag — it should be a custom field or a pipeline stage.
- 01project: — which piece of work or property this person relates to. project:podium
- 02source: — where they came from. source:meta, source:referral, source:walk-in
- 03stage: — a coarse lifecycle marker, not your pipeline. stage:enquiry, stage:qualified, stage:client
- 04status: — operational flags. status:dnc, status:bounced, status:hold
The format rules
Three rules, no exceptions, and the scheme holds:
- 01Lowercase only. Tag matching is inconsistent enough without case variants.
- 02Hyphens between words, colon after the category. Never spaces.
- 03No dates inside tags. A date belongs in a field you can sort and filter by range.
Migrating without breaking workflows
The dangerous part is not renaming — it's renaming while workflows are still filtering on the old name. Do it in this order and nothing breaks.
- 01Export the full tag list and group every existing tag under one of the four categories.
- 02For each group, pick the canonical name. Write the mapping down before touching anything.
- 03Add the canonical tag to every contact holding a variant. Do not remove anything yet.
- 04Update every workflow, smart list and campaign filter to use the canonical tag.
- 05Run for a week. Watch the counts on both tags — they should track together.
- 06Only then remove the variants.
Keeping it clean
Restrict tag creation to the smallest group of people you can. Review the tag list monthly — if a new tag appeared that isn't in the scheme, either fold it in or delete it that week, while its meaning is still known.
If you inherit an account with hundreds of tags, don't try to fix it by hand. The mapping is the deliverable; the applying is mechanical and should be automated with a preview and an undo.