Glossary
Komo-specific terms you'll encounter across the platform, documentation, and client conversations.
Workspace
The top-level organizational unit in Komo. A Workspace contains Sites, Contacts, and shared settings (team members, integrations, billing). Think of it as the account container — everything a client does lives within their Workspace.
Site (Hub)
A branded web destination for engagement experiences. Each Site has its own URL, pages, cards, and theme. A Workspace can contain multiple Sites — for example, one per campaign, one per event, or one always-on hub. Also referred to as an Engagement Hub.
Card
An individual interactive content unit. Examples include trivia games, polls, quizzes, spin-to-win, surveys, scratch cards, and instant-win games. Cards live within Sites. Komo offers 55+ card types, each configurable without code.
Contact
A user profile built from engagement data. Contacts are created when users submit forms or interact with cards. Each Contact contains zero-party data, engagement history, tags, and custom properties. Contacts live at the Workspace level and are shared across all Sites.
Competition
The prize management system within Komo. Competitions include draw logic (random draws, instant wins), leaderboards, entry tracking, coupon distribution, and winner management. Competitions are associated with Cards and can span multiple cards or an entire Site.
Workflow
An automated flow triggered by events within Komo. Workflows use triggers (form submission, prize award, gameplay events) and actions (HTTP requests, CRM updates, emails, SMS). They're the primary mechanism for integrating Komo with external systems.
Zero-Party Data
Data that users voluntarily provide through engagement — preferences, quiz answers, poll votes, form responses, and survey results. Distinct from first-party behavioral data (page views, clicks). Zero-party data is the core value proposition of Komo: users give it willingly in exchange for interactive experiences.
Engagement Hub
A Komo Site configured as an always-on or campaign-specific destination for interactive content. The term emphasizes the Site's role as a central engagement touchpoint — where audiences go to interact, play, and share data. Functionally identical to a Site, but framed in terms of the use case.
Card Cover
An image or image-plus-button preview of a Card displayed on the Site. When a user clicks the Card Cover, the full card experience opens in a modal overlay. Card Covers are how cards are presented in a grid or list layout on Hub pages.
Card Trigger
Any HTML element configured to open a Card experience when clicked. Used with the Embed SDK to launch specific cards from buttons, links, images, or any interactive element on an external website or app. Triggers allow card experiences to be opened without displaying the full Hub.
Embed SDK
A JavaScript library for embedding Komo cards or entire Hubs into external websites or apps. Available for web (browser) and mobile (React Native). The SDK handles rendering, authentication, event communication, and responsive sizing.
User Interaction Events
Frontend events pushed to tag managers (Google Tag Manager, Adobe Launch) when users interact with cards. Used for analytics tracking, conversion measurement, and retargeting audiences based on engagement behavior.
Webhook Events
Server-side events pushed to configured URLs when actions occur in Komo. Webhook events fire for prizes awarded, forms submitted, coupons claimed, and other significant actions. They're the real-time integration mechanism for connecting Komo to external systems.
Extension Data
Custom key-value data attached to user interaction events for advanced tracking. Extension data is passed from the host page or app into Komo via the Embed SDK, allowing partners to enrich events with context like user IDs, session tokens, campaign identifiers, or attribution parameters.
Tracked Data
Additional behavioral data attached to events for analytics purposes. Tracked data captures contextual information about how users interact with cards — timing, completion status, answers given, scores achieved — and is available in analytics exports and webhook payloads.
Scoping
The level at which a Workflow or configuration applies. Workflows can be scoped to a Workspace (fires for all Sites), a Site (fires for all Cards in that Site), or an individual Card (fires only for that Card). Scoping determines the breadth of automation behavior.