> 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/prospect-import-for-brands/prospect-import-faq.md).

# 潜客导入常见问题

以下是有关导入潜在合作伙伴的常见问题。要了解更多信息，请参阅 [潜在合作伙伴导入说明](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/platform-features/prospect-import-for-brands/prospect-import-explained.md) 和 [批量导入潜在合作伙伴到您的计划](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/platform-features/prospect-import-for-brands/bulk-import-prospects-to-your-program.md).

<details>

<summary>如何知道导入是否成功？</summary>

导入后， *上传摘要* 页面会告知您潜在合作伙伴文件是否已成功提交处理。这表示文件已通过初步验证，但不保证所有潜在合作伙伴都已成功导入。导入处理完毕后，您会收到一封电子邮件，其中包含已导入潜在合作伙伴的摘要，列出成功导入的对象以及需要修正的错误（如有）。

</details>

<details>

<summary>导入需要多长时间？</summary>

导入每一行大约需要 4 秒。例如，导入 500 行大约需要 25 分钟。由于处理需要一定时间，上传将以异步方式进行。导入完成后，您会收到电子邮件和应用内通知。

</details>

<details>

<summary>如果导入工具识别出已有的 impact.com 账户，会发生什么情况？</summary>

如果找到现有的 impact.com 合作伙伴账户，合作伙伴的姓名和电子邮件地址将更新为其当前账户设置中的信息。您导入的联系人电子邮件仍会保留，并作为自定义联系人显示在合作伙伴的侧滑面板中。无论是常规导入还是试运行，您都可以在成功文件中看到匹配的合作伙伴姓名和 ID。

</details>

<details>

<summary>导入时可以为合作伙伴添加多个分组吗？</summary>

虽然您无法在导入表格的同一行中为一个合作伙伴分配多个分组，但可以为该合作伙伴的每个分组分配单独添加一行，从而将其分配到不同的分组。

{% hint style="info" %}
**注意：** 导入潜在合作伙伴时无法创建分组。请确保在导入潜在合作伙伴列表之前，已创建所需的所有分组。
{% endhint %}

</details>

<details>

<summary>如果我上传的分组名称不存在，会发生什么情况？</summary>

该记录不会被导入，您会在报告中看到错误。

</details>

<details>

<summary>如何联系自定义联系人？</summary>

设置电子邮件工作流时，您可以选择向潜在合作伙伴的 Marketplace 联系人或自定义联系人发送邀请。

{% hint style="info" %}
**注意：** 如果潜在合作伙伴是另一品牌的 [直接合作伙伴](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/performance-program/recruiting-partners/marketplace-vs-direct-partner-recruiting-explained.md) （即他们只与一个品牌建立合作关系），那么电子邮件邀请只会发送给您提供的自定义联系人。
{% endhint %}

</details>

<details>

<summary>如果导入的潜在合作伙伴与某个直接合作伙伴匹配（即只与一个品牌建立合作关系的合作伙伴），会怎么样？</summary>

您导入的某些潜在合作伙伴可能已与 impact.com 上的其他品牌建立直接合作关系，但其账户关联的电子邮件地址会被隐藏，只有在您与其建立合作关系后才会显示。您仍可以通过 [电子邮件工作流](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/email-workflows/create-and-manage-email-workflows.md)联系这些合作伙伴，系统会向其自定义联系人发送电子邮件。

</details>

<details>

<summary>如果导入的潜在合作伙伴记录有误，该怎么办？</summary>

如果您导入的潜在合作伙伴与错误的合作伙伴账户匹配，可能是因为该合作伙伴在 impact.com 上有多个账户。您仍可通过电子邮件工作流联系该合作伙伴，因为导入时上传的自定义联系人将用于联系。这种不匹配情况通常发生在合作伙伴拥有多个账户时（例如，针对不同地区的账户）。默认情况下，我们的系统会自动关联其最活跃的账户。

</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/platform-features/prospect-import-for-brands/prospect-import-faq.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.
