> For the complete documentation index, see [llms.txt](https://help.openloyalty.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.openloyalty.io/implementation-guide/gamification/badges/using-badges-in-campaigns.md).

# Using Badges in Campaigns

Automatically grant badges when a campaign rule matches.

## Overview

Campaigns can grant badges automatically when rule conditions are met.\
Use this to tag members based on behavior or milestones.

{% hint style="info" %}
Create the badge first. Then you can select it in a campaign effect.
{% endhint %}

### Example scenario

Grant a **Frequent Buyer** badge after a member completes a qualifying purchase.

### Configure the “Grant badge” effect

{% stepper %}
{% step %}

### Open a campaign

1. Go to **Campaigns**.
2. Create a campaign or open an existing one.
   {% endstep %}

{% step %}

### Add rules and conditions

1. Add a **rule**.
2. Configure the rule **conditions**.
   {% endstep %}

{% step %}

### Add the badge effect

1. Add an **effect**.
2. Set **Action type** to **Grant badge**.
3. Select the **Badge** you want to grant.

<figure><img src="https://content.gitbook.com/content/Z4Fuoa1PTF0DrNTgjzJu/blobs/28wRO8a2elfS4pHlfhp5/image.png" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://help.openloyalty.io/implementation-guide/gamification/badges/using-badges-in-campaigns.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

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.