Wheel of Fortune
Configure a Wheel of Fortune game with segment design, winning options, and scheduled or probability-based outcomes.
Placeholders in this article
This article contains placeholder screenshots. Search for placehold.co in this file and replace them before publishing.
Use Wheel of Fortune when you want a familiar spin interaction, multiple winning slices, and a clearly visible losing outcome on the same wheel.
Before you begin
- Open an existing campaign in Studio. If you still need the campaign shell, start with Your first campaign.
- Prepare the shared touchpoint assets: a
Background Imageat1536 x 2048 pxand, if you plan to reuse the game in listings, aThumbnailat800 x 800 px. - Prepare the wheel-specific visuals: square artwork for segment images, a dedicated
Pointer Image, and an optionalBorder & Center Image. - Decide which rewards belong to each winning slice before you open
Outcomes. That makes it much faster to link rewards and test probabilities.
Configure the game
1. Create the touchpoint
In Build -> Touchpoints, add a new game touchpoint and choose Wheel of Fortune.
Give the touchpoint a clear internal name before you continue. That same name appears in validation messages and makes troubleshooting easier later.
2. Set the page appearance
Open the Appearance tab and fill in the player-facing header:
- Upload the
Background Image. - Add the
TitleandSubtitle. - Add a
Thumbnailif this touchpoint will be reused in carousels or campaign listings. - Turn on
Hide Wheel in Intro Screenif you want the first screen to focus on the headline before the wheel appears.
The wheel itself is configured separately, so use this tab for the page frame and the intro screen copy.
3. Build the wheel design
Open Custom Wheel Configuration and configure the wheel itself.
- Choose the
Number of Segments. The current builder offers4,6,8,10, or12. - Add each winning slice as a
Winning Optionwith a name, color,Number of Segments, and optional segment image. - Keep one losing outcome named exactly
Losing Option. The current product validates that name literally. - Upload the
Pointer Image, then add an optionalBorder & Center Imageif you want a more branded wheel. - If you turn on gaps between segments, also define the gap color and gap size.
The number of slices assigned to each option controls how many visible segments point to the same outcome. A simple six-segment wheel can be mapped like this:
4. Configure the outcomes
Open Outcomes to decide how winners are resolved.
Random Chancelets every play use probability weights. Make sure the total across winning and losing options equals100.Scheduled Rewardslets you define when rewards become available. UseSimplefor one continuous date range, orAdvancedfor attribution slots inside each winning option.- Each winning option needs a
Winning Option Messageand a linked reward. - The losing outcome needs its own
Losing Message.
In the current Wheel of Fortune UI, the available modes are Random Chance and Scheduled Rewards. If you need a delayed draw instead of an immediate result, use a game type that exposes Lottery, such as Simple / Instant Win or 3D Selection game.
For advanced reward timing, link the reward first, then configure the attribution slots that appear inside the winning option. Use the canonical reward docs for the mechanics behind Instant Win, Attribution slots, and reward linking.
5. Review the shared tabs and test
After Appearance and Outcomes, review the shared luck-based tabs as needed: Terms & Conditions, Restrictions, Dates, Gamification, and Advanced.
Use Dates to control when the touchpoint itself is playable. In Scheduled Rewards, the outcome dates only control winning moments, not whether the page is open.
Save the touchpoint, publish or preview the campaign, and test a few plays from Pages before launch. For a quick first-pass validation, try one winning slice, one losing slice, and a visible pointer before you polish the artwork.
What players see
Players land on a branded page with the touchpoint title, subtitle, and wheel. When the intro screen is enabled, the wheel can stay hidden until they tap the main CTA.
When play starts, Pages shows the instruction Tap the wheel to spin and reveal your reward. After the wheel stops, OmniLab displays the message and reward linked to the selected option.
Common validation issues
| Validation message | Meaning | Fix |
|---|---|---|
Wheel must have at least 2 segments (current: {{segment_count}}) | The wheel cannot run with only one slice. | Open Custom Wheel Configuration and add more segments to the wheel. |
Wheel must have at least one winning option | Every wheel needs at least one slice that can award a reward. | Mark at least one option as a winning option. |
Losing option {{option_index}} must be named 'Losing Option' (current: '{{actual_name}}') | The losing slice name does not match the required convention. | Rename the losing outcome to 'Losing Option'. |
Option '{{option_id}}' repeat count mismatch: expected {{expected_count}}, found {{actual_count}} segments | The number of slices does not match the value configured on the option. | Make sure the number of slices assigned to that option matches the option setup in Custom Wheel Configuration. |
Pointer image is missing | The wheel design was saved without the asset that indicates the final slice. | Upload the pointer image in Custom Wheel Configuration and save the wheel again. |
If the wheel still does not validate, reopen Custom Wheel Configuration and save it again. That step also regenerates the wheel asset used by Pages.
What to try next
Your first game in 15 minutes
See a full Wheel of Fortune setup flow from campaign creation to first publish.
Instant Win rewards
Use the canonical reward guide when wheel outcomes should resolve immediately.
Attribution slots
Plan advanced scheduled availability for each winning reward.
Link rewards to touchpoints
Review the shared reward-linking flow used across OmniLab touchpoints.