Kitetags terms and definitions

Term Definition
Account Manager A user role with full administrative access to a Kitetags account. Account Managers invite and remove team members, manage billing, and have all the same content-management powers as a Tag Manager. Every account has exactly one Account Manager. Compare with Tag Manager and Limited Account Manager.
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. Inside the Interaction Builder, these same behaviors are available as step types.
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.
Chip Model The type of NFC chip embedded in a Kitetag. Supported models include ST25TV, ST25TVxxxC (ST25TV512C/ST25TV02KC with on-chip tap counters), and NTAG21x (NTAG213/215/216). The chip model is selected when uploading CSVs and determines how the platform parses tap-counter data. See CSV import / export.
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.
Design tab The second tab in the Interaction Builder, where you set the colors, fonts, and logo used by every display step in the interaction. Design choices are saved per interaction, so different brands can have different looks.
Display Information Table step A step type that shows the Tapper a two-column table of label/value rows — useful for part numbers, calibration data, event details, or anything else pulled from the tag’s KDS. Supports template placeholders in every row.
Display step Any step in a step-based interaction that renders UI the Tapper sees and interacts with — Message, Form Input, vCard, WiFi Share, Display Information Table. Contrast with silent and terminal steps.
Final Message step A Message step placed at the end of a step-based interaction to thank or confirm the Tapper. Set Button Text to empty to end the flow on that screen.
Form Input step A step type that presents a form to the Tapper and captures the response. Field types include Text Input, Email, Phone, Dropdown, Radio Buttons, and Checkbox. Responses are passed to subsequent steps (for example, a Webhook that logs them).
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 drag-and-drop editor in the Kitetags dashboard where you create and configure Kitetag Interactions. The builder supports step-based flows (multiple chained steps) and the Design tab for brand customization. See the Interaction Builder guide.
Interface The visual layout or screen that a Tapper sees after tapping a Kitetag. The Interface is generated by the App or step 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. An interaction can be a single action (URL redirect, vCard, etc.) or a step-based flow. You build interactions with the Interaction Builder. See the interactions guide.
Kitetag Tapped (Step 0) A fixed first step shown at the top of the step list in the Interaction Builder. Step 0 represents the tap event itself — you cannot edit or delete it. Your configurable steps are numbered 1, 2, 3… after it.
Limited Account Manager A user role with the same content powers as the Account Manager, but without the ability to delete team members. Used when an organization wants to share admin-level access without full destructive privileges.
Message step A display step with a title, message body, and optional Continue button. Used for welcome screens at the start of a flow or confirmation screens at the end (see Final Message step). Supports KDS template placeholders like {{ callsign }}.
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.
NTAG21x A family of NFC chips (NTAG213, NTAG215, NTAG216) made by NXP. NTAG21x chips use a 24-bit hex tap counter format. Select NTAG21x in the CSV uploader when uploading tags made with these chips.
Progress dots The row of dots shown at the top of a step-based tap page, indicating how many visible (non-silent) steps the Tapper will pass through. Silent steps like Webhook and Zapier are not counted.
Silent step A step type that runs in the background without UI — Webhook and Zapier. After the action completes, the flow auto-advances to the next step. Silent steps are not counted in the progress dots.
Step 0 See Kitetag Tapped.
Step-based interaction A Kitetag Interaction that chains multiple steps into a single flow. Built in the Interaction Builder. Supports display steps (Message, Form Input, vCard, WiFi Share, Display Information Table), silent steps (Webhook, Zapier), and a terminal URL Redirect.
Tag Manager A user role with day-to-day content powers: create and edit Kitetag Groups, KDS, and Interactions; manage tag data. Tag Managers cannot manage billing, invite team members, or delete the organization. Compare with Account Manager.
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.
Tap flow The sequence of screens and actions a Tapper experiences after tapping a Kitetag — applies to step-based interactions. See also: progress dots, display step, silent step, terminal step.
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.
Terminal step A step that ends the flow. URL Redirect is the built-in terminal step — when added, the Interaction Builder pins it to the end of the step list and inserts any new step before it. A Message step with no button is also effectively terminal (the Tapper has nowhere to advance).
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.
vCard step A display step that shows the Tapper a contact card with a Save & Continue button (or Continue when download is disabled). Email and phone values are rendered as tappable mailto:/tel: links. Compare with the single-action vCard App.
WiFi Share step A display step that shares WiFi credentials via a branded QR code screen. The Tapper scans the QR or downloads the image; most phones recognize the embedded credentials and offer to join the network.

Next steps

Last updated 17 Apr 2026, 15:38 +0900 . history