> 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/performance-program/recruiting-partners/screen-partners-automatically-with-partner-verification.md).

# 使用合作伙伴验证自动筛选合作伙伴

*合作伙伴验证* 用于控制选择加入您项目的合作伙伴是否也会由 impact.com 进行市场筛选。它会改变合作伙伴完成申请清单后会发生什么。

## 找到该设置

1. 从顶部导航栏中，选择 ![](https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2F210dEQa93qyQgoJDkieL%2FUser%20profile.svg?alt=media\&token=f84c5b17-fae4-4a30-990a-9de5e57a150b) **\[用户资料] → 设置**.
2. 在右侧，位于 *品牌设置*，选择 [**合作伙伴注册页面**](https://app.impact.com/secure/advertiser/campaign/partner-signup-form-settings-flow.ihtml).
3. 找到 *合作伙伴验证*.

该设置对每个项目分别生效，因此请确认已选择正确的项目。更改它会影响之后加入的合作伙伴，不会影响已经在您项目中的合作伙伴。

## 选择一个设置

开启验证可接收已筛选的合作伙伴、自动批准，并让您的合作伙伴在 impact.com 上接触其他品牌。若您不希望 impact.com 自动提交其市场申请，请将其关闭。\
\
请参阅下表，了解每种设置下会有哪些变化。

{% hint style="success" icon="circle-info" %}
**品牌权衡：** 被批准进入市场的合作伙伴会从您的品牌标识切换为 impact.com 品牌标识。被拒绝的合作伙伴则保留您的品牌标识。
{% endhint %}

## 比较这两种设置

| 变化内容                               | 开启验证                                              | 关闭验证                    |
| ---------------------------------- | ------------------------------------------------- | ----------------------- |
| 合作伙伴加入 impact.com 市场的申请            | 在他们完成清单后于后台提交                                     | 不提交——合作伙伴可以从其个人资料菜单自行申请 |
| 合作伙伴姓名旁的 Marketplace Verified 勾选标记 | 对通过的合作伙伴显示                                        | 不显示                     |
| 您对其加入您项目的申请所做的决定                   | 完全由您决定                                            | 完全由您决定                  |
| 合作伙伴在其仪表板中看到的品牌标识                  | 一旦合作伙伴被批准进入市场，就显示 impact.com 品牌标识；如果被拒绝，则显示您的品牌标识 | 始终显示您的品牌标识，除非合作伙伴自行加入市场 |

## 了解 Marketplace Verified

Marketplace Verified 表示合作伙伴通过了 impact.com 筛选：品牌安全、欺诈和内容检查，并确认该合作伙伴至少拥有他们所列出的一个推广渠道。

将其作为自动化工作流中的条件，以更快批准已筛选的合作伙伴，而不是逐一手动审核。

关于在每种招募路径中由谁验证合作伙伴，请参阅 [Marketplace 与 Direct：合作伙伴招募说明](/brand/zh/what-would-you-like-to-learn-about/performance-program/recruiting-partners/marketplace-vs-direct-partner-recruiting-explained.md).

## 常见问题

<details>

<summary>验证会决定谁加入我的项目吗？</summary>

不会。您的批准决定是完全独立的。合作伙伴可以通过验证，但仍然会被您拒绝。

</details>

<details>

<summary>合作伙伴知道我使用的是哪个设置吗？</summary>

不会。该设置在任何时候都不会向合作伙伴显示。

</details>

<details>

<summary>如果合作伙伴未通过验证，他们会收到通知吗？</summary>

不会。他们申请的是您的项目，而不是市场，因此不会发送市场拒绝通知。

</details>

<details>

<summary>已批准的合作伙伴何时会得知市场信息？</summary>

impact.com 会在批准后延迟一天发送市场通知，因此合作伙伴会先加入您的项目，然后才会看到他们可参与的其他品牌。在该时间窗口内作出决定可让您的项目优先。

</details>

### 相关文章

* [自定义合作伙伴注册页面](/brand/zh/what-would-you-like-to-learn-about/performance-program/recruiting-partners/customize-the-partner-sign-up-page.md) — 设置合作伙伴在注册您的项目时看到的页面，其中包括您的条款、问卷以及合作伙伴验证开关本身。
* [Marketplace 与 Direct：合作伙伴招募说明](/brand/zh/what-would-you-like-to-learn-about/performance-program/recruiting-partners/marketplace-vs-direct-partner-recruiting-explained.md) — 比较从 impact.com 市场招募合作伙伴与直接邀请他们加入您的项目，并了解在每种情况下由谁验证合作伙伴。


---

# 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/performance-program/recruiting-partners/screen-partners-automatically-with-partner-verification.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.
