> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fanfare.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Configure Draw (Lottery)

> Set up random selection draws for fair allocation of limited products

# Configure Draw Experience

Draw experiences (also called lotteries) use random selection to fairly allocate limited products. All eligible consumers enter during an entry window, and winners are randomly selected at a specified time. This is ideal when you want to give everyone an equal chance regardless of when they enter.

## When to Use Draws

Draws are best for:

* **Fair allocation** - Equal chance for all participants
* **High-demand launches** - When demand far exceeds supply
* **Giveaways** - Free product distributions
* **Exclusive access** - VIP opportunities for loyal customers
* **Avoiding queues** - No advantage to being first

## Creating a Draw Experience

1. Navigate to **Experiences > Create Experience**
2. Select **Draw** from the experience type options
3. Complete the draw configuration form

*Caption: The draw creation form with all configuration options*

## Draw-Specific Settings

### Entry Period Tips

Configure when consumers can enter the draw:

*Caption: Set when consumers can enter the draw*

| Field         | API field  | Required | Description                        |
| ------------- | ---------- | -------- | ---------------------------------- |
| **Open At**   | `openAt`   | No       | When consumers can start entering. |
| **Close At**  | `closeAt`  | No       | When entries stop.                 |
| **Draw At**   | `drawAt`   | Yes      | When winners are selected.         |
| **Time Zone** | `timeZone` | Yes      | Time zone for scheduled fields.    |

<Tip>
  Allow at least 24-48 hours between entry close and draw time to build anticipation and give latecomers a chance to hear about the draw.
</Tip>

### Draw Configuration

*Caption: Configure how winners are selected*

| Field                        | API field                         | Required | Description                                                                                                |
| ---------------------------- | --------------------------------- | -------- | ---------------------------------------------------------------------------------------------------------- |
| **Winner Count**             | `winnerCount`                     | Yes      | How many winners to select.                                                                                |
| **Entry Capacity**           | `capacity`                        | No       | Maximum draw entries.                                                                                      |
| **Admission Window**         | `admissionExpirationSeconds`      | No       | How long selected winners have to continue.                                                                |
| **Continue Selecting**       | `continueSelectingUntilCompleted` | No       | Continue replacement selection until the configured winner count completes, when supported for the launch. |
| **Loyalty-Biased Selection** | `loyaltyBiasEnabled`              | No       | Optionally gives loyal or engaged entrants improved opportunity. Off by default.                           |

Winner selection is separate from product allocation. Draw configuration decides which eligible consumers are selected as winners; product allocation decides what product a selected consumer receives.

### Loyalty-Biased Selection

Use loyalty-biased selection when loyalty or engagement should influence opportunity for a specific draw experience. This setting is optional and off by default.

When enabled:

* Selection remains non-guaranteed.
* Customer copy should not promise a fixed chance or guaranteed outcome.
* Promotion terms should be reviewed for legal and fairness requirements before launch.

### Product Allocation

For consumer-selected products, winners choose from the available products or variants configured for the experience. For system-assigned products, configure product allocation weights so Fanfare can assign from the product pool; higher weights make a product more likely to be assigned relative to the other products in that pool.

## Winner Handling

### Selection Process

When the draw time arrives:

1. Entries close according to the configured timing.
2. Winners are selected according to the configured `winnerCount`.
3. Selected consumers see the appropriate next step in their journey state.
4. Non-selected consumers see outcome messaging.

*Caption: View draw results after selection*

## Notifications

### Entrant Notifications

| Event               | Notification                 |
| ------------------- | ---------------------------- |
| **Entry Confirmed** | You're entered in the draw   |
| **Entry Reminder**  | Draw happening soon          |
| **You Won**         | Congratulations + next steps |
| **You Didn't Win**  | Better luck next time        |

### Non-Winner Options

Configure what non-winners see:

| Option               | Description                          |
| -------------------- | ------------------------------------ |
| **Waitlist**         | Option to join waitlist for forfeits |
| **Related Products** | Show similar available products      |
| **Next Draw**        | Info about upcoming draws            |

## Draw Timing

```
upcoming → active → ended
              ↓
            killed
```

Draw visibility and entry actions are derived from the distribution timing state:

| State        | Description                                             |
| ------------ | ------------------------------------------------------- |
| **upcoming** | The draw is scheduled but entries have not opened       |
| **active**   | Entries are open                                        |
| **ended**    | Entries have closed and winner confirmation can proceed |
| **killed**   | The draw was manually stopped                           |

## Example: Product Launch Draw

### Scenario

* Product: Limited edition sneakers
* Inventory: 200 pairs
* Expected entries: 10,000+

### Configuration

```yaml theme={null}
Name: "Jordan Retro Launch Draw"
Product: Jordan Retro 2024
Audience: Loyalty Members

Entry Period:
  Open At: Monday 9 AM
  Close At: Wednesday 9 PM
  Draw At: Thursday 12 PM

Draw Settings:
  Winner Count: 200
  Entry Capacity: 10000
  Continue Selecting: Enabled

Per-Winner:
  Purchase Required: Yes
  Admission Window: 48 hours

Notifications:
  - Entry confirmed
  - Draw reminder (1 hour before)
  - Win/loss results
  - Confirmation reminders
```

*Caption: A fully configured product launch draw*

## Best Practices

### Entry Period

1. **Give adequate time** - At least 48 hours for entry
2. **Promote early** - Announce before entries open
3. **Clear deadlines** - Make entry close time obvious
4. **Multiple reminders** - Send reminders before close

### Fair Selection

1. **Choose the right selection mode** - Use standard random selection when every entrant should have the same opportunity, and loyalty-biased selection only when loyalty should be part of the promotion
2. **Document your terms** - Be transparent about eligibility and customer-facing rules
3. **Exclude duplicates** - Verify one entry per person
4. **Audit trail** - Keep records of selection process

### Winner Management

1. **Reasonable confirmation window** - 24-48 hours minimum
2. **Clear next steps** - Explain what winners need to do
3. **Multiple contact attempts** - Don't forfeit too quickly
4. **Backup winner process** - Have alternates ready

### Common Configurations

| Use Case       | Winners | Entry Period | Admission Window |
| -------------- | ------- | ------------ | ---------------- |
| Small giveaway | 10      | 1 week       | 48 hours         |
| Product launch | 100-500 | 2-3 days     | 24 hours         |
| VIP access     | 50      | 1 week       | 72 hours         |
| Large raffle   | 1,000+  | 2 weeks      | 48 hours         |

## Handling Issues

### Low Entry Count

If entries are below expectations:

* Extend entry period
* Increase promotion
* Lower any entry requirements
* Partner for cross-promotion

### Duplicate Entries

If you detect duplicate entries:

1. Review entry patterns
2. Identify linked accounts
3. Remove duplicates before draw
4. Consider stricter verification

### Winner Disputes

If a winner disputes results:

1. Provide selection documentation
2. Show their entry confirmation
3. Verify their eligibility
4. Escalate to support if needed

### Low Completion

If many selected winners do not continue:

1. Review the admission window
2. Send additional reminders
3. Verify notification delivery
4. Consider enabling continued selection for future draws

## Compliance Considerations

### Sweepstakes Rules

For promotional draws:

* Check local gambling/sweepstakes laws
* Provide official rules
* Consider "no purchase necessary" options
* Document winner selection

### Data Handling

* Only collect necessary information
* Secure entry data
* Delete after required retention
* Handle winner info appropriately

## Related Guides

* [Experience Schedule](/dashboard/experiences/experience-lifecycle) - Understanding draw timing
* [Experience Analytics](/dashboard/experiences/experience-analytics) - Draw metrics
* [Audience Management](/dashboard/audiences/overview) - Targeting entries