> 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) **\[互动]** → **内容 → 请求**.
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.
