Build
Set up your receipt game: the upload Touchpoint, the checks that accept a receipt, and the rewards it unlocks.
1 min read
Build a receipt game that lets shoppers upload proof of purchase to unlock rewards. These guides walk you through the Touchpoint in OmniLab Studio and the shared Platform settings your challenge often relies on.
BuildCreate a receipt gameCreate the touchpoint and fill the participant-facing basics.BuildSet opt-in for a receipt gameSee how opt-in scope applies to receipt games and where to configure it.BuildSet the participation form for a receipt gameChoose whether participant data is collected at campaign level or touchpoint level.BuildConfigure notifications for a receipt gameCheck which notification types matter most for receipt games.BuildAcceptance policy overviewUnderstand which receipt checks run before a submission can count.BuildConfigure field requirementsChoose which extracted fields must be present before a receipt can continue.BuildConfigure amount rulesUse minimum and maximum spend thresholds inside the acceptance policy.BuildConfigure merchant rulesWhitelist or block specific retailers and control exact-match behavior.BuildConfigure location rulesUse zip-code rules when a challenge is limited to a store network or area.BuildValidation policy: manual vs automaticDecide whether operators review receipts or the system validates them directly.BuildChallenge rules overviewSee how receipt-based progress conditions unlock winning options.BuildCreate a challenge ruleAdd one rule, name it clearly, and decide whether it repeats.BuildChallenge condition typesUnderstand the supported rule conditions and when to use each.BuildWinning options and attribution slotsConnect the challenge to rewards and optionally control time-based distribution.BuildGlobal outcome rulesApply shared constraints such as exclusivity or unlock limits across rewards.