The customer activation platform.Every interaction becomes a qualified contact. Book a demo

About rewards and reward types

Learn how rewards work in OmniLab, choose the right reward type, and see when to use a global reward.

In this article, you'll learn what a reward is in OmniLab, when to use a reward linked to one touchpoint, and when a global reward is the better fit for a multi-touchpoint campaign.

What a reward is

A reward defines what participants can win, see, or redeem. You configure rewards in Build -> Rewards.

Typical reward configuration includes:

  • a title, subtitle, and icon
  • a quantity
  • participant-facing messages
  • redemption settings when the reward needs a code or claim flow

Unlike Gamification badges, rewards are about prize value, eligibility, or redemption rather than progression alone.

Why global rewards exist

Global rewards are useful when one reward should react to activity across several touchpoints instead of being owned by a single touchpoint.

Typical campaign examples include:

  • enter a grand-prize lottery after a participant attends all workshops
  • give a goodie as soon as a participant joins any workshop
  • unlock a voucher after a participant completes 3 sponsor-booth visits

This is what makes multi-touchpoint campaign dynamics possible. You can combine a broader campaign goal with smaller rewards along the way.

One touchpoint or several?

SetupUse it whenExample
Global rewardSeveral touchpoints should contribute to the same rule.Attend all workshops to enter a grand-prize lottery.
Reward linked to one touchpointOne touchpoint should award the reward directly.A Wheel of Fortune gives an instant coupon.

The four reward types

Reward typeWhat it doesBest forTypical touchpoints
Instant WinDecides the result immediately during participation.Instant-win moments and chance-based play.Wheel of Fortune, Scratch Card, Reveal Card, Simple Instant Win, 3D Selection Game
LotteryMarks participants as eligible first, then resolves winners later.Campaign-end lotteries and delayed prize resolution.Lottery-mode Simple Instant Win or 3D Selection Game flows
LeaderboardAwards the best-performing participants.Score-based or ranking-based competition.Memory, Quiz, Form, Catcher
First Come, First ServeAwards the first eligible claims until quantity is exhausted.Immediate claim logic and limited availability.Offer

In Build -> Rewards, choose this in Winner Selection Method. The key difference for operators is the participant outcome: immediate win, delayed draw, leaderboard ranking, or first-claim allocation.

Rules that matter before you publish

Keep these rules in mind before you build the detailed configuration:

  • Every reward needs a clear title. Icon, subtitle, quantity, and winner message are also common validation checkpoints.
  • Unlimited quantity is only available for qualifying luck-based game rewards.
  • A reward linked to one touchpoint must be linked in that touchpoint before participants can earn it.
  • A global reward must have its Reward Trigger configured before the campaign can evaluate it.
  • Use one Leaderboard reward per performance game when you want a clear, unambiguous ranking outcome.
  • Keep Offer rewards dedicated to the Offer that should distribute them.
  • Time-based reward distribution needs exclusive, deliberate scheduling. If one reward is shared across several games, the setup must stay compatible.

Messages attached to a reward

Rewards are not only about the prize itself. They also control what participants read:

  • Winner message: the success state shown when the reward is won
  • Eligible message: used for lottery-style rewards where the participant qualifies before the draw is run
  • Non-winner message: used on reward flows that need an explicit losing state
  • Redemption warning message: used when winners need a claim or coupon-based follow-up

The selected reward type determines which of these messages matter most, so choose the reward type first and write the participant copy second.

Was this helpful?

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

On this page