On this page
menu_book
Kitetags Glossary: NFC and Platform Terms Defined
Definitions for every Kitetags term including Kitetag Groups, KDS, KI, Callsign, Tapper, NFC, and more. A quick reference for the Kitetags platform.
**TL;DR:** This page defines every term you will encounter in the Kitetags platform and documentation. Use it as a quick reference when you need a refresher.
Kitetags terms and definitions
| Term | Definition |
|---|---|
| App | The engine that produces the response a Tapper sees after tapping a Kitetag. Built-in Apps include URL Redirect, vCard, Webhooks, and Zapier. Each App takes tag data and turns it into an action. See the Apps overview. |
| Automatic Message Data | Data that the Kitetags platform collects and attaches to each tap automatically, such as the timestamp and device information. You do not need to configure this — it is included by default. |
| Built-in Data | Data fields that every Kitetag has by default, such as UID and Callsign. These fields exist on every tag regardless of the Kitetag Data Structure assigned to its group. |
| Bundle | A pack of Kitetags purchased together. Bundles come in various sizes and can be assigned to your account for claiming and configuration. |
| Callsign | The human-readable identifier for a Kitetag, such as “kite-8247”. The Callsign makes it easy to find and reference a specific tag without using its full UID. You can find the Callsign printed on the tag or shown in the dashboard. |
| Claiming a Kitetag | The process of linking an unclaimed Kitetag to your account. You claim a tag by tapping it with your phone for the first time. Once claimed, the tag appears in your dashboard and can be configured. See the quickstart guide. |
| Custom Data | Data fields that you define through a Kitetag Data Structure (KDS). Custom Data lets you store information specific to your use case, such as a product name, employee ID, or target URL. |
| Frozen Kitetag | A Kitetag that has been permanently deactivated. Frozen tags cannot be tapped, configured, or reactivated. Freezing is irreversible. Use it when a tag is lost, stolen, or no longer needed. |
| Grounded Kitetag | A Kitetag that has been temporarily disabled. Grounded tags do not respond when tapped, but they can be reactivated at any time from the dashboard. Grounding a tag removes it from your active tag count. |
| Interaction Builder | The visual editor in the Kitetags dashboard where you create and configure Kitetag Interactions (KI). The Interaction Builder lets you define what happens when a tag is tapped without writing any code. See the interactions guide. |
| Interface | The visual layout or screen that a Tapper sees after tapping a Kitetag. The Interface is generated by the App assigned to the tag’s group. |
| Kitetag | A pre-encoded NFC tag made by Tagstand that connects to the Kitetags cloud platform. Each Kitetag has a unique UID and Callsign. When tapped by a smartphone, it triggers the configured App response. See What is Kitetags?. |
| Kitetag Data Structure (KDS) | A template that defines the data fields for all tags in a Kitetag Group. Think of a KDS as a form — it specifies what information each tag holds (such as name, URL, or phone number), while each tag has its own values. See the data structures guide. |
| Kitetag Group | A container for one or more Kitetags that share the same KDS and KI. Every Kitetag belongs to exactly one group. When you change a group’s settings, all tags in that group update instantly. See the Kitetag Groups guide. |
| Kitetag Interaction (KI) | The configuration that defines what happens when a Kitetag is tapped. A KI connects a tag’s data to an App and controls the response. You create KIs using the Interaction Builder. See the interactions guide. |
| Kitetag Manager | A person who manages Kitetags through the platform dashboard. Kitetag Managers create groups, define data structures, build interactions, and monitor tag activity. |
| Near Field Communication (NFC) | A short-range wireless technology that lets two devices exchange data when they are within a few centimeters of each other. Kitetags use NFC to communicate with smartphones. See How NFC works. |
| Tap | The action of holding a smartphone close to a Kitetag so the phone reads the tag via NFC. A tap triggers the Kitetag Interaction assigned to the tag’s group. |
| Tapper | A person who taps a Kitetag with their smartphone. Tappers do not need a Kitetags account or any installed app — their phone handles the NFC read natively. |
| Test Flight | A built-in App and group that verifies a Kitetag is working correctly. When you tap a tag in the Test Flight group, you see its UID and Callsign. New tags start in Test Flight by default. |
| UID | The unique hardware identifier assigned to a Kitetag at the factory. The UID cannot be changed and is used by the platform to identify each tag. It is different from the Callsign, which is a human-readable name. |
| Unclaimed Kitetag | A Kitetag that has not yet been linked to any account. Tapping an unclaimed Kitetag starts the account creation or sign-in flow to claim it. See the quickstart guide. |
Next steps
- Follow the quickstart guide to see these concepts in action
- Read What is Kitetags? for a full platform overview
- Explore the platform guide to learn how Groups, KDS, and KI work together
Last updated 27 Mar 2026, 06:51 +0900 .