> 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/seller-program/amazon-seller-program/introduction-welcome-to-impact.com/step-2-discovery-and-vetting.md).

# 第 2 步：发现与审核

发现和筛选流程的第一步是联系潜在的合作伙伴或创作者。impact.com 的外联功能可让你找到、审核并邀请你感兴趣的合作伙伴。

## 发现合作伙伴 <a href="#section-id235247184450724" id="section-id235247184450724"></a>

使用 [发现](/brand/zh/what-would-you-like-to-learn-about/performance-program/recruiting-partners/discover/discover-overview.md) 根据对你重要的指标搜索并筛选合作伙伴，例如受众规模或推广方式。在浏览 Discover 或查看合作伙伴资料时，你可以 [将你感兴趣的合作伙伴标记为潜在对象](/brand/zh/what-would-you-like-to-learn-about/performance-program/recruiting-partners/prospective-partners/mark-potential-partners-as-prospects.md) 和 [提出合同条款](/brand/zh/what-would-you-like-to-learn-about/performance-program/recruiting-partners/prospective-partners/send-a-proposal-to-a-prospect.md)。您还可以通过设置来自动化并扩展您的合作伙伴发现 [扩展搜索](/brand/zh/what-would-you-like-to-learn-about/performance-program/recruiting-partners/extended-search.md).

### 查找创作者

你也可以发掘创作者，并将以内容为驱动的创作者活动与你的常规合作同时运行。创作者在 Discover 中的展示方式与合作伙伴相同。要了解更多关于与创作者合作的信息，请参阅 [Creator 计划说明](/brand/zh/what-would-you-like-to-learn-about/creator-program/creator-program-explained.md).

## 管理申请 <a href="#section-id235247184551727" id="section-id235247184551727"></a>

如果你的 Amazon Seller 计划是 [可在 Marketplace 中被发现](/brand/zh/what-would-you-like-to-learn-about/account-administration/program-settings/profile-and-branding/manage-your-marketplace-profile-for-brands.md)，合作伙伴可以主动申请加入。 [处理申请](/brand/zh/what-would-you-like-to-learn-about/platform-features/review-partner-applications/manage-applications-and-send-proposals.md) 快速处理是让你的收入更早增长的简单方法！它还能帮助你与希望与你合作的合作伙伴建立信任和信心。为避免手动审核申请并让待处理的合作关系队列变得杂乱，使用自动化处理可节省时间：

* 使用 [工作流](/brand/zh/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/email-workflows/create-and-manage-email-workflows.md) 当您希望基于特定规则自动批准和拒绝时使用。
* 使用 [Impact AI](/brand/zh/what-would-you-like-to-learn-about/performance-program/recruiting-partners/impact-ai-explained.md) 当您希望根据系统推荐的标准自动批准和拒绝时使用。如果您是联盟营销新手，这是一个很好的选择。

合作伙伴的收件箱也会很忙，就像你的一样。跟进 [已发送的提案](/brand/zh/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/contracts/review-contract-proposals-youve-sent.md) ，让你的外联始终留在对方脑海中。

## 细分合作伙伴 <a href="#section-id235247184636869" id="section-id235247184636869"></a>

接下来是创建合作伙伴组。 [合作伙伴组](/brand/zh/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/partner-groups/create-and-manage-partner-groups.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/seller-program/amazon-seller-program/introduction-welcome-to-impact.com/step-2-discovery-and-vetting.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.
