> 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/best-practices-for-referral-programs/best-practices-for-marketing-and-scaling-your-advocate-program.md).

# 营销和扩展你的 Advocate 项目的最佳实践

在 impact.com 设置好您的 Advocate 计划后，就该助力它不断发展了！

优秀的推荐计划不会止步于设置完成——它需要持续、巧妙的推广才能蓬勃发展。借助 Advocate 的工具，让计划持续获得关注、便于分享并保持品牌一致，您就能将满意的客户转化为稳定的推荐者。

&#x20;<img src="https://1651675991-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FpVKEIcehMut8QKRmaUZu%2Fuploads%2FiaGgKM32jOcur3x3IZNO%2Fai-sparkles.svg?alt=media&amp;token=65c2c155-b61d-45f8-990e-c349f0d7afdc" alt="" data-size="original"> ask impact supports this feature in chat.

{% hint style="info" %}
**提示：** 试着在 ask impact 中提问：

* *扩展推荐计划有哪些最佳实践？*
  {% endhint %}

成功始于曝光度。推荐计划的影响力，取决于有多少人了解它并乐于分享。以下情况下，人们更愿意推荐：

* 计划容易找到。
* 计划的流程和规则清晰明了。
* 奖励有吸引力。
* 体验具有品牌特色且值得信赖。

在本系列中，我们将分享专业建议，助您让推荐计划从设置走向成功：

* [打造品牌风格并自定义您的 Advocate 计划](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/advocate-program/best-practices-for-referral-programs/brand-and-customize-your-advocate-program.md): 设置推荐体验，使其从交易邮件到分享文案和推荐链接，在外观、感受和表达上都像是您品牌中值得信赖的一部分。
* [为您的 Advocate 计划制定战略营销方案](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/advocate-program/best-practices-for-referral-programs/strategic-marketing-for-your-advocate-program.md): 在关键客户触点推出计划，并通过巧妙、持续的营销提升计划曝光度，从而促进参与和推荐。
* [优化您的 Advocate 计划](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/advocate-program/best-practices-for-referral-programs/optimize-your-advocate-program.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/best-practices-for-referral-programs/best-practices-for-marketing-and-scaling-your-advocate-program.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.
