Getting around the Kitetags Platform

Learn about the main components of the Kitetags platform.

Kitetag Groups

All Kitetags in a group share the same Kitetag Data Structure (KDS) and Kitetag Interation (KI). This is a useful way to organize Kitetags by teams, locations, projects, or other purposes.
Any Kitetag that is moved into a group will inherit the group's selected KDS and KI.
To function, a group must have a KDS and KI selected. If not, then the Test Flight app will be the default KI.
When expanded, you can see the individual Kitetags and their data. Here is where you can make direct changes to any data of any Kiteag. Changes take effect immediately.
Data for all the Kitetags in a group can be exported as a CSV and imported with changes. This makes it easy for you to manipulate and change data with an external application such as a spreadsheet program.

Data structures describe the name and data type for the fields that are available for Kitetags in a group. It is not the actual data, but similar to the header row of a spreadsheet that provides the name of the data field. Continuing with that analogy, each row below the header would be the actual data for each Kitetag.
A KDS can be used by one or more groups.
Data types are specified to ensure that data is properly formatted for your business requirements. Examples include text, integer, URL, email, etc.

Kiteag Interactions describe what happens after a Kitetag is tapped.
A KI is linked to a KDS which can be used by many groups.
When building a KI, the chosen app will have its own Kitetag Interaction Builder tool. You can setup the post-tap iteraction and how to merge the Kitetags data.