> 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/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/newsletters/review-newsletter-engagement-performance.md).
# Review Newsletter Engagement Performance
From this screen, you can view statistics on your sent newsletter. This data can help you evaluate the performance of the newsletter and its engagement with recipients. You can only view reports if the newsletter is in a sent or failed to send status.
## View newsletter statistics
1. From the left navigation bar, select  **\[Engage]** → **Partners** → **Automation** → [**Newsletters**](https://app.impact.com/secure/advertiser/fr/newsletter-ui.ihtml).
2. Hover your cursor over a newsletter.
3. Select **View Report**.
The report shows the newsletter's name, its subject line, and its status. It opens on the *Partners* tab. Select *Contacts* to see individual recipients.
Both tabs have a search box for a partner name, partner ID, or email address, along with **Clear All** to reset the search and any filters, **Sort Order** to reorder the table, and the column icon to choose which columns appear. The **Contacts** tab adds a **Status** filter; the **Partners** tab has none. Select **Newsletters** in the breadcrumb to return to the newsletter list.
## Review partner results
The *Partners* tab shows one row for each partner the newsletter targeted. Select **+ \[Expand]** on a row to expand that partner and see its individual contacts, each with its own status.
| Metric | What it counts |
| -------------------- | -------------------------------------------------------------- |
| *Estimated Partners* | Partners the newsletter targeted. |
| *Processed Partners* | Partners impact.com processed the newsletter for. |
| *Delivered* | Partners that received the newsletter, with the delivery rate. |
| *Opened* | Partners that opened the newsletter. |
| *Clicked* | Partners that selected a link. |
| *Unsubscribed* | Partners that unsubscribed. |
| *Bounced* | Partners whose email address returned the newsletter. |
| *Errors* | Partners the newsletter could not reach. |
Partners tab columns
| Column | Description |
| -------------- | ----------------------------------------------------- |
| *Partner* | The partner's name. |
| *Stage* | How far the newsletter progressed for that partner. |
| *Processed* | Contacts impact.com processed for the partner. |
| *Delivered* | Contacts that received the newsletter. |
| *Opened* | Contacts that opened the newsletter. |
| *Clicked* | Contacts that selected a link. |
| *Unsubscribed* | Contacts that unsubscribed. |
| *Bounced* | Contacts whose email address returned the newsletter. |
| *Errors* | Contacts the newsletter could not reach. |
## Review contact results
The *Contacts* tab shows one row for each contact the newsletter was sent to, and the partner each contact belongs to.
| Metric | What it counts |
| -------------------- | -------------------------------------------------------------- |
| *Processed Contacts* | Contacts impact.com processed the newsletter for. |
| *Delivered* | Contacts that received the newsletter, with the delivery rate. |
| *Opened* | Contacts that opened the newsletter. |
| *Clicked* | Contacts that selected a link. |
| *Unsubscribed* | Contacts that unsubscribed. |
| *Bounced* | Contacts whose email address returned the newsletter. |
| *Errors* | Contacts the newsletter could not reach. |
Contacts tab columns
| Column | Description |
| -------------- | -------------------------------------------------------- |
| *Email* | The contact's email address. |
| *First Name* | The contact's first name. |
| *Last Name* | The contact's last name. |
| *Contact Type* | How impact.com uses the contact. |
| *Partner* | The partner the contact belongs to. |
| *Status* | The contact's delivery status, with a timestamp beneath. |
Status filter
Select **Status** to filter the table by one or more delivery statuses. These describe what happened to each contact's email, not how far the newsletter progressed. For newsletter stages, see [Manage Newsletters as a Brand](/brand/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/newsletters/manage-newsletters-as-a-brand.md).
*Delivered*, *Sent*, *Opened*, *Clicked*, *Bounced*, *Unsubscribed*, *Failed*, *Dropped*, *Spam Report*, *No Contacts*, *Out of Network*, *Blocked by Partner*, *No Email*, and *Invalid Email*.
### Related articles
To see a newsletter's processing history, select **Events Log** at the top right of the report. See [Open the Events Log](/brand/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/newsletters/manage-your-newsletter-issues-log.md#open-the-events-log).
To find a newsletter or check what actions each one offers, see [Manage Newsletters as a Brand](/brand/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/newsletters/manage-newsletters-as-a-brand.md).
---
# 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/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/newsletters/review-newsletter-engagement-performance.md?ask=&goal=
```
`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.