> 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/zh/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/zh/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.