Coupons & redemption (Simple vs. Secure mode)
Choose the right redemption mode, prepare coupons, and understand what winners see.
In this article, you'll choose how winners receive their reward, decide whether the flow needs coupons, and understand the difference between Simple Mode and Secure Mode.
Before you begin
- The reward already exists.
- You know whether the reward needs a unique code or coupon.
- If you plan to use
Secure Mode, you are ready to prepare or upload the coupon pool.
Configure redemption
Open Redemption Settings
Open the reward in Build -> Rewards, then go to Redemption Settings.
Write the Redemption Confirmation Message
Add the warning or follow-up message winners should see when they need to claim the reward before it expires.
Choose the Redemption Display Mode
Select either Simple Mode or Secure Mode depending on the participant experience you need.
If needed, prepare the coupons
When the reward uses Secure Mode, open Manage Coupons and prepare the coupon set you want winners to receive.
Save and test the winner flow
Run a controlled test so you can confirm what the participant sees after winning.
Compare the two modes
Use Simple Mode when the winner only needs the success message and does not need a unique code.
This mode is best when the reward is:
- informational
- handled manually on site
- badge-like or achievement-like rather than coupon-driven
The participant sees the winner message without coupon code handling.
Use Secure Mode when the reward should reveal a unique code protected by the secure winner flow.
This mode is best when the reward is:
- a voucher or coupon
- a gift card or code-based prize
- any reward that must be tracked at redemption time
Use Manage Coupons to upload or prepare the coupon pool in advance. OmniLab can work with generated codes, but the smoothest experience usually comes from preparing the coupon stock before winners start claiming.
Coupon summary
When a reward uses Secure Mode, OmniLab gives you a coupon management view with the key counts:
AvailableIssuedRedeemed
This makes it easier to track whether the reward still has enough codes prepared for the expected winner volume.
What validation tells you
| Validation message | Meaning | Fix |
|---|---|---|
Reward '{{reward_name}}' has no redemption expiration message | Winners would not see the claim warning or expiry guidance. | Add the redemption confirmation message. |
Reward '{{reward_name}}' uses Simple Mode - winners will see only the success message without codes | The reward is configured without unique code redemption. | Keep it if that experience is intentional, or switch to Secure Mode. |
Reward '{{reward_name}}' uses Secure Mode - winners will receive a unique code with lock screen protection | The reward is configured for code-based redemption. | Prepare coupons in advance if the reward should use a controlled code pool. |
Reward '{{reward_name}}' has {{coupon_count}} prepared coupons but quantity is {{reward_quantity}}. | The secure reward may not have enough prepared codes. | Add or upload enough coupons in Manage Coupons. |
Related
Create a reward
Start here if the reward itself still needs to be created.
About rewards and reward types
Revisit how redemption fits into the broader reward model.
Notification types reference
Review the Winner and Reward Redeemed notifications that often accompany claim flows.
Configure notifications globally
Send the right follow-up messages once the redemption flow is in place.