> For the complete documentation index, see [llms.txt](https://docs.fuul.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fuul.xyz/incentives-manager/badges.md).

# Badges

Badges are visual labels assigned to users to recognize achievements, status, or membership. They appear on dashboards and leaderboards, giving users public recognition.

## How they work

A badge is an **audience with a display layer** — it has a name, image, and description on top of a standard audience segment. Any user who belongs to that audience receives the badge.

This means badges inherit all audience capabilities:

* **Static badges** — manually curated lists of users (e.g., early supporters, approved affiliates)
* **Dynamic badges** — automatically assigned based on conditions like volume, conversions, token holdings, or points balance

## Use cases

| Badge             | Audience condition         | Applies to |
| ----------------- | -------------------------- | ---------- |
| 🥇 Gold Partner   | Referred volume > $100K    | Affiliates |
| 🐋 Whale          | Token balance > 100K       | Any user   |
| 🏆 Top Trader     | Trading volume > $1M       | Traders    |
| ⭐ Early Supporter | Static list                | Any user   |
| 🔥 Power User     | Number of conversions > 50 | Any user   |

## Configuration

Badges are configured in the **Audiences** section of the Fuul app. When creating or editing an audience, enable the badge option and set:

* **Name** — displayed to the user
* **Image** — icon or logo shown on dashboards and leaderboards
* **Description** — short explanation of what the badge represents

{% hint style="info" %}
Badges are a display feature on top of audiences. To understand how audiences and segmentation work, see [Tiers & Multipliers](/core-concepts/tiers-and-multipliers.md) and [Managing Audiences](/developer-guide/managing-audiences.md).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.fuul.xyz/incentives-manager/badges.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.