Clusters

Clusters are used to classify and filter Batches in larger configurations. Clusters are created at the Tag Group level and can then be applied to Batches either when the Batch is created or later.

Creating Clusters

Navigate to your chosen Tag Group and then Tag Group Function Panel > Clusters Tab. Enter the name for your Cluster and click on Add. Each Tag Group can have up to 25 Clusters. Clusters are not shared between other Tag Groups.

Applying Clusters

When creating Batches

Once a Cluster has been created, it will be available as an option when created a Batch via the Tag Group Function Panel > Add Batch Tab. You don't need to select a Cluster and you can change or remove the Cluster after the Batch has been created.

Within a Batch

You can set or remove a Cluster from within a Batch by navigating to Batch Data Panel > Cluster Tab.

Filtering by Cluster

On the Tag Group screen, once a Cluster has been created, an additional column will be visible on the Batches table within the Batch Panel. Additionally, a drop down allows you to filter by Cluster

Clusters Filtering

Cluster Subtags

The Cluster associated with a Tag Code (via the Batch) can be displayed dynamically within a Redirect, via the API Response or via CodeLink using the subtag - {cluster}. More information on creating dynamic links using subtags.

Using Clusters

The purpose of using Clusters is to help organise structures with larger numbers of Batches. You can use Clusters however you choose. However, if you are using Clusters to help track the release of multiple Batches of tags, there's two approaches for this :

Using Clusters as Product definitions

Consider a scenario for a Product hierarchy where you have, say 'Jeans' as an Active Folder, 'Style A' as your Tag Group and then multiple colours of Style A.

You might choose to create a separate Batch for each colour of Style A so that you can organise the Tags. You can then use Clusters to define each colour and the Batch Name to define the Batch release (assuming that you might create more than one release of tags).

In this way, you can dynamically include the colour on the API/Redirect/CodeLink.

Using Clusters as Release definitions

Alternatively, using the same scenarion as described above, you may choose to define the Batch Name as the colour and then use Clusters as - for example - the Release. So if you issue two sets of tags for a particular colour then you can use Cluster to define Release 1 and Release 2 so you can track which tags were sent out when.

Which works best ?

In the experience we have had with customers to date, we would recommend using the Cluster as the Release definition.

Cluster Groups

We are currently Beta testing with a limited number of clients Cluster Groups. Cluster Groups allows you to define up to 5 different sets of Clusters (rather than current one). In this way, you can define Batches in more granular detail such as 'size', 'leg length', etc.

We expect Cluster Groups to go to full release in May 2024.