Roulette
Use Roulette to add a gamified spinner for discounts, prizes, or interactive offers.
Content settings
| Setting | What it controls |
|---|---|
| Items | Prize, discount, or option list. |
| Result behavior | What happens after the spin completes. |
| Button or trigger | Text and action used to start the spin. |
| Tracking | Events or scripts attached to spin actions when available. |
Style settings
| Style area | What you can adjust |
|---|---|
| Wheel | Segment colors, text, pointer, size, and spacing. |
| Button | Text color, background, border, radius, and hover state. |
| Animation | Spin behavior and motion settings when available. |
| Responsive layout | Wheel size and spacing on mobile. |
Best practices
- Disclose rules or eligibility when required.
- Test touch behavior on mobile.
- Avoid using fake prizes or misleading scarcity.
FAQ
When should I use this page?
Use this page when you need a quick reference for this Atomicat feature and want to understand what it changes before editing or publishing. It is especially useful while reviewing a page, funnel, quiz, lead flow, product setup, video configuration, or account setting. For Roulette, keep a short checklist of the fields you changed and test the result in the same browser session.
Do I need to configure this before publishing?
Configure it before publishing whenever the feature affects visitor behavior, tracking, SEO, forms, embeds, checkout, or access. If the feature only changes internal organization, review it before launch so your team can manage the campaign consistently. For Roulette, keep a short checklist of the fields you changed and test the result in the same browser session.
Can this affect live pages?
Yes, some settings can affect live pages after saving or publishing. Always preview the page, test the main action, and confirm desktop and mobile behavior before sending paid traffic or sharing the URL. For Roulette, keep a short checklist of the fields you changed and test the result in the same browser session.
What should I check if something looks wrong?
Check the page status, project access, saved revisions, browser cache, connected domain, and any related integrations. If the feature depends on a plan, permission, or enabled module, confirm that your workspace has access. For Roulette, keep a short checklist of the fields you changed and test the result in the same browser session.