> 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/manage-advocate-participant-experiences/message-links-explained.md).

# 消息链接说明

<a href="https://pxa.impact.com/student/activity/2359755?sid=0c0e3e5c-54c9-4435-9bee-ebcdccb7f292&#x26;sid_i=0?utm_source=app.impact.com&#x26;utm_medium=owned-platform&#x26;utm_content=&#x26;utm_campaign=help-center" class="button primary">参加 PXA 课程</a>

消息链接允许您的客户倡导者将预先格式化的消息分享到各种社交媒体平台。每条消息都包含您预先撰写的文案，也可以包含倡导者专属的分享链接。消息链接可以添加到以下位置：

* 计划小组件
* 事务性电子邮件
* 您的应用或网站，可作为嵌入式链接或按钮
* 外部电子邮件营销活动

<details>

<summary>调整消息链接内容</summary>

1. 在左侧导航菜单中，选择 ![](https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-230534471fef5f40808e921e41ee44e4a06ded03%2Fe6cb9548999afdc1ed3ce4942e4cb5b45b5cecbd323267aac2a7cd1915fccc09.svg?alt=media) **\[互动] → 计划规则**.
2. 在 *计划规则* 屏幕上，选择 **共享** 选项卡。
3. 如果你使用的是 *托管的* Open Graph 来源，然后更新 **标题**, **描述**和 **图片** 该内容将展示给最终用户。
4. 在 *其他分享渠道* 部分中，选择所有需要设置消息的分享渠道，并在 *分享正文* 部分中输入消息。

   <div data-with-frame="true"><figure><img src="https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2F8RQe6UXQs1fTTb7ijE4n%2FScreenshot%202026-05-19%20at%2009.21.21.png?alt=media&amp;token=7078d3ab-d86c-4b02-90fe-5f6fc50f8b15" alt="" width="563"><figcaption></figcaption></figure></div>
5. 选择 **保存分享消息** 以保存内容。

现在，您可以在推荐计划的小组件和事务性邮件中加入消息链接，也可以将其嵌入网站、应用或邮件营销活动的其他位置。

</details>

<details>

<summary>在计划触点中添加消息链接</summary>

内容编辑器允许你在以下位置添加消息链接： [计划小组件](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participant-experiences/widget-experiences/customize-program-widgets.md) 和 [事务性电子邮件](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participant-experiences/email-experiences/create-and-customize-advocate-program-emails.md) 只需极少的额外设置——仅需提供计划 ID。若要在其他位置插入消息链接，可以嵌入符合以下格式的链接。

```programlisting
https://app.referralsaasquatch.com/a/ 
{tenant_alias}/message/redirect/{share_medium}
?engagementMedium={engagement_medium}&accountId= 
{accountId}&userId={userId}&programId=
{program_ID}&rsLandingPage= {rsLandingPage}
```

花括号中的信息 **{ }** 应替换为受支持的参数值之一。

{% hint style="info" %}
**注意：** 此处的 `accountId` 和 `userId` 值必须根据程序数据动态填充。如需有关如何获取这些数据的帮助，请联系开发团队。
{% endhint %}

| 参数                   | 示例                                   | 说明                                                                                                                                                                                                                                                                                                                                                                                  |
| -------------------- | ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `tenant_alias`       | `test_bpinhag9gag`                   | <p>您的计划租户别名。查找租户别名的方法：</p><p>1. 在顶部导航栏中，选择 <img src="https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2F210dEQa93qyQgoJDkieL%2FUser%20profile.svg?alt=media&amp;token=f84c5b17-fae4-4a30-990a-9de5e57a150b" alt=""> <strong>\[用户个人资料] → 设置</strong>.</p><p>2. 在左侧的 <em>倡导者设置</em>下，选择 <strong>常规</strong>.</p> |
| `share_medium`       | `WHATSAPP`                           | <p>倡导者分享此推荐时使用的媒介。</p><p>支持的值：</p><p>• <code>EMAIL</code></p><p>• <code>FACEBOOK</code></p><p>• <code>FBMESSENGER</code></p><p>• <code>LINEMESSENGER</code></p><p>• <code>LINKEDIN</code></p><p>• <code>PINTEREST</code></p><p>• <code>SMS</code></p><p>• <code>TWITTER</code></p><p>• <code>WHATSAPP</code></p>                                                                    |
| `engagement_medium`  | `EMBED`                              | <p>倡导者参与推荐计划时所使用的媒介（例如，嵌入式小组件）。</p><p>支持的值：</p><p>• <code>EMAIL</code></p><p>• <code>EMBED</code></p><p>• <code>MOBILE</code></p><p>• <code>POPUP</code></p>                                                                                                                                                                                                                        |
| `accountId`          | \[根据电子邮件地址生成的哈希 ID]                  | 用于构建此消息链接的账户 ID。对于大多数参与者，用户 ID 和账户 ID 字段的值相同。                                                                                                                                                                                                                                                                                                                                       |
| `userId`             | \[根据电子邮件地址生成的哈希 ID]                  | 用于构建此消息链接的用户 ID。对于大多数参与者，用户 ID 和账户 ID 字段的值相同。                                                                                                                                                                                                                                                                                                                                       |
| `programId`          | `21789`                              | 您的计划 ID。可在 **计划规则** 页面上计划名称下方找到。                                                                                                                                                                                                                                                                                                                                                    |
| `rsLandingPage` （可选） | `https://example.com/driver-program` | <p>覆盖计划的落地页，将生成的分享链接重定向到其他 URL。</p><p>仅支持更改计划落地页 URL 中的路径。出于安全原因，不能重定向到其他域名。</p>                                                                                                                                                                                                                                                                                                    |

{% hint style="info" %}
**示例：** 按照上述格式，以下是 impact.com 演示计划中，用户 ID 和账户 ID 为 `messageLink` 的参与者所对应的消息链接 URL 示例： `klip-referral-program`。此链接会通过电子邮件发送给参与者，供其通过移动链接分享。

```programlisting
https://app.referralsaasquatch.com/a/test_aut32av0b11uc
/message/redirect/EMAIL?engagementMedium=
MOBILE&accountId=messageLink&userId=
messageLink&programId=klip-referral-program
```

{% endhint %}

</details>


---

# 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/manage-advocate-participant-experiences/message-links-explained.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.
