> 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/congratulations.md).

# 恭喜！

恭喜！你已经设置好你的推荐人计划，现在可以奖励那些为你带来最多推荐的推荐人参与者了。使用推荐人计划将帮助你通过值得信赖的方式扩大影响力并发展你的计划，同时也与帮助你实现这一目标的人分享它带来的回报。

如果你也在我们其他某种项目类型上刚刚起步，请查看下面相关的指南：

* [我也是 Creator 的新手](/brand/zh/what-would-you-like-to-learn-about/creator-program/introduction-welcome-to-creator.md)
* [我也是 Performance 新手](/brand/zh/what-would-you-like-to-learn-about/performance-program/introduction-welcome-to-impact.com.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/zh/what-would-you-like-to-learn-about/advocate-program/introduction-welcome-to-advocate/congratulations.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.