When building Blueprints, understanding tag relationships is crucial to using data effectively. There are two main parts to understanding tag relationships: tag hierarchy and connected tags. Tag hierarchy guides Blueprints on which set of tags to prioritize when different tag types share the same name, and connected tags define how a tag's contents are organized and filtered.

In Fluency, there are four tag types:

When used in a Blueprint, account tags take precedence over Blueprint tags, which, in turn, take precedence over shared tags, and so on. In cases of tags with identical names but different types, the Blueprint prioritizes the tag with the higher-priority tag type.

Example: Consider having an account tag and a Blueprint tag both named [inventory]. Each is connected to different data. If used in a Blueprint, the tag [inventory] will fetch content from the account tag, not the Blueprint tag.

Within a tag group, you can have multiple tags. Click the + icon next to a tag group name to reveal its tags. For instance, an inventory tag group might include tags like make, model, and condition, resulting in tags like [inventory.make], [inventory.model], and [inventory.condition].

Tags in the same group are "connected," meaning they share the same data source. Tags are more likely to work well together when they're from the same tag group, rather than mixing tags from different tag groups.

For example, a tag named [PrimaryMake] isn't in the "inventory" tag group, so it draws from a different data source. This means that using [PrimaryMake][inventory.model] together might not create the right connection (e.g., Honda Crosstrek). In these cases, using a data filter is necessary to achieve the desired output. On the other hand, using [inventory.make][inventory.model] in a Blueprint field connects the make with the correct model (e.g., Subaru Crosstrek) because they belong to the same tag group.