Templates / Fundamentals / Platform Fundamentals

Platform Fundamentals

Fundamentals

Core concepts, glossary, and platform overview. The foundation every partner needs.

Template Content

~2146 words, 238 lines

## Platform Overview

A high-level introduction to the Komo platform -- what it is, what it does, and how the pieces fit together.

### Komo is an Engagement Engine

Komo is a **no-code platform for creating interactive digital experiences**. Brands use it to turn passive audiences into active participants -- capturing zero-party data, driving engagement, and proving ROI across every channel.

It's not a CMS, not an event app, not a survey tool. It's the engagement layer that sits on top of (or alongside) a client's existing tech stack. One platform, one data model, one analytics dashboard -- used across every touchpoint, every event, every campaign.

### Core Capabilities

- **55+ Interactive Card Types** -- Games, polls, quizzes, trivia, surveys, spin-to-win, scratch cards, scavenger hunts, instant-win, and more -- all no-code.
- **Branded Hubs & Sites** -- Fully branded web destinations with custom themes, pages, navigation, and domain support. Campaign-specific or always-on.
- **CRM & Zero-Party Data** -- Built-in contact management with profiles enriched by engagement data -- preferences, quiz answers, form responses, and behavioral signals.
- **Competitions & Prizes** -- Prize management with instant wins, random draws, leaderboards, entry tracking, coupon distribution, and winner management.
- **Loyalty Programs** -- Points-based loyalty systems with earning rules, redemption tiers, and engagement rewards -- all tied to the same data model.
- **Workflow Automation** -- Event-driven automations triggered by form submissions, prize awards, and gameplay. Send HTTP requests, sync to CRMs, send emails and SMS.
- **Embed SDK, API & Webhooks** -- JavaScript embed SDK for web and React Native, REST API for programmatic access, and webhook events for real-time external integrations.
- **Analytics & Reporting** -- Built-in dashboards with engagement rates, data capture volumes, completion rates, time-on-site, and per-sponsor attribution.

### How It Works

The end-to-end flow from creation to results:

1. **Create a Hub** -- Set up a branded Site with custom theme, domain, pages, and navigation. Campaign-specific or always-on.
2. **Add Cards** -- Choose from 55+ interactive card types -- quizzes, polls, games, surveys, competitions -- and configure them with no code.
3. **Distribute** -- Share via direct URL, QR codes, email, social media, or embed directly into websites and apps using the SDK.
4. **Capture Data** -- Every interaction captures zero-party data -- preferences, opinions, contact details -- voluntarily provided by users in exchange for value.
5. **Automate Actions** -- Use workflows to sync data to CRMs, trigger emails and SMS, send webhook notifications, and update external systems in real time.
6. **Analyze Results** -- Review engagement metrics, data capture volumes, completion rates, and ROI attribution in the built-in analytics dashboard.

### Key Differentiators

- **No-code** -- Marketing teams can create, launch, and manage experiences without engineering resources.
- **Enterprise-scale** -- Built for high-traffic events, large audiences, and concurrent usage without performance degradation.
- **SOC 2 Type 1 certified** -- Enterprise-grade security and data handling that passes procurement reviews.
- **Web-based, no app download** -- Users engage directly in the browser. No friction, no app store, no installation. Works instantly.
- **Works on 4G/5G** -- Optimized for mobile networks. Critical for live events, stadiums, and venues where Wi-Fi is unreliable.

---

## Platform Concepts

The mental model you need before reading a single line of API docs. Understand how Komo's pieces fit together, what the terminology means, and how data flows through the system.

### Data Hierarchy

Everything in Komo lives inside a strict hierarchy. Understanding this structure is the key to knowing where data lives and how permissions work.

```
Workspace (org-level container)
├── Site / Hub (branded web destination)
│   ├── Pages (layout sections within the hub)
│   │   └── Cards (interactive content units)
│   ├── Theme & Branding (colors, logos, fonts)
│   └── URL (e.g., brand.komo.site or custom domain)
├── Contacts (user profiles built from engagement)
├── Competitions (prize pools, draws, instant wins)
└── Workflows (event-driven automations)
```

### Workspaces

A **Workspace** is the top-level organizational unit. It represents an account -- typically one per client or one per business unit. All Sites, Contacts, Competitions, and Workflows belong to a Workspace. Team members are invited at the Workspace level and can be assigned roles to control access.

### Sites (Hubs)

A **Site** -- also called a **Hub** -- is a branded web destination where engagement happens. Think of it as a microsite purpose-built for interactive content.

**What a Site has:**

- A URL (subdomain on komo.site or custom domain)
- Pages -- layout containers that hold cards
- Theme -- colors, fonts, logos, background images
- Cards -- the interactive content units
- Navigation and footer configuration

**How Sites are used:**

- Standalone engagement destinations (linked from email, social, QR codes)
- Embedded into existing websites or apps via the Embed SDK
- Event-specific microsites with sponsor branding
- Always-on loyalty or community hubs

### Cards

**Cards** are the building blocks of engagement in Komo. Each card is a self-contained interactive content unit with its own gameplay, data capture, and visual presentation. There are **55+ card types**.

**Card Type Examples:**

- **Gamification:** Trivia, Spin-to-Win, Scratch Cards, Instant Win, Memory Match
- **Data Capture:** Polls & Surveys, Quizzes, Personality Tests, Pick & Compare, Swipe Cards
- **Engagement:** Scavenger Hunts, Countdown Timers, Video Players, Content Reveals, Photo Galleries

Each card can include a **data capture form** (pre or post gameplay) that collects contact details, preferences, and custom fields. Cards can also be linked to Competitions for prize management.

### Contacts

A **Contact** is a user profile automatically built from engagement. When someone fills out a form on a card, their data is captured and stored as a Contact within the Workspace.

**What a Contact contains:**

- **Identity** -- email, name, phone, custom fields
- **Engagement history** -- which cards they interacted with, scores, answers
- **Zero-party data** -- preferences, opinions, and selections willingly given
- **Tags & segments** -- applied manually, by workflows, or by card configuration
- **Competition entries** -- prize draws they're eligible for, prizes won

This is **zero-party data** -- data users voluntarily provide in exchange for the value of the experience. No cookies, no tracking pixels, no third-party inference.

### Competitions

**Competitions** manage everything related to prizes and winning. They're a separate entity from Cards -- a card can be linked to a Competition, but the prize logic lives independently.

**Competition features:**

- Prize pool definition (multiple prizes, quantities)
- Draw logic (random, leaderboard, first-come)
- Instant win configuration
- Scheduled draws with automated winner selection
- Leaderboard tracking with point systems

**Coupon distribution:**

- Upload coupon pools (CSV of unique codes)
- Auto-distribute on win or form submission
- Track redemption status
- Limit per-user distribution

### Workflows

**Workflows** are event-driven automation flows. They follow a **Trigger -> Action** pattern: when something happens in Komo, the workflow executes a sequence of actions.

**Triggers (events):**

- Gameplay.DataCaptured
- Gameplay.Ended
- Prize.Won
- Form.Submitted
- Contact.Created
- Receipt validation events

**Actions:**

- HTTP Request (call any API)
- Send Email / SMS
- Update Contact properties
- Salesforce Get/Update/Create
- Mailchimp Upsert/Tag
- Braze Track User

Workflows also support **conditional logic** (Decision nodes), **delays** (Wait nodes), and **data mapping** to transform payloads between steps.

### Embedding

Komo content doesn't have to live on komo.site. The **Embed SDK** lets you place cards or full hubs into any website or mobile app.

**Embedding capabilities:**

- **Full Hub embed** -- render the entire Site as an iframe in your page
- **Card Cover embed** -- show a card's promotional image/button that opens the card modal
- **Card Trigger embed** -- attach card-open behavior to any HTML element
- **SSO via JWT** -- pass auth tokens so users don't re-authenticate
- **Form prefilling** -- pre-populate form fields from your existing user data
- **Event listening** -- receive events (gameplay, form, prize) in your parent page
- **Extension data** -- pass custom key-value data that flows through to webhooks/workflows

### How Data Flows

This is the core loop. Every Komo deployment follows this same pattern -- only the specifics of the cards, data fields, and downstream systems change.

```
User visits Hub -> Engages with Card -> Data Captured
(web / embed)     (trivia, poll,        (form fields,
                   spin-to-win...)       answers, scores)
                                              |
                                              v
                                      Contact Enriched
                                      (profile updated,
                                       tags applied)
                                              |
                                              v
                                    Workflow Triggered
                                    (automation fires)
                                              |
                              +---------------+----------+
                              v               v          v
                         HTTP Request    CRM Updated   Email
                         (your API)     (Salesforce,   Sent
                                        Mailchimp,
                              v          Braze)
                        Webhook Event
                        (real-time POST
                         to your endpoint)
```

- **Engagement Layer** -- Cards capture attention and data. Users interact willingly because the experience is fun, rewarding, or interesting.
- **Data Layer** -- Contacts, form entries, gameplay results, and competition entries are all stored and queryable within Komo.
- **Integration Layer** -- Workflows, webhooks, and the API push data outward to the systems that need it -- CRMs, CDPs, analytics, and custom backends.

---

## 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.

Changes here will propagate to all partner hubs using this template. Switch to Preview to see how it renders.

What is Komo

Partner Usage

Using template (3)

Fan 360 x Komo auto-updates

Eventbase auto-updates

WMT Sports auto-updates

Customised (0)

No partner overrides

Editing impacts 3 hubs

Changes to this template will be reflected in all partner hubs that haven't customised this section. Partners with their own version (0) will not be affected.