> 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/reach-out-to-partners/newsletters/review-newsletter-engagement-performance.md).

# 审核新闻通讯互动表现

在此界面，您可以查看已发送新闻简报的统计数据。这些数据可帮助您评估新闻简报的表现及其与收件人的互动情况。只有当新闻简报处于已发送或发送失败状态时，您才能查看报告。

#### 查看新闻简报统计数据

1. 从左侧导航栏中选择 ![](/files/209022bdb234289211a24a980f6227a8684cc439) **\[Engage]** → **合作伙伴** → **自动化** → **新闻简报**.
2. 将鼠标悬停在您要查看统计信息的新闻简报上并选择 **查看报告**.

   * 有关此页面上状态筛选器的更多信息，请参阅 *状态筛选器参考* 以下内容。
   * 有关此页面上各列的更多信息，请参阅 *列说明* 以下内容。

   <div data-with-frame="true"><figure><img src="/files/3fc59e7f183a3f92b4f14a439c4f5c565c7d1a3d" alt=""><figcaption></figcaption></figure></div>

<details>

<summary>状态筛选器参考</summary>

<div data-with-frame="true"><figure><img src="/files/fd1e584d5bdfcf0c20f465709fc4801711c3fdae" alt=""><figcaption></figcaption></figure></div>

| 筛选器 | 描述                                 |
| --- | ---------------------------------- |
| 已发送 | 您发送该新闻简报的收件人数量。                    |
| 已打开 | 收件人打开的新闻通讯数量。                      |
| 未打开 | 收件人未打开的新闻简报数量。                     |
| 已点击 | 收件人在新闻通讯中点击某个元素的次数。                |
| 未点击 | 收件人从未点击新闻简报中任何元素的次数。               |
| 已退回 | 新闻通讯未能送达收件人的次数。例如，如果收件人已取消订阅该新闻通讯。 |

</details>

<details>

<summary>列说明</summary>

您还可以查看您发送新闻简报的每位收件人的列出数据。

<div data-with-frame="true"><figure><img src="/files/58c2e47738dbbe38325760e7ed98c81d9fa68bd6" alt=""><figcaption></figcaption></figure></div>

| 列       | 描述                                                                                                                                  |
| ------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| 电子邮件    | 收件人的电子邮件地址。                                                                                                                         |
| 合作伙伴名称  | 新闻简报发送到的合作伙伴账户。                                                                                                                     |
| 合作伙伴 ID | 新闻简报发送到的账户的唯一标识符。                                                                                                                   |
| 联系人姓名   | 接收该新闻简报的收件人姓名。                                                                                                                      |
| 发送日期    | 新闻简报发送给收件人的日期和时间。                                                                                                                   |
| 最后打开时间  | 收件人最后一次打开新闻简报的日期和时间。                                                                                                                |
| 最后点击时间  | 收件人最后一次点击新闻简报中某个元素的日期和时间。                                                                                                           |
| 已退回     | <p>新闻通讯未能送达收件人的次数。例如，如果收件人已取消订阅该新闻通讯。</p><p>• 查看 <a href="/pages/4ec254ac60916bc53800890e6616c5b5b7cf1f75">问题日志</a> 与发送失败相关的内容。</p> |

</details>


---

# 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/platform-features/reach-out-to-partners/newsletters/review-newsletter-engagement-performance.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.