> 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-1-set-up-your-integrations-and-referral-attribution-tracking.md).

# ステップ1：連携と紹介アトリビューション追跡を設定する

別途提供される *技術実装計画* お客様の実装特有の要件やニーズに合わせてカスタマイズされます。技術実装が完了したら、プログラムの設定に進めます。

あなたの [紹介アトリビューション追跡](https://integrations.impact.com/integration-guides/for-brands/advocate/advocate-tracking-integrations/advocate-installation-scripts) これは、誰が紹介しているのか、紹介がどこから来たのか、そして紹介件数がいくつあったのかを把握するのに役立ちます。

Advocateプログラムを作成する際に、プログラムのイベントタイプを共有できます。これにより、既存の impact.com 連携を活用し、それらの間でコンバージョンデータを共有できます。この同じデータを、Advocateプログラムのルール設定にも使用できます。


---

# 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-1-set-up-your-integrations-and-referral-attribution-tracking.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.