TagSets (Professional)
TagSets are the structured foundation of the J2 Tag Manager workflow. They define the managed tags used throughout the system and provide the prefix and hierarchy rules that make large tag collections easier to organize.
TagSets are part of J2 Tag Manager Professional.
What a TagSet Is
A TagSet is a dedicated Data Asset that stores a structured collection of managed tags.
It acts as the organizational source for TagSet Tags and provides the rules and defaults that those tags inherit. Instead of defining tags ad hoc directly on actors or components, TagSets allow projects to maintain a more controlled and maintainable tagging structure.
This becomes increasingly important as the number of tags grows and multiple systems begin to rely on consistent naming and usage.
What a TagSet Does
A TagSet defines a collection of managed tags. These tags can then be created, edited, and maintained through the plugin’s editor tools.
Because each TagSet provides its own structure and defaults, it becomes much easier to keep naming and usage consistent across a larger project.
Without TagSets, teams often end up with manually created tags that slowly drift apart in naming and intent.
Working with TagSets
In most cases, TagSets are primarily managed through the Tag Manager panel.
This is the main place where TagSets are edited as complete systems. It allows you to create, organize, and maintain the tags that belong to a TagSet and is intended to be the primary workflow for structured tag management.
Viewing the TagSet Asset
A TagSet can also be opened directly as a Data Asset. This provides a useful overview of the TagSet and its current configuration.
When viewing the TagSet asset directly, you can inspect:
all tags contained in the TagSet
the TagSet description
the default usage
the display name
This makes the asset useful as a direct reference when reviewing the structure of a TagSet.
Read-Only TagSet Structure
Some parts of a TagSet are visible on the asset but are not intended to be edited there.
This includes:
the Tag Prefix
the Parent TagSet
These values can be inspected directly on the asset, but they are not edited from that view.
This helps keep the asset useful for reference without turning it into the main editing workflow.
Prefixes
Every TagSet defines a prefix. This prefix becomes the first part of the tag path for all tags inside that set.
For example, a TagSet with the prefix J2 might contain tags such as:
This creates a clear namespace and helps separate systems from one another.
Parent TagSets
A TagSet can also have a parent TagSet. In that case, the final path can effectively include multiple prefix levels.
This allows projects to build broader hierarchies and maintain consistent naming conventions across related systems.
Parent TagSets are especially useful when a project wants to organize tags at multiple levels without giving up the clarity of local TagSet ownership.
Shared Defaults
A TagSet can define shared defaults for its contained tags. One of the most important examples is Usage, which determines whether tags are available for actors, components, or both.
Individual tags can override that behavior when necessary, but the TagSet still provides a useful default configuration.
This helps reduce repetitive setup and keeps related tags consistent by default.
TagSet Properties
A TagSet can provide several important properties that define how it behaves in the editor.
Description
The Description provides additional context about the purpose of the TagSet. This is useful when projects contain multiple TagSets and users need a quick explanation of what each set is meant for.
Display Name
The Display Name allows the TagSet to appear with a more user-friendly label in the editor UI.
Default Usage
The Default Usage defines whether the tags inside the TagSet are intended for:
Actor Tags
Component Tags
Both
This value acts as the shared default for all contained tags unless a specific tag overrides it individually.
Behavior Assets on TagSets
TagSets can also reference Behavior Assets.
This allows a TagSet to define automation at a higher organizational level instead of attaching behavior only to individual tags. Multiple Behavior Assets can be assigned to the same TagSet, which makes it possible to combine several automation rules within a single structured tag collection.
Behavior assignments on TagSets can also participate in the broader inheritance workflow of the Behavior System.
Why TagSets Matter
The value of TagSets becomes much clearer as the project grows.
They help with:
consistent naming
scalable organization
better discoverability
cleaner workflows
more maintainable editor tooling
A small prototype may work fine with Quick Tags alone, but a larger production workflow usually benefits from the structure provided by TagSets.
TagSets and Production Workflows
Quick Tags are useful for speed. TagSets are useful for discipline and long-term maintainability.
That is the main design difference between the two systems. TagSets are intended for the tags that should become part of the project’s stable and organized tagging language.