> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/brand/what-would-you-like-to-learn-about/advocate-program/advocate-rewards/referral-promo-codes-for-participants/replace-used-promo-codes.md).

# Replace Used Promo Codes

When an advocate's code is used in a referral, it's marked as used and 1 replacement code is automatically assigned from your available codes. You don't need to do anything.

* Codes are replaced one at a time, as each one is used.
* Replacements only work while you have unused codes. If you run out, advocates can't get new codes until you [upload more](https://help.impact.com/brand/what-would-you-like-to-learn-about/advocate-program/advocate-rewards/referral-promo-codes-for-participants/set-up-referral-promo-codes.md).

## **Give a participant an extra code**

In exceptional cases, you can give a participant a code on top of their assigned codes:

1. Navigate to **Participants** and select the participant.
2. Select the **Codes and Links** tab.
3. Select **Add referral code**.

The code is added to their existing codes on their widget.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.impact.com/brand/what-would-you-like-to-learn-about/advocate-program/advocate-rewards/referral-promo-codes-for-participants/replace-used-promo-codes.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 `automate deployments from our CI pipeline` 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.
