For the complete documentation index, see llms.txt. This page is also available as Markdown.

🎟️Raffles

Raffles provide a straightforward way to enhance player engagement through dynamic draw mechanisms. They allow for the creation of individual draws that can operate within specified time frames and include recurring options. For instance, hourly draws are designed to maintain player interest and encourage consistent daily participation.

Each draw can be customized to align with its target audience, including configurable prize settings to ensure the experience remains engaging and adaptable to various needs. This flexibility makes raffles suitable for diverse scenarios and player segments.

Raffle legend of terminology:

  • Raffle page - refers to the landing page.

  • Draw page - refers to the page displaying the draw details, accessible by selecting a specific draw.

  • Prize - represents the award that the user can potentially win.

  • Per draw - refers to the overall activity period of the draw. For recurring draws, this encompasses all draw runs.

  • Per run - refers to an individual instance of a draw run. For example, in an hourly draw setup, a new draw run occurs every hour.

Raffle Mechanic Overview

  • Players can earn raffle tickets through various channels, including marketing campaigns, automation rules, missions, mini-games, tournaments, or by purchasing them directly from the store.

  • Each ticket is linked to a specific player and automatically enters the upcoming run in every draw. For example, if you have a daily, weekly, and grand draw, a ticket given to a player would give them a chance in the next run in each of the draws (if the draw/prize settings and the ticket eligibility period allow it)

  • The more tickets a player holds, the higher their chances of winning. Every additional ticket increases the probability of winning a prize.

  • When a draw is executed, winners are determined and publicly announced. Players can be notified of their winnings through multiple communication channels, ensuring visibility and engagement.

Here's an example raffle to give you a clearer picture of what’s possible.

Raffle Period

  • Start Date: June 1

  • End Date: August 31

  • Segment of players: any player with at least one deposit, registration country - FR, not marked as "Bonus abusers"


Daily Draw

  • Execution Time: Every day at 10:00 PM

  • Eligibility: Tickets collected during the 24 hours before each draw

  • Prizes: 100 × “10 Free Spins” 10 × “50 Free Spins” 1 × €100 Cash (Major Prize)


Weekly Draw

  • Execution Time: Every Sunday at 3:00 PM

  • Eligibility: Tickets collected during the 7 days before the draw

  • Prizes: 10 × €100 Cash 1–5 × €1,000 Cash (Major Prize) Eligibility: Players have to collect at least 10 tickets to be eligible for the major prize. The major prize will only be activated if 1,000 or more tickets are collected for the draw. Additional settings: For every additional 1,000 tickets, one more major prize is added: 2,000 tickets = 2 × €1,000 3,000 tickets = 3 × €1,000 ... up to a maximum of 5 major prizes (€5,000 total)


Grand Draw (Finale)

  • Execution Time: August 31 at 5:00 PM

  • Eligibility: All tickets collected from June 1 to August 31

  • Prizes: 1 × BMW XM Eligibility: Only players who collected at least 1,000 tickets The grand prize is only unlocked if a total of 100,000 tickets are collected across the full period. 10 × iPhone 16 Pro Max Eligibility: Players with at least 100 tickets 1,000 × €100 Cash Eligibility: All players, regardless of the number of tickets collected

Creating Raffle

To set up a Raffle, navigate to Raffles in the Gamification section. Create a Raffle and follow the provided setup steps.

BO: Raffle page

Raffle Setup

  • Start by adding the raffle/section name, description, terms and conditions (T&C), and images that will be displayed on the landing page.

    • Internal name is the name you see in the Back-Office. Name is the name players see.

    • Raffle lobby image (890x193 px) and Raffle lobby image(mobile) (300x142 px) are shown on the landing page.

    • Custom section name and Custom section image are the raffle's entry in the navigation menu of the Gamification widget. Each raffle keeps its own custom section, created and updated together with the raffle.

  • Define the segmentation of participation and user visibility. You can choose to make the raffle widely available or restrict it to a specific group of users.

    • Who can participate - This segment defines the users who can acquire and accumulate tickets for the Raffle. It doesn't control participation in the Draw, and as such, if a user has already collected tickets and is later removed from the participation segment, their existing tickets will remain valid and give them a chance to win.

    • Who can see - This segment defines only the visibility of Raffle for users, and it doesn't affect their participation, as such users can acquire tickets and win in Draws even if they are not segmented to see it.

  • Raffle Segment Conditions: When building segments in the Back-Office for marketing campaigns or follow-ups, two dedicated raffle conditions are available: "Users have tickets for raffle" (to filter players holding at least a specified number of tickets) and "Users won in raffle draw" (to target winners of a specific draw).

  • The 'Active period' of the raffle, from start date to end date, can be up to the Max raffle duration, days setting in Label settings (default 180 days); ask your Success manager to change it.

  • The Visibility period is when the widget shows the raffle. It must contain the whole Active period. Draws become visible only once the Active period has started.

  • Set a cap for the number of issued tickets, both globally per raffle and per user, based on a specific recurring window. Use this feature to balance the ticket flow and ensure all users have the time and opportunity to acquire tickets before reaching the maximum tickets count.

    • Max. tickets count is the cap for the whole raffle.

    • Limit tickets per user adds Max. tickets count per user: up to 10,000 tickets per period. The period is Lifetime, or a number of days, hours or minutes, up to 30 days.

    • For a period of whole days, choose how it is counted: Time from last receiving, Calendar days (UTC) with its time zone, or Calendar days (user timezone).

  • Ticket cap visualization chooses what the widget shows about the cap: Show ticket counter or Show message when ticket cap is reached.

  • Indicative ticket cost is used for the estimates in the Summary tab. Players never pay it.

  • Custom data field holds a value you can read through the Public API, to build a custom UI.

  • On a multi-brand account, the Branding section changes the texts and images per brand. Empty fields use the values from the General and UI sections.

BO: Raffle core setup

Raffle status

A new raffle is a Draft, and players do not see it. To put a raffle live:

  1. Add at least one draw. A new draw is Inactive.

  2. Add at least one prize to the draw, and set the prize to Active.

  3. Set the Draw Scheduler Status of the draw to Active.

  4. Set the Status of the raffle to Active. Neither the Active period nor the Visibility period may have started yet.

An Active raffle can only move to Archived. Archived is final: scheduled draw runs are cancelled, tickets can no longer be given, and only the Internal name can still be changed.

On an Active raffle, the start of the Active period is fixed and Max. tickets count cannot be decreased.

To reuse a raffle, press Clone. The copy is a Draft with its own custom section, without the draws and prizes.

Draw Setup

BO: Raffle Draw page
  • Begin by adding the name, description, and images that will distinguish this draw from others and provide visibility into what players are competing for. Promo Image, Promo Image(mobile) and Draw Icon are required; Draw Background and Draw Background(mobile) are optional.

  • Define the execution date/time by setting up "When to draw". The options are Hourly, Daily, Days of week, Days of month, One time: On a specific date and time, and Few times: On specific dates and times.

    • A run must fall inside the Active period of the raffle, and two active draws of a raffle cannot have the same schedule.

    • "When to draw" cannot be changed while the draw and the raffle are both Active. Set the draw to Inactive first.

    • A One time draw can be marked as a Grand Draw.

  • Specify the ticket eligibility period (Ticket Eligibility Period) to determine which tickets qualify for participation. You can leave it open for all tickets to qualify or set a timeframe from 10 minutes to 90 days (e.g., 1 day prior to the draw execution) to narrow eligibility.

  • Define a segment of users who will be ineligible to win prizes and will be excluded from the awarding process when a raffle is drawn. (Used for testing purposes only)

  • Choose whether tickets can win multiple prizes or whether they should be removed from the draw upon winning.

  • Define the maximum number of prize wins a player can achieve per single Draw run or per lifetime (total prize for all Draws). The lifetime limit cannot be smaller than the limit per run.

  • A new draw is created Inactive. Add its prizes, then set Draw Scheduler Status to Active. A draw without an active prize cannot be activated.

  • To reuse a draw, press the clone icon in its row. Give the copy a new schedule, and switch on Clone prizes to copy its prizes too.

Upon deactivation of the Draw Scheduler, some additional settings will appear under the Status field: - Hide Draw - if enabled, it will hide the draw from the Gamification - Hide Draw History - if enabled, it will remove all history log instances from the Gamification (beware that users with unclaimed prizes won't be able to claim them afterwards)

BO: Raffle Draw setup

Draw Opt in

The Opt in configuration allows you to require a manual 'Join' for users to qualify for a Draw run. This feature is designed to give you more control over player qualification and to ensure that users are actively engaging with your platform. Enabling this setting will shift a Draw from a passive background event into an active touchpoint that requires user intent for every individual run.

Gamification: Draw Opt in for Raffle

Core Logic and Rules

The manual opt-in serves as the eligibility "gateway" for the Draw execution.

  • Eligibility Qualification: A user must press the Opt-in button for the specific Draw run to be eligible to win. Having an accumulated ticket balance is not enough to qualify for a win if the opt-in has not been performed.

  • Execution Logic: When a Draw executes, the system will only consider the pool of tickets belonging to opted-in users.

  • Reset Mechanism: Opt-in status is run-specific. Once a Draw run is executed and a new one begins, all users are reset to a "Not Joined" state. Users must opt-in again for the new run to participate.

It is important to note that this feature only changes eligibility, not the underlying ticket mechanics:

  • Ticket Accumulation: The logic for how users earn or accumulate tickets remains untouched. Users continue to gain tickets via existing platform activities.

  • Ticket Balance: Opting in does not deduct from or change a user's ticket balance. It simply marks their current tickets as "eligible" for that specific Draw run.

  • Total Tickets count: The total tickets column on the user interface reflects only the collective sum of tickets belonging to players who have already opted in for the current run.

Draw Scheduler & Draw Run - Changing Statuses

Draw functionality is divided into two main components: the scheduling mechanism and manual control over active runs. Scheduling is governed by the Draw Scheduler status, which can be set to either Active or Inactive. When marked Active, the Draw is enabled to execute automatically based on the configured timing parameters. If the status is set to Inactive, it halts any future scheduling of executions from taking place until reactivated.

Control over live Draw runs is managed via the Draw History panel. Within this interface, operators can take direct actions such as canceling an ongoing Draw or resuming one that was previously canceled. These controls allow for intervention in real-time operations without affecting the scheduling setup.

Lets go over all settings and show they affect the Draw behavior.

Changing the Draw Scheduler status:

Draw Active

  • Draw is actively scheduling Draw runs

Draw Active → Draw Inactive

  • Stops scheduling of new Draw runs.

  • The current Draw run continues and executes as usual.

Draw Inactive → Draw Active

  • If current Draw run is still ongoing: - Simply re-enables scheduling of future Draw runs.

  • If the last Draw run has finished: - Schedules a new Draw run based on current time and configuration. - Example: If action is done at 14:30 with a set hourly schedule, a run is created now at 14:30 and set for execution at 15:00.

Changing the Draw run status:

Draw Active → Cancel run

  • Cancels the current (ongoing) Draw run.

  • Waits for the previously scheduled execution time to pass, only then schedules a new Draw run.

Draw Active → Cancel run → Resume run

  • Resumes the canceled Draw run and returns it to running state.

Changing both Draw Scheduler & Draw run statuses:

Draw Active → Cancel run → Draw Inactive

  • Cancels the current Draw run.

  • Stops scheduling of new Draw runs.

Draw Inactive → Cancel run → Draw Active

  • Schedules the next available Draw run.

  • If still within the canceled run’s period, wait until its previously scheduled execution time to pass before starting a new one. - Example: At 14:30 with hourly schedule (14:00-15:00), and the canceled run was to execute at 15:00 → Wait until 15:00 and start a new Draw run, with scheduled execution for 16:00.

Draw Inactive → Cancel run → Draw Active → Resume run

  • Resumes the canceled Draw run and returns it to running state.

  • New Draw run scheduling continues as normal.

Legend of Status Names for Next Draw and Draw Run

Next Draw statuses in Draw:

  • Date of execution - shows the upcoming Draw execution date

  • Not planned - shown when currently there is no scheduled execution (Will appear when the last Draw run is executed and Draw scheduler is Inactive)

Draw run statuses in Draw History:

  • Running - shown during the gathering tickets phase

  • Drawing - shown when the draw execution has started

  • Executed - shown when the draw was successfully executed

  • Canceled - shown when the draw was deactivated abruptly before a draw execution

Prize Setup

BO: Raffle Prize page
  • Assign a prize to an already created draw.

  • Establish the prize details, including the name, image, and Position. A position can be used by one prize of a draw.

Note: In the Gamification Widget, the prizes will be ordered starting from top position (1) to lower positions (2,3...), but executions will always start from the lowest position prize towards the top one, so that the biggest prize is always given last.

  • Select the type of prize and define its base amount. Supported types of prizes are: Bonus, Gems, Diamonds, Points, Mission, Level change, Avatar item, Ticket in the Raffle, Spin attempt in the Mini-game, and Tangible item. The type cannot be changed after the prize is saved.

  • Set Initial prizes per run, the number of prizes each run starts with.

  • Set criteria for unlocking the prize at both the user and global levels (Min tickets per user and Min global tickets). This helps manage costs and ensures that prizes are awarded only once a specified ticket threshold is met.

  • Introduce additional prizes when users reach the global ticket threshold to boost interest and engagement (Add +1 prize per X tickets).

  • Define different cap criteria to ensure the number of prizes awarded stays within specified limits: Cap prizes per run is the most prizes one run can reach, and Stock items per draw is the number of prizes left for all runs of the draw.

  • Define the maximum number of times a player can win the Prize (Max wins per user). This applies across all Draw runs when a recurring draw is configured. Once a user reaches the defined limit, they will no longer be eligible to win this specific Prize in any future Draw runs.

  • Claim: You can enable the "Claim" option where players must manually claim their won prize in the Gamification widget rather than receiving it automatically upon draw completion.

    BO: Raffle Prize setup
  • Hide chance to win hides the chance that appears when the prize unlocks.

  • Indicative prize cost is used for the estimates in the Summary tab.

  • Custom data field holds a value you can read through the Public API, to build a custom UI.

  • To reuse a prize, press the clone icon in its row. The copy starts Inactive, in the draw and position you choose.

Summary

You can use the information in this section, even before the Raffle is published, to get an overview of the statistics that will help you determine whether your setup will be profitable or if you have made some mistakes in the process. You can also track the actual progress of the Raffle as users engage with it to determine whether you need to make corrections along the way to improve engagement and efficiency.

Check the criteria included in the analysis
  • Max. tickets count - The total number of tickets that can be issued for the Raffle.

  • Max. tickets value - The total value of tickets that can be given to users. Calculated by multiplying the Indicative ticket cost by the Max. tickets count.

  • Issued tickets - The number of tickets already given to users.

  • Issued tickets value - The value of all tickets that are issued to users.

  • Max. prizes cost - Calculates the total indicative costs for all set prizes, factoring in the max number of times each prize is potentially awarded per draw. For more accurate results, ensure the "Indicative Prize Cost" is provided for every prize.

  • Actual prizes cost - The value of all prizes that have already been given to users

  • Projected profit/loss - The result of Max tickets value minus Max prizes cost.

  • Actual profit/loss - The result of Issued tickets value minus Actual prizes cost.

List of all prizes that are setup in the Raffle, along with columns with the following information:

  • Prize - info such as title, type and redirection to the prize

  • Prize cost - individual prize cost

  • Max prizes - the max. number of prizes that are potentially available to be won

  • Max cost - the max. cost amount if all potential prizes are won

  • Won prizes - the current amount of won prizes

  • Won cost - the current amount of cost for the already won prizes

  • Used in Draw - defines the Draw name of which this prize is part of, along with a redirection to the draw itself

Raffle - Summary tab

Other tabs

  • Tickets lists the tickets given to players.

  • Draws History lists the runs of each draw, with their dates, participating tickets, prizes won and run status. Here you can cancel a run or resume a canceled one.

  • Win History lists the winners with their prize and ticket, and when each prize was won and claimed.

  • Used In lists the automation rules, campaigns and other places that give tickets for this raffle.

  • History lists the changes made to the raffle, its draws and its prizes.

Raffles Reporting Dashboard

For detailed draw analytics, ticket issuance channel breakdowns, player behavioral uplift, and prize claim performance, refer to the Raffles Dashboard in Reports › Gamification › Raffles.

Presentation in the Gamification widget

The Raffle has its own dedicated section within the Gamification widget, featuring a two-level navigation system. Upon opening a Raffle, you are greeted by the Raffle landing page. Selecting a Draw takes you to the Draw page, where detailed information about the prizes is displayed.

Raffle landing page

This is the Raffle welcome page, designed to provide users with a clear overview. The upper section introduces the Raffle, allowing users to understand its purpose and access the description and rules. The lower section displays all active and completed Draws, including information on the draw schedule and participating tickets. Users can click on a Draw to navigate to its dedicated page and explore the details further.

Gamification: Raffle main page

Draw page

Here, users can view the details of the Draw across three distinct phases:

Gathering Phase:

  • A countdown, indicating the time remaining to gather tickets.

  • Prizes showing their status, whether unlocked or, if not, the ticket threshold required (either personal or global) to unlock them.

  • The ticket counter functions as a progress bar, visually indicating how much progress remains to meet the required ticket threshold. Prize rows can be expanded to reveal more information.

  • If a multiplier is set on a prize, it will appear as a progress bar surrounding the prize, allowing users to track progress toward reaching the milestone.

Drawing Phase:

  • During this phase, the countdown disappears, and a draw animation becomes visible until the winners are selected.

Winners Phase:

  • After the drawing concludes, a list of winners is displayed, showing the winning user, ticket number, and the type of prize won.

  • For recurring draws, a button will become available to provide a quick link to the latest draw.

Gamification: Draw page with list of prizes

Raffle events

Five events are available to act on ticket issuance, draw results, prize claims, and player opt-ins:

  • Raffle: Tickets given — fired when tickets are successfully issued to a player

  • Raffle: Tickets issue failed — fired when ticket issuance fails (e.g., ticket cap reached or user outside participation segment)

  • Raffle: Draw Won — fired when a player wins a prize in a draw execution

  • Raffle: Prize Claimed — fired when a player explicitly claims a won prize in the gamification widget

  • Raffle: Draw Run Opt In — fired when a player opts into a specific draw run

You can use these events:

  • To communicate with players whenever they have won in a draw using real-time campaigns

  • To set automation rules to run additional activities whenever the balance is changed. E.g., whenever a player gets a ticket to run a Web Hook to report the change to the external API.

  • Build missions and badges. E.g., Mission "Collect 10 Raffle tickets."

How to give tickets

  • Manually - Through the user profile page

    BO: Give manually tickets through the Profile page
  • Rewards - setup tickets as a reward from Missions, Tournaments, Mini-games, Lootbox, Prize drop

    BO: Give tickets by awarding them through Missions
  • Store - set up a store item of the "Raffle Ticket" type to sell one or more tickets for a designated raffle

    BO: Give tickets through the Store
  • Automation - use the new activity to give raffle tickets

    BO: Give tickets through Automation rules
  • Campaigns - use the new activity to give raffle tickets

    BO: Give tickets through Campaigns

Build raffles with an AI assistant

With the MCP Server, an AI assistant such as Claude or ChatGPT can read, create and update raffles, their draws and their prizes for you, with the same checks as the Back-Office. It helps most when you build a series of raffles with many prizes.

The assistant builds a raffle in the same order as the Back-Office:

  1. The raffle, as a Draft.

  2. Each draw, as Inactive.

  3. The prizes of each draw.

  4. When you agree, the draws and then the raffle go Active.

Images must be hosted files. The assistant can upload them first, see MCP - How to manage images.

An example prompt:

Build a raffle "Summer raffle" for all players, active from 1 June to 31 August, with a limit of 100,000 tickets and 50 tickets per player per day. Add a daily draw at 22:00 UTC with 5 prizes of 500 points and 1 bonus "Weekend free spins". Show me the plan first, and keep everything as a Draft.

Raffles, draws and prizes cannot be deleted. Archive the raffle, set the draw to Inactive, or set the prize to Inactive.

FAQ

What are Indicative Ticket Cost and Indicative Prize Cost?

Indicative costs are estimated monetary values that operators assign to tickets and prizes during setup. They are used exclusively in the Back-Office Summary tab and Raffles Dashboard to calculate projected financial liability, total ticket value, and profit/loss estimates. They do not charge players or alter how tickets and prizes are awarded.

Why are raffle tickets not being credited to a player from a campaign, wheel, or rule?

Ticket issuance can fail if:

  1. The player does not belong to the raffle's "Who can participate" segment.

  2. The raffle's global maximum ticket cap or the player's personal ticket cap for the current window has been reached.

  3. The raffle is not currently in Active status or the current time is outside the raffle's start and end dates.

  4. The label enforces active account checks and the player's account status is not Active or Pending.

  5. The player is included in a gamification control group.

When a ticket grant fails, the system triggers the "Raffle: Tickets issue failed" event with the specific failure reason.

Why can't I activate a raffle or a draw?

A raffle goes Active only when it has an active draw, and when neither its Active period nor its Visibility period has started. A draw goes Active only when it has an active prize and its next run falls inside the Active period of the raffle.

What happens to accumulated tickets if a player does not opt into a draw run?

Tickets earned by a player are never deducted or lost when an opt-in draw executes. If a player does not click Join for a specific run, their tickets simply do not enter that single run's drawing pool. The tickets remain in the player's balance and can participate in future draw runs, provided the tickets fall within the draw's ticket eligibility timeframe.

Last updated

Was this helpful?