Your first receipt challenge
Create, test, and validate a first receipt challenge from an existing campaign.
Placeholders in this article
This article contains placeholder screenshots. Search for placehold.co in this file and replace them before publishing.
This walkthrough takes you from an existing campaign to a working receipt challenge. You will create one Receipt Game touchpoint, link one Receipt Game Reward, configure one simple spend rule, and test both the participant and operator sides.
Estimated time: 20 minutes
Prerequisites
- You can open an existing campaign in Studio.
- The campaign dates already make sense for testing.
- You have one reward idea ready, such as a tote bag, coupon, or gift card.
- You have one real sample receipt available for testing.
Main task
Create the receipt touchpoint
Open the campaign, go to Build -> Touchpoints, then click Add New Touchpoint.
In the touchpoint picker, choose Receipt Game. OmniLab adds the touchpoint to the campaign and opens its configuration.
Fill the participant-facing basics
In Appearance, fill the fields that participants will notice first:
Header ImageTitleSubtitleDetailsSubmission Message
If you expect on-site review, also fill Host Validation Message so the QR-based handoff makes sense to the participant.
Create one reward for this receipt game
Go to Build -> Rewards, add a new reward, and choose Receipt Game Reward.
Keep the first version simple:
- clear participant-facing reward title
- one icon or visual
- a realistic quantity
- winner copy that matches the receipt challenge
Save the reward, then return to the receipt game.
Add one winning option and one rule
Open Configuration.
In Winning Options, click Add Winning Option, then set:
- a
Display Name - a
Total Quantity - the
Associated Reward
Next, in Rules, click Add Rule and create one basic threshold rule. In the current UI, the available rule condition is Total Amount, so a simple first target is a threshold such as 20.00.
Turn on the minimum receipt checks
Still in Configuration, go to Receipt Acceptance Policy and enable the fields you need for the first test.
For a basic spend challenge, a good starter setup is:
AmountrequiredMerchantrequiredMin Amountset to the same threshold as your rule
Then choose a Validation Mode:
Automaticif eligible receipts should count immediatelyManualif a host or staff member should review them first
Test the participant flow in Preview
While the campaign is still a draft, use Preview and open the receipt challenge on a phone.
Tap the upload button, then follow the product guidance: the image should be clear, sharp, centered on the receipt, with the merchant and amount visible.
In automatic mode, a valid receipt can count immediately. In manual mode, the participant sees a pending state and the host-validation handoff.
If you chose manual mode, validate one receipt as an operator
Open the operator side and go to Liste des Sessions, then open the session you just created.
In Validation de Session, open the receipt and use:
Validerto approve itRefuserto reject itModifierif the merchant or amount needs a correction before re-evaluating policy
What good looks like
A healthy first setup behaves like this:
- the participant can upload a real receipt without confusion
- the accepted receipt moves to
VALIDimmediately or toPENDINGfor manual review - the rule is clearly linked to one winning option
- the winning option is linked to a
Receipt Game Reward - the operator can find the session and understand the submission status without guesswork
Go further
Create a receipt game
Go deeper on touchpoint creation and the appearance fields.
Acceptance policy overview
See how receipt checks map to statuses like valid, rejected, incomplete, and duplicate.
Validation policy: manual vs automatic
Choose the right review posture before launch.
Test the receipt flow
Run a cleaner pre-launch checklist once the basic setup works.