> 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/platform-features/reach-out-to-partners/generate-leads/receive-leads-from-your-partners.md).
# 接收来自合作伙伴的潜在客户
找到合适合作伙伴的最佳方式之一，是从现有合作伙伴那里获得潜在客户。通过将第三方 CRM 系统的潜在客户表单集成到合作伙伴的仪表板中，您可以利用在 impact.com 上已有的合作关系来获取潜在客户。
#### 向您的合作伙伴提供第三方潜在客户表单
1. 从左侧导航菜单中，选择  **\[Engage]** → **内容 → 组件**.
2. 在右上角，选择 **创建组件 → 潜在客户表单**.
3. 输入 **名称** 该潜在客户表单的。
4. 可选地，输入一个 **说明** 适用于该潜在客户表单。
5. 选择 **来源** 您的第三方潜在客户表单的。
* 选择  **\[单选按钮]** **网址** 并输入潜在客户表单 URL。使用带有 URL 来源的潜在客户表单的合作伙伴，其线索将自动归因给他们。
* 或者，选择  **\[单选按钮]** **嵌入代码** 并将嵌入代码输入到提供的字段中。
* 如果您选择 **嵌入代码** 作为您的潜在客户表单来源，您必须添加合作伙伴 ID 令牌 `irpid={irpid}` 到您的嵌入代码中，以跟踪并将潜在客户归因给合作伙伴。如果您选择 **网址** 作为您的潜在客户表单来源，该令牌会自动作为查询参数追加，因此潜在客户将自动归因给提交它们的合作伙伴。
* 查看来源示例 *网址* 和 *嵌入代码* 如下所示。
**示例来源 URL：**
`https://share.hsforms.com/1234_0AbCDE1FgHIjKLmnop2q`
**示例来源嵌入代码：**
```programlisting
```
6. 可选地，  **\[开启]** **限制合作伙伴访问权限** 以设置哪些合作伙伴可以使用此潜在客户表单。您可以将该潜在客户表单限制为特定的 *合作伙伴* 或 *合作伙伴组*.
7. 可选地，添加 **标签** 到您的潜在客户表单。
8. 设置 **语言** 该潜在客户表单的。
9. 选择 **保存**.
* （可选）选择 **预览** 用于潜在客户表单的预览显示。
创建潜在客户表单组件后，它将作为组件在其仪表板上提供给与您建立合作关系的合作伙伴。
{% hint style="success" %}
**注意：** 请参阅 [HubSpot 集成](https://integrations.impact.com/integration-guides/for-brands/plugin-integrations/crm-customer-relationship-management/integrate-with-hubspot) 以跟踪潜在客户表单提交，并在 impact.com 中监控联系人和交易状态的变化（例如潜在客户转化为销售）。
{% endhint %}
---
# 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/platform-features/reach-out-to-partners/generate-leads/receive-leads-from-your-partners.md?ask=&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.