Create a receipt game
Add a receipt challenge to your campaign and write the words shoppers see when they upload a receipt.
Set up the receipt challenge shoppers interact with, then write the on-screen copy that invites them to upload a receipt. This covers creating the Touchpoint and filling its Appearance fields before you move on to rules, rewards, and validation.
A receipt challenge is a Touchpoint
You create a receipt challenge from your campaign's Touchpoint picker, not from a separate homepage.
Assets you'll need
A receipt game uses a banner, a thumbnail for listings, and reward icons.
Banner Image
OptionalThe header image for an activity, offer, receipt challenge, or treasure hunt.
- Optional
- Size900 × 600 px
- Aspect ratio3:2
- FormatsJPEG / WEBP / PNG
Thumbnail Image
OptionalThe square tile shown in carousels and campaign listings — not on the play screen.
- Optional
- Size800 × 800 px
- Aspect ratio1:1
- FormatsJPEG / WEBP / PNG
Reward Icon
OptionalThe icon that represents a reward.
- Optional
- Size800 × 800 px
- Aspect ratio1:1
- FormatsJPEG / WEBP / PNG
Circular design and a transparent background work best.
For every image spec in one place, see Image & asset specs.
Create the Touchpoint
Open the Touchpoint picker
Go to Build, then Touchpoints, and click Add New Touchpoint.
Choose Receipt Game
In the Create a new touchpoint window, select Receipt Game and confirm.
OmniLab adds the Touchpoint to your campaign and opens its tabs right away.
Fill in Appearance first
The first useful fields live in the Appearance tab. Write the shopper-facing copy first, so every later test runs against realistic content.
What the Appearance tab controls
| Field | What shoppers see | Notes |
|---|---|---|
| Header Image | The main visual at the top of the receipt challenge. | Use it to anchor the promotion or store. |
| Title | The main call to action. | Keep it outcome-driven, for example "Upload your receipt to unlock your gift". |
| Subtitle | Supporting context under the title. | A good place to remind shoppers of the spend target or which stores count. |
| Details | Longer explanation. | Use it to explain how the challenge works, not for legal terms. |
| Host Validation Message | The message shown when staff check the receipt. | Most useful with manual review or an on-site activation. |
| Thumbnail | The smaller visual used in campaign-level views. | Keep it consistent with the header image. |
| Submission Message | The copy around the upload and submit step. | Use it to set expectations before the shopper takes a photo. |
The tabs to plan next
After Appearance, most teams continue in this order:
- Configuration for winning options, rules, the acceptance checks, and the validation mode.
- Terms & Conditions when the Touchpoint needs its own legal copy.
- Dates and Advanced when the challenge should not fully inherit the campaign defaults.
A simple first draft
For a first publishable version, keep the copy short:
- a title that tells the shopper to upload a receipt
- a subtitle that states the reward or spend target
- one short details block explaining the steps
- host-validation copy only if staff really step in
That is usually enough to test the live experience before you polish the campaign.
Related
Your first receipt challenge
Follow the full first-run setup from touchpoint to test submission.
Acceptance policy overview
See how receipt checks work once the touchpoint exists.
Winning options and attribution slots
Link the touchpoint to rewards and time-based allocation.
Set opt-in for a receipt challenge
Continue with the shared consent setup when the campaign needs it.