> ## 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.

# Bot Protection

> How Fanfare helps protect high-demand experiences from automated misuse.

Fanfare includes bot and abuse protection designed to help keep high-demand experiences fair for legitimate consumers.

<Note>
  This page describes the public integration contract at a high level. Specific detection signals, thresholds, and enforcement rules are intentionally not documented publicly.
</Note>

## Why Bot Protection Matters

High-demand launches can attract automated abuse, including scripted entry attempts, account misuse, queue bypass attempts, and disruptive traffic spikes. Fanfare helps preserve a fair path for real consumers without requiring customers to build their own anti-abuse system.

## Protection Layers

Fanfare combines several categories of protection:

<CardGroup cols={2}>
  <Card title="Client integrity" icon="shield-check">
    The SDK includes the client-side context needed by Fanfare protection.
  </Card>

  <Card title="Traffic controls" icon="gauge">
    Request patterns are monitored and controlled to reduce automated abuse.
  </Card>

  <Card title="Experience rules" icon="sliders">
    Entry, purchase, and participation limits can be configured per launch.
  </Card>

  <Card title="Review signals" icon="chart-line">
    Dashboards surface aggregate protection outcomes for launch monitoring.
  </Card>
</CardGroup>

## Configuring Protection

### Protection Levels

Choose the protection level that matches the expected launch profile:

| Level    | Description                            | Use Case      |
| -------- | -------------------------------------- | ------------- |
| Standard | Balanced protection and UX             | Most launches |
| Enhanced | Stricter checks for higher-demand work | Major drops   |
| Maximum  | Most restrictive protection posture    | Peak demand   |

Configure protection in the dashboard under **Settings > Security**.

### Per-Experience Settings

Different experiences may need different protection levels. Use the dashboard or API to configure the protection posture, authentication requirements, and participation limits for each experience.

### Purchase And Participation Limits

Combine bot protection with customer-facing limits such as:

* Maximum entries per verified consumer
* Maximum purchases per order or experience
* Authentication requirements for specific launches
* Draw or queue mechanics for fair allocation

## Consumer Experience

Most legitimate consumers should continue without interruption. When additional verification is required, the SDK handles the verification flow and returns a clear state to your integration. Consumers who cannot be verified should see a plain, helpful message and a support path.

```typescript theme={null}
try {
  await client.experiences.enter(experienceId);
} catch (error) {
  if (error.code === "ACCESS_DENIED") {
    showMessage("We could not verify your access. Please try again or contact support.");
  }
}
```

## Integration Recommendations

1. Keep the SDK updated so your integration receives current protection behavior.
2. Use Fanfare SDKs or documented APIs rather than recreating protection-sensitive flows.
3. Validate server-side handoffs before fulfilling inventory or issuing rewards.
4. Monitor launch dashboards and support channels during high-demand moments.

## Monitoring And Support

The dashboard reports aggregate protection outcomes so teams can understand whether a launch is healthy and whether legitimate consumers need help. If a consumer reports that they were blocked, collect the experience, approximate time, and any displayed support code, then contact Fanfare support for review.