> 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/ja/what-would-you-like-to-learn-about/advocate-program/advocate-rewards/view-advocate-reward-catalog.md).

# Advocate報酬カタログを表示する

〜から *報酬カタログ* 画面でアドボケイトの詳細を表示します [報酬](/brand/ja/what-would-you-like-to-learn-about/advocate-program/advocate-rewards/set-up-a-fuel-tank-reward.md).

1. 左側のナビゲーションメニューで、 ![](https://1458456015-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-230534471fef5f40808e921e41ee44e4a06ded03%2Fe6cb9548999afdc1ed3ce4942e4cb5b45b5cecbd323267aac2a7cd1915fccc09.svg?alt=media) **\[Engage] → 報酬** → **カタログ**.
2. フィールドの説明については、以下の表を参照してください。

   | 項目    | 説明                                                            |
   | ----- | ------------------------------------------------------------- |
   | 名前    | 報酬の名前。                                                        |
   | 付与回数  | 過去30日間に報酬が発行された回数。                                            |
   | 使用先   | この報酬を使用しているすべてのプログラムと報酬交換を表示します。                              |
   | 値     | 参加者が紹介から受け取る報酬の割合値です。この値は、パーセンテージだけでなく、金額や顧客向け報酬の値を表すこともできます。 |
   | 種類    | 報酬の種類。例: 割引、クレジット、燃料タンク、ギフトカード。                               |
   | ステータス | 紹介プログラム内の報酬コードの数。                                             |
3. 必要に応じて、管理したいカタログにカーソルを合わせて選択します **編集** または **削除**.


---

# 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/ja/what-would-you-like-to-learn-about/advocate-program/advocate-rewards/view-advocate-reward-catalog.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.