> 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/partner/zh/ni-xiang-liao-jie-shen-me/account-management/account-settings/notification-settings/create-custom-notifications-as-a-partner.md).
# 作为合作伙伴创建自定义通知
您可以创建自定义电子邮件通知，当特定事件发生时，它们会提醒您。了解如何设置并自定义这些通知。
## 查看现有的自定义通知
1. 在顶部导航栏中，选择  **\[通知]**.
2. 在通知面板右上角，选择 [**设置**](https://app.impact.com/secure/mediapartner/notification/view-edit-notification-deliverychannel-settings-publisher-flow.ihtml) 以编辑通知设置。
3. 从顶部导航栏上的 *通知频率设置* 页面中，选择 **自定义通知**.
* 您会看到一个包含当前现有通知的表格。
4. 要修改通知，请将鼠标悬停在表格条目上并选择  **\[更多]** 行末的
* 有关修改选项的更多信息，请参阅 *选项参考* 相同。
选项参考
| 选项 | 描述 |
| ------- | ------------------------------ |
| 编辑 | 修改该通知的 *通知详情*, *通知规则*，或 *共享* 。 |
| 订阅/取消订阅 | 选择此选项可接收（或停止接收）此通知。 |
| 停用/重新启用 | 选择此选项可禁用（或启用）此通知。 |
| 删除 | 通知停用后，您可以选择此选项将其删除。 |
## 创建自定义通知
1. 在顶部导航栏中，选择  **\[通知]**.
2. 在通知面板右上角，选择 [**设置**](https://app.impact.com/secure/mediapartner/notification/view-edit-notification-deliverychannel-settings-publisher-flow.ihtml) 以编辑通知设置。
3. 从顶部导航栏上的 *通知频率设置* 页面中，选择 **自定义通知**.
4. 在 *自定义通知* 页面中，选择 **创建自定义通知**  **\[下拉菜单]** 右上角的
* 您可以选择创建一个 *欺诈* 通知或一个 *业绩* 通知，从下拉菜单中选择。
5. 选择 **账户** 该通知应适用的，然后添加一个 **通知名称** 和 **描述**.
* 当您收到通知时，这些内容会显示出来。
6. 添加 *通知规则*.
7. 也可以选择  **\[已勾选复选框]** **设为公开** 如果您希望其他账户成员也能访问该通知。
8. 选择 **保存** 以完成创建过程。
自定义通知示例
这里有一个自定义通知的快速示例，帮助您入门！
**场景**：Dinah Soares 希望在客户点击量连续 7 天低于 1,000 时，以及操作量连续 7 天低于 1,000 时，收到电子邮件通知。该通知应提示她联系营销团队，以便他们优化数字资产支出。
我们建议她创建一个 *业绩* 使用以下配置的通知：
---
# 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/partner/zh/ni-xiang-liao-jie-shen-me/account-management/account-settings/notification-settings/create-custom-notifications-as-a-partner.md?ask=&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.
