Extended Data
Last updated
Last updated
Copyright TabDesk Ltd 2024
For each Tag Code you have the option of creating up to five additional text or date data fields. These are called the Extended Data fields.
Extended Data fields can store tag specific data, such as 'Colour' or 'Size' which can be used to identify Tag Codes throughout the platform in stats and the Console. They can also be included in Redirect URLs, API Responses and the Direct Response page using Dynamic Response.
The Extended Data fields are created at the Folder level. Data for those fields can then be entered at the Tag Group or the Tag Code level.
If no data is entered at the Tag Code level, then the Tag Code will automatically inherit data for that Extended Data field from the Tag Group level. Entering data into an Extended Data field at the Tag Code level will override the default Tag Group level data.
Extended Data fields are created at the Active Folder level and are available to all Tag Groups, Batches and Tag Codes within that Folder.
Navigate to an Active Folder, then Folder Function Panel > Data Tab.
The first item is the 'Tag Name' which is a Core Data field not an Extended Data field. This cannot be removed.
To add the first Extended Data field, enter the name of the field (which can be edited later), select either a Text or Date data type and click 'Add'. Up to five of these Extended Data fields can be added.
To remove an Extended Data field, navigate to the Active Folder level and then Folder Function Panel > Data Tab. Then click the 'x' button next to the Data field to be deleted.
Deleting an Extended Data field will permanently delete all associated data at both the Tag Group and Tag levels.
Once the Extended Data field has been created, data can be associated with that field at both the Tag Group and Tag Code levels.
Any data entered for an Extended Data field at the Tag Group level will automatically be inherited by any Tag Codes under that Tag Group. However, entering data for that Extended Data field at a Tag Code level will break the inherited link.
Navigate to a Tag Group within the Active Folder where you have just set up your Extended Data fields. Then Tag Group Data Panel > Extended Tab.
This will list all the Extended Data fields that you have created at the Active Folder level.
Enter a value into the appropriate Extended Data field and click Update.
Navigate to a Tag Code within the Active Folder where you have just set up your Extended Data fields. Then Tag Data Panel > Extended Tab.
If you have set data for this Extended Data field at the Tag Group level, you will see 'inherited' next to the field name. To change the data for this Tag Code only, you can enter new data and click 'Update'.
If you want to revert back to the Tag Group 'default' data, then simply delete all data and click 'Update'.
One of the core functions of using Extended Data is that Tag Codes inherit any data for that field set at the Tag Group level. The data isn't set, it's just inherited (unless you set it specifically for a Tag Code).
This means that if you move a Tag Code to another Tag Group - in the Console or via Locus - then it will automatically inherit the Extended Data from the new Tag Group.
For example, you may have created an Extended Data field called 'Location'. Assume one Tag Group has default data for this field as 'Warehouse A' and another Tag Group in the same Active Folder has data for this for field as 'Warehouse B'. Moving a Tag Code from the first Tag Group to the second will change the Extended Data field for this Tag Code from Warehouse A to Warehouse B.
Extended Data can be viewed at any time through the Console.
However, the real benefit is being able to add the Extended Data fields directly into the Responses using Dynamic Response.
In the example above, we moved a Tag Code from 'Warehouse A' to 'Warehouse B'. This information can then be dynamically included in URL link on the Response Mode, on a response page on Direct Response or even in the API with the API Response Mode.
The Tag Codes therefore have changing responses based on their location with your configuration. Moving a Tag Code automatically changes the Response.
