Naming templates

Naming templates are the center of Taggie. A template turns the structure you already maintain into the name HighLevel receives.

The simplest useful rule is:

{group} - {parts}

Literal text and punctuation stay literal. Tokens are replaced with values from the tag’s place in the workspace.

Template tokens

Token	Uses
{folder}	The folder value used by the tag’s structure
{group}	The tag group name
{category}	The category name
{parts}	The tag’s parts, joined with the configured parts separator
{cat_num}	The category’s order number
{tag_num}	The tag’s order number

Use only these tokens. Everything outside braces is treated as the text between values.

The parts separator is separate

The template controls the overall shape of a name. The parts separator controls how a multi-part tag fills {parts}.

Keeping those two choices separate lets one rule describe a name such as a group followed by several tag parts without confusing the separator inside the parts with the punctuation around the group.

The live preview is the quickest way to confirm both choices together.

Inheritance

Templates resolve through three levels:

1. Workspace — the default for the whole taxonomy.
2. Group — an optional override for one tag group.
3. Category — an optional override for one category.

Each level inherits until it has its own rule. Removing an override returns that level to the rule above it.

This keeps the ordinary convention in one place while allowing a genuine exception to stay explicit.

Ordinals make order part of the name

{cat_num} and {tag_num} are different from descriptive tokens: their values change when items move.

If either token is present, reordering is also a rename operation. Taggie includes those changes in the preview before they reach HighLevel.

Validation and preview

The editor updates a sample name as you type. Check that preview for the exact separators, literal text and inherited values you expect.

When an existing rule changes, the apply step reports:

• how many tags receive a different computed name;
• the before and after names; and
• any names that would collide.

Resolve collisions before applying the rule. A preview is information, not permission for Taggie to pick a winner.

Templates also drive import

During import, Taggie reads the same template in reverse. The pattern tells the wizard which pieces of an existing HighLevel name belong to the group, category and tag parts.

Patterns are explicit and ordered. Taggie does not guess separators. See Importing tags for match counts, multiple patterns and the unmatched bucket.