Form
Configure a Form game where the form is the touchpoint itself, with submission summary and performance rewards.
Form is a performance touchpoint where the participant completes the form inside the game itself. Use it when the form is the main interaction, not just an extra data-capture step before another game.
A typical example is a campaign where participants submit a product preference, upload a photo, and finish the touchpoint by sending the form itself.
Form game and Participation Form are different features
Use Form when the form is the touchpoint itself. Use About participation forms when you need a shared form before or around another touchpoint.
Form game vs Participation Form
| Use this | When the form should... | Typical example |
|---|---|---|
Form game | be the touchpoint itself | survey touchpoint, preference submission, upload-based entry |
Participation Form | collect extra data around another touchpoint | gather profile details before or around a wheel, memory, or quiz |
If you are new to the shared form layer, continue with About participation forms and Set the participation form for a game.
How rewards work here
Form uses Leaderboard rewards. Create the reward in Platform, then link it to this touchpoint in Performance Rewards.
In the current product, completed form-game submissions are ranked by completion time rather than by a player-facing score. Keep one Leaderboard reward per performance game so the ranking stays clear.
Configure the game
Create the touchpoint and set the page appearance
In Build -> Touchpoints, add a new game touchpoint and choose Form.
Then configure the page frame:
- upload the
Background Image - add the
TitleandSubtitle - add a
Thumbnailif the game also appears on a landing page or in listings
Keep the page copy focused, because the form itself is the main interaction.
Build the form inside the touchpoint
If you want stronger visual framing, add a Header Image at the top of the form block.
Then build the form in Form Fields. For each field, define the label, type, placeholder where relevant, required state, and a unique field ID. Common field types include Text, Textarea, Email, Number, Tel, Select, Checkbox, Date, and Image.
If you use a Select field, give participants at least two clear options.
Write the post-submit message and optional final question
Add the message shown after the participant submits the form.
If you want one more response after the form itself, enable the optional Open-Ended Question and choose whether it accepts Text Only, Image Only, or Text and Image.
Link the reward and test the full submission flow
Add the game's reward in Performance Rewards, then submit the form once from the participant view.
Use this test to verify required fields, mobile readability, image upload behavior if you use it, and the final confirmation flow.
What players see at the end
After the participant submits the form, OmniLab can show the optional open-ended question before the summary.
The summary then shows your post-submit message. Unlike Quiz or Catcher, the default player-facing result is confirmation-style rather than score-style.
Keep the ranking fair
Because the current Form leaderboard flow ranks completed submissions by completion time, the safest setups usually:
- keep the form short enough to finish comfortably on mobile
- use only the required fields that genuinely matter
- keep field labels and IDs clear so the submissions stay readable later
- avoid making large image uploads mandatory if speed is part of the comparison
Before you publish
- the form contains at least one field
- every field has a unique ID, label, and type
- every
Selectfield has at least two options - the post-submit message is set
- the optional
Open-Ended Questionis complete if enabled - the linked reward is dedicated to this game
Related
About participation forms
See when you need a shared participation form instead of a Form game.
Leaderboard rewards
Configure the performance-based reward type used by Form.
Quiz
Compare Form with a question-based performance flow.
Set the participation form for a game
Add the shared participation layer when another touchpoint also needs extra data.