Build
Configure the receipt-game touchpoint, the acceptance logic, and the reward model.
These articles cover what you configure inside the receipt-game touchpoint in Studio, plus the shared Platform settings that receipt challenges often depend on.
Create a receipt game
Create the touchpoint and fill the participant-facing basics.
Set opt-in for a receipt challenge
See how opt-in scope applies to receipt challenges and where to configure it.
Set the participation form for a receipt challenge
Choose whether participant data is collected at campaign level or touchpoint level.
Configure notifications for a receipt challenge
Check which notification types matter most for receipt challenges.
Acceptance policy overview
Understand which receipt checks run before a submission can count.
Configure receipt age and submission window
Control how old a receipt can be and how long users can wait before submitting it.
Configure OCR confidence threshold
Understand when low OCR confidence should trigger a stricter review posture.
Configure field requirements
Choose which extracted fields must be present before a receipt can continue.
Configure amount rules
Use minimum and maximum spend thresholds inside the acceptance policy.
Configure merchant rules
Whitelist or block specific retailers and control exact-match behavior.
Configure location rules
Use zip-code rules when a challenge is limited to a store network or area.
Validation policy: manual vs automatic
Decide whether operators review receipts or the system validates them directly.
Challenge rules overview
See how receipt-based progress conditions unlock winning options.
Create a challenge rule
Add one rule, name it clearly, and decide whether it repeats.
Challenge condition types
Understand the supported rule conditions and when to use each.
Winning options and attribution slots
Connect the challenge to rewards and optionally control time-based distribution.
Global outcome rules
Apply shared constraints such as exclusivity or unlock limits across rewards.