Displaying the Wheel of Fortune pop-up

You can configure the trigger conditions for the Wheel of Fortune from the Global Settings section.

There are 3 options to choose from:

  • based on exit intent - we use an advanced algorithm that triggers the app when the visitors intend to leave, based on their behavior in the store. On a desktop, this happens when the mouse cursor is moved fast towards the upper part of the window, outside the page viewport. In contrast, this happens if the visitor scrolls up on mobile, which leads to the toolbar showing up.
  • after several seconds - you can choose to trigger the app after an exact number of seconds
  • on scroll up - this setting will trigger the app when the user scrolls up the page

You may also choose not to show it to the visitor again for several days using the Block Days option (the default is 30 days).

You can also let the visitor choose for himself if he wants to trigger the app or not by checking the Enable Manual Trigger setting.

Furthermore, you can choose on which devices the Wheel of Fortune to be shown. It can either be just desktop, just mobile, or both.

Testing or troubleshooting:

Please keep in mind that the Wheel of Fortune is intended to only show up once for first-time visitors and, by default, it has a cool-off period (block days) of 30 days (will not show up for 30 days after the first time it shows).

If you wish to test the Wheel of Fortune while you're setting it up, please check in a new Incognito page. All incognito pages need to be closed first, and a new one has to be opened to re-trigger the Wheel (so that no cookies are saved in the browser).

You can find a quick tutorial on how to open Incognito mode below:

How to use Incognito mode

Alternatively, you can choose to delete any VITALS-related cookies from your browser to dynamically test the Wheel of Fortune app without using Incognito mode by following the tutorial below:

Resetting Vitals on your browser

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.