> 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/ads/requests-from-partners/review-email-drop-requests-from-partners.md).

# 审核合作伙伴提交的邮件投放请求

与你合作的一些合作伙伴可能会通过电子邮件为你的品牌投放广告或进行推广。这些合作伙伴可以向你提交内容请求，以及你的抑制列表。

* 合作伙伴可以向你请求使用你现有的电子邮件广告内容，以在他们的渠道上促进行动。
* 你可以批准或拒绝这些请求，并提供已批准的电子邮件广告内容供他们使用——批准后，他们还将可以访问你的抑制列表。
* 合作伙伴还可以向你请求新的电子邮件广告内容——创建完成后，他们必须再提交电子邮件投放请求才能使用它。

#### 批准或拒绝请求

1. 从左侧导航菜单中，选择 ![](https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-230534471fef5f40808e921e41ee44e4a06ded03%2Fe6cb9548999afdc1ed3ce4942e4cb5b45b5cecbd323267aac2a7cd1915fccc09.svg?alt=media) **\[Engage]** → **内容 → 请求**.
2. 在……中 *申请* 列表，查找 *电子邮件投放* 请求类型。
3. 在最右侧，选择 ![](https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2FMLtRUwWz0pujlfmYWOgg%2FMoreVN.svg?alt=media\&token=03a3c355-a347-4207-baf7-c44fadf6d080) **\[菜单] →** **处理**.
4. 查看 *请求详情*，以及 **可选择留下回复** 给发起请求的合作伙伴。
5. 选择 **拒绝请求** 或 **批准** 以完成该流程。

当你批准来自合作伙伴的电子邮件投放请求时，你是在授予他们访问你预先创建的某个电子邮件广告的权限。获批后，合作伙伴将可按电子邮件广告内容的配置访问你的抑制列表。


---

# 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/ads/requests-from-partners/review-email-drop-requests-from-partners.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.