> 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>

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

### 查找创作者

你还可以发现创作者，并在标准合作伙伴关系之外开展以内容为驱动的创作者活动。创作者会以与合作伙伴相同的方式显示在“发现”中。要了解更多关于与创作者合作的信息，请参阅 [创作者计划说明](/brand/zh/what-would-you-like-to-learn-about/creator-program/creator-program-explained.md).

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

如果你的 Amazon 卖家项目 [可在 Marketplace 中被发现](https://help.impact.com/brand/what-would-you-like-to-learn-about/account-administration/program-settings/profile-and-branding/manage-your-marketplace-profile-for-brands)，合作伙伴可以主动申请加入。 [处理申请](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/review-partner-applications/manage-applications-and-send-proposals) 快速处理申请是让你的收入更快增长的简单方法！它还有助于与希望与你合作的合作伙伴建立信任与信心。为避免手动审核申请并使待处理合作关系队列杂乱无章，可通过自动化处理节省时间：

* 使用 [工作流](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/email-workflows/create-and-manage-email-workflows) 当你希望根据特定规则自动接受或拒绝时。
* 使用 [Impact AI](https://help.impact.com/brand/what-would-you-like-to-learn-about/performance-program/recruiting-partners/impact-ai-explained) 当你希望根据系统推荐的标准自动接受或拒绝时。这对于刚接触联盟营销的人来说是个不错的选择。

合作伙伴的收件箱也会变得很忙，就像你的一样。跟进 [已发送的提案](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/contracts/review-contract-proposals-youve-sent) ，让你的拓展联系始终被优先记住。

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

接下来是创建合作伙伴组。 [合作伙伴组](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/partner-groups/create-and-manage-partner-groups) 可让你对合作伙伴或创作者进行细分，随着新合作伙伴加入，便于管理你的组合。通过细分后的合作伙伴，你可以有效使用新闻通讯、批量申请管理、自定义条款以及合作伙伴专属内容上传等功能。


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
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=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
