> 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/integrations-and-data-exchange/custom-fields/setup-for-rewards-and-fortune-wheels.md).

# Setup for Rewards and Fortune Wheels

Every reward type, and Fortune Wheels, has its own Custom Fields schema, set up from **Custom Fields** the same way as for [Members](/implementation-guide/members-and-activity/members.md) and [Campaigns](broken://pages/fde74abd6c30b23c57ef3b3b181b88c67659115d). Subgroups aren't supported here — only simple fields.

### Entering values

The reward (or Fortune Wheel) editor has a dedicated **Custom Fields** section, scoped to that specific reward type's schema. Required fields must be filled in before saving.

### Custom fields in webhooks

Custom field data is included in the **created** and **updated** webhooks for that reward, mirroring the campaign behavior described in [Custom Fields for Campaigns, Leaderboards & Challenges](broken://pages/fde74abd6c30b23c57ef3b3b181b88c67659115d).

{% hint style="info" %}
The read/write API pattern (group → field payload, `PUT` replace vs. `PATCH` partial update) is the same across Members, Campaigns, and Rewards — see [Setup ](broken://pages/73ab80dfa53158596fe151b346f507e6fe9600af)for the full request/response shapes.
{% 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 following URL with the `ask` and `goal` query parameters:

```
GET https://help.openloyalty.io/implementation-guide/integrations-and-data-exchange/custom-fields/setup-for-rewards-and-fortune-wheels.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.