Kitetag Data Structures (KDS): Define Your Tag Data
Learn how Kitetag Data Structures define the fields your NFC tags carry. Choose a preset or build a custom structure with text, date, email, and more.
What is a Kitetag Data Structure?
A Kitetag Data Structure (KDS) is a template that defines the data fields for every tag in a Kitetag Group. Think of the KDS as the column headers in a spreadsheet. Each Kitetag in the group is a row with its own values.
For example, a “Contact Info” KDS might have fields for name, email, and phone number. Every tag in the group would carry those same fields, but each tag would hold a different person’s contact details.
How groups, data structures, and interactions connect
A Kitetag Group ties everything together. It references one KDS (what data the tags hold) and one Kitetag Interaction (KI) (what happens when a tag is tapped). Multiple groups can share the same KDS.
graph LR
A[Kitetag Group] -->|uses| B[KDS - Data Structure]
A -->|uses| C[KI - Interaction]
C -->|reads fields from| B
B -->|shared by| D[Other Groups]
The KDS defines the data. The KI reads that data and passes it to an App. The group holds the tags that carry the actual values.
How to choose a KDS preset
The platform includes presets to help you get started quickly:
| Preset | Included fields | Best for |
|---|---|---|
| Contact Info | Name, email, phone, company, title | Digital business cards, employee directories |
| Product Info | Product name, SKU, description, price | Product tags, inventory lookup |
| Location Info | Location name, address, latitude, longitude | Venue tags, asset tracking |
| Custom | No preset fields — you define everything | Any use case not covered by a preset |
To apply a preset, select it when creating a new KDS. You can add, remove, or rename fields after applying a preset.
Supported data types
Each field in a KDS has a data type that controls what values tags can hold:
| Data type | Description | Example value |
|---|---|---|
| Text | Any string of characters | “Jane Smith” |
| Integer | Whole numbers only | 42 |
| Decimal | Numbers with decimal points | 19.99 |
| Percent | A percentage value | 75 |
| Date | A calendar date | 2026-03-27 |
| A valid email address | jane@example.com | |
| Phone | A phone number | +1-555-0123 |
| Website | A valid URL | https://example.com |
Choosing the correct data type matters. The platform validates values on entry and during CSV import. If a value does not match the field’s data type, the platform will reject it.
How to mark a field as required
When creating or editing a KDS, check the Required checkbox next to any field that must have a value. Required fields cannot be left blank when entering tag data or importing from CSV.
Use required fields for data that your interaction depends on — for example, a URL field for a redirect App.
How to create a custom data structure
- Navigate to Data Structures in the dashboard.
- Click Create Data Structure.
- Choose the Custom preset (or start from another preset and modify it).
- Add fields by clicking Add Field. For each field, enter a name, choose a data type, and decide if it is required.
- Click Save.
You can now assign this KDS to one or more Kitetag Groups.
How a KDS can be shared across groups
A single KDS can be used by multiple groups. This is useful when different groups need the same data fields but different interactions. For example, you might have two groups — “Sales Team” and “Engineering Team” — both using a Contact Info KDS, but with different tap behaviors.
Editing a shared KDS updates the structure for all groups that use it. Be careful when removing fields from a KDS that is used by multiple groups.
Next steps
- Set up what happens on each tap in the interactions guide
- Organize your tags with Kitetag Groups
- Bulk-update tag data using CSV import and export
Last updated 27 Mar 2026, 06:51 +0900 .