Key concepts glossary
Look up the core OmniLab terms used across campaigns, organisations, touchpoints, rewards, and deployment.
This glossary defines the shared terms that appear across OmniLab. Use it when you encounter a product word for the first time and want a short, self-contained explanation before going deeper.
How to use this page
Definitions are alphabetical and link to the closest related article or section whenever a deeper page already exists in the docs.
A-C
Acquisition form
An Acquisition form is the campaign-level form used when OmniLab needs to turn a participant into a subscribed or identified contact. It is configured once for the whole campaign rather than separately per touchpoint, because subscription and consent collection should stay consistent across the experience.
Asset (3D model: GLB, USDZ)
An asset is a reusable media file used by a campaign experience. In 3D and AR contexts, this often means a model file such as GLB or USDZ, which OmniLab uses to power richer visual experiences in Pages.
Attribution slot
An Attribution slot is a reward distribution rule that controls when and how an instant-win reward becomes available. It belongs to reward logic, not to the touchpoint itself.
Badge (gamification)
A badge is a gamification item awarded when a participant completes or unlocks something in a campaign. Badges help represent progression and can also support other reward or collection mechanics.
Campaign
A campaign is the top-level container in Studio. It holds the shared settings, dates, touchpoints, rewards, forms, notifications, deployment choices, and analytics that make up one activation.
Campaign level / Touchpoint level
These two labels describe where a setting applies. Campaign Level means one configuration is reused across the whole campaign, while Touchpoint Level means each touchpoint must be configured separately without falling back to the campaign version.
Check-in (Self, Scan)
Check-in is the step that records an attendee's arrival for an event or activity. In event flows, self check-in is participant-led, while scan check-in is handled by staff or a host flow.
Coupon
A coupon is a code linked to a reward, especially in secure redemption flows. OmniLab can use generated codes or uploaded third-party coupon pools depending on how the reward is configured.
D-L
Digital Agency (user profile)
A digital agency user is an external operator who creates or manages campaigns for assigned organisations. This profile typically signs in with an email-based OTP rather than SSO.
First Come First Served
First Come First Served is a winning method where rewards are claimed in the order participants become eligible, until quantity is exhausted. It is commonly used for offer-style rewards that should stop once stock runs out.
Global organisation / Organisation
A Global organisation and other organisations structure access, shared settings, and local campaign ownership. The Global organisation is used for shared governance, while other organisations are used for local work.
Landing page
A landing page is the campaign-level entry page shown before participants open touchpoints. It can introduce the experience, explain what to do next, and route users into the right part of the campaign.
Liquid template
A Liquid template is a text template that inserts dynamic campaign, participant, reward, or touchpoint data into content. You usually encounter it in notifications and other personalized messaging.
Lottery / Draw at End
Draw at End is a lottery-style winning method. Participants first become eligible, and winners are selected later rather than immediately at the moment of participation.
O-S
Offer / Offer Pass
An Offer Pass is the touchpoint participants open when a campaign groups one or more offers inside a single experience. An offer is one of the items managed inside that Offer Pass.
Online game
An online game is a consumer-facing game touchpoint in Pages, such as a wheel, scratch card, memory game, quiz, or catcher-style experience. Online games are often used to acquire audiences, capture signals, and distribute rewards.
Opt-in
Opt-in is the consent layer shown to the participant before or during participation. In OmniLab, it combines the consent text and the terms content, and it can be disabled, campaign-level, or touchpoint-level.
Organisation
An organisation is the workspace boundary that scopes users, campaigns, templates, and shared settings. What you can see or change in Studio depends on which organisation you are allowed to access and which organisation you are currently viewing.
OTP
OTP stands for one-time password. In OmniLab, it refers to an email-based authentication flow where a verified user receives a temporary code to start a session.
Pages
Pages is the consumer-facing layer where participants open landing pages, start touchpoints, submit forms, accept terms, and receive outcomes. Pages can run on a dedicated subdomain or inside an embedded experience.
Participation form
A Participation form is the form used to collect participant data during participation. It follows the three-state pattern, so it can be disabled, configured once at campaign level, or configured separately for each touchpoint.
Receipt game
A receipt game is a Transactions experience where a participant submits proof of purchase and OmniLab checks reward or eligibility rules against the receipt. It connects spending behavior to rewards, data capture, and follow-up.
Reward
A reward is the incentive a participant can win, become eligible for, or redeem. Rewards are created once at campaign level and then linked to the touchpoints that should distribute them.
Scope
Scope is the rule that decides where a setting applies. In OmniLab, it usually answers whether something is off, campaign-wide, touchpoint-specific, or limited to one or more organisations.
SSO
SSO stands for single sign-on. In OmniLab, it means authentication is delegated to an external identity provider, typically through an OIDC-compatible setup for staff users.
SSO user label
Some setups use different labels for SSO-backed user profiles. Follow the labels shown in your own workspace rather than assuming one universal OmniLab name.
Slug
A slug is the human-readable identifier used in a campaign or Smart Link URL. It should stay unique, readable, and stable enough to be shared or printed.
Smart Link
A Smart Link is a dynamic, trackable URL that redirects users to a destination while collecting analytics. Smart Links are often paired with QR codes and are designed for cross-channel distribution.
Studio
Studio is the back-office interface where teams create, configure, validate, publish, and analyze campaigns.
T-W
Template (ZIP)
A template (ZIP) is a portable campaign template file used to reuse or move campaign structure between organisations or environments. You can export a campaign as a template file, import it, and then generate a new campaign from it.
Touchpoint
A touchpoint is the interactive element participants open in Pages, such as a game, offer, activity, or another supported experience unit. Touchpoints are the main building blocks you add to a campaign.
Touchpoint families
When you add a touchpoint, Studio can show different campaign experiences such as games, activities, treasure hunts, Offer Pass, or receipt flows. Some of those touchpoints also include child items managed inside the parent experience. See About touchpoints in a campaign.
TOP_X
TOP_X is a performance-based winning method that rewards the top participants according to score or ranking. It is used for skill-based mechanics rather than instant-win or lottery-style flows.
Validation code
A validation code is a code OmniLab checks to restrict or unlock participation in specific flows, such as gated access, voucher-style entry, or controlled distribution. Validation codes are usually managed as reusable pools rather than typed directly into each touchpoint.
Variant (Smart Link)
A Smart Link variant is a named alternative used to distinguish placements, channels, locations, or media formats while keeping one destination strategy. Variants make reporting clearer because each scan or click can be tied back to its source placement.
Variables (organisation-level)
Organisation-level variables are shared values stored once and reused across campaigns, templates, or add-on settings. They become especially important when a campaign is recreated in another organisation or environment.
Winning method
A winning method is the rule that decides how a reward is distributed, such as First Come First Served, Real-Time Draw, Draw at End, or TOP_X. The winning method shapes the participant journey, the reward logic, and the related notification flow.