> 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/introduction-welcome-to-advocate/step-3-manage-your-advocate-participant-experiences.md).

# ステップ3：アドボケイト参加者の体験を管理する

次に、アドボケイトをカスタマイズします [参加者体験](/brand/ja/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participant-experiences/introduction-to-participant-experiences.md)。顧客アドボケイトや、その紹介先に取引メールを送信できます。プログラムには初期設定として標準版のプログラムメールが設定されていますが、私たちは次を推奨します [プログラムメールを調整すること](/brand/ja/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participant-experiences/email-experiences/create-and-customize-advocate-program-emails.md) 情報がプログラムや製品に関連し、よりパーソナライズされた印象になるようにするためです。

次にカスタマイズするのは、あなたの [プログラムウィジェット](/brand/ja/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participant-experiences.md) または [マイクロサイト](/brand/ja/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participant-experiences/microsite-experiences.md)。プログラムウィジェットまたはマイクロサイトは、参加者が紹介プログラムにアクセスし、利用するための主な方法です。ウィジェットとマイクロサイトは、紹介プログラムのメッセージングをブランドとして強化するものであり、顧客アドボケイトが紹介を行うための出発点となります。


---

# 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/introduction-welcome-to-advocate/step-3-manage-your-advocate-participant-experiences.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.