Wheel of Fortune feature allows you to customize the slices of the wheel. The wheel itself consists of 10 slices in total: 5 winning, 5 losing. All of these slices can be edited to your preference, although not all of them have the same setup. This article explains how to correctly define the probabilities and manage the coupon codes.
Winning slices settings
There are 5 winning slices in total, which share a 100% probability of showing up. The wheel only stops at the winning slices.
This 100% can be split up among the 5 winning slices in any way preferred as long as the total sum comes to exactly 100%.
You can go ahead and have 100, 0, 0, 0, 0 if you want only a particular slice to roll out. Also, you can go with 20, 20, 20, 20, 20 if you want to have all slices show up with the same probability. Any other combination of 5 slices that sums up to 100% works as well.
The full setup of winning slices consists of:
Label - name the slice of the wheel so it best expresses the prize underneath it. We recommend keeping it short and simple (limited up to 15 characters)
Discount code - paste your discount code for each winning slice. More on discount code settings are below.
Probability - the probability of the slice rolling out. The higher the number, the more likely it is to roll out. The total sum of 5 winning slices should be 100%.
Losing slices settings
As the wheel stops only at the winning slices, losing slices have a slightly more simple setup. For losing slices, only one Label is required, which would show up on the wheel itself. Equally, as with the winning slices, we suggest keeping it short and simple (limited up to 15 characters).
Discount codes settings
Winning slices allow you to add discount codes, which show up to the winner (all subscribers who fill in the form). These discount codes should be manually created on your store and then pasted into the setup form. Omnisend does not automatically create the discount codes provided in the Wheel of Fortune setup.
To learn more about the setup process of Wheel of Fortune, read this article.