Key concepts glossary

Look up the core OmniLab terms used across campaigns, organisations, touchpoints, rewards, and deployment.

Look up any OmniLab term you meet for the first time and get a short, self-contained explanation before you go 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 augmented-reality experiences, this is often a model file (a GLB or USDZ file) that OmniLab uses to power richer visuals in OmniLab 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 OmniLab 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. Touchpoint Level means each touchpoint is configured separately, with no fallback 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 usually signs in with a one-time code sent by email rather than through your company login.

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.

Dynamic fields (personalised content)

Dynamic fields let a message insert details that change for each recipient — such as their name, the reward they won, or a booking time. You mostly use them in notification emails and other personalised 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 OmniLab 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 step shown to a participant before or during participation. It combines the consent text and the terms content. You can turn it off, set it once for the whole campaign, or set it per touchpoint.

Organisation

An organisation is the workspace boundary that scopes users, campaigns, templates, and shared settings. What you can see or change in OmniLab Studio depends on which organisation you are allowed to access and which organisation you are currently viewing.

One-time code (OTP)

A one-time code (sometimes shown as OTP) is a temporary code sent to a verified user by email to start a session. OmniLab uses it as a sign-in method for some users.

OmniLab Pages

OmniLab Pages is the consumer-facing layer where participants open landing pages, start touchpoints, submit forms, accept terms, and receive outcomes. OmniLab 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. You can turn it off, set it once for the whole campaign, or set it per touchpoint.

Receipt game

A receipt game is a OmniLab 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. It usually answers whether something is off, set for the whole campaign, set per touchpoint, or limited to one or more organisations.

Single sign-on (SSO)

Single sign-on (SSO) lets your team sign in with your company account instead of a separate OmniLab password. Your IT team connects OmniLab to your company's login system. See Integrations.

Sign-in labels

Some setups show different labels for users who sign in with your company account. 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 OmniLab Smart Link URL. It should stay unique, readable, and stable enough to be shared or printed.

A OmniLab Smart Link is a dynamic, trackable URL that redirects users to a destination while collecting analytics. OmniLab Smart Links are often paired with QR codes and are designed for cross-channel distribution.

OmniLab Studio

OmniLab 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 OmniLab 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, OmniLab 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.

Leaderboard reward

A Leaderboard reward (created as a Performance Based Reward) rewards the top participants by score or ranking. Use it for skill-based games 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.

A OmniLab 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 Lottery, Instant Win, First Come, First Serve, or a Performance Based Reward (Leaderboard). The winning method shapes the participant journey, the reward logic, and the related notifications.

Was this helpful?

Optional comments help us improve this page for future authors and readers.

On this page