> 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/manage-newsletters-as-a-brand.md).
# Manage Newsletters as a Brand
The *Newsletters* screen lists every newsletter in your program and groups them by how far each one has progressed. Use it to check on a send, act on a draft, or open a report.
## Open the Newsletters screen
From the left navigation bar, select  **\[Engage]** → **Partners** → **Automation** → [**Newsletters**](https://app.impact.com/secure/advertiser/fr/newsletter-ui.ihtml).
## Narrow the list
The screen opens with every newsletter listed. Four summary cards above the table count the newsletters at each point in the sending lifecycle, and together they account for the full list. Select a summary card to filter the table to those newsletters.
| Summary card | Statuses it holds | What it holds |
| -------------- | -------------------------------------------------------- | --------------------------------------------------------------------------------- |
| **Drafted** | *Draft*, *Active* | Newsletters you saved but have not sent, and newsletters scheduled to send later. |
| **Processing** | *Queued*, *Running*, *Enriching*, *Staged*, *Delivering* | Newsletters impact.com is working through the delivery pipeline. |
| **Completed** | *Sent* | Newsletters that finished sending. |
| **Failed** | *Failed* | Newsletters that stopped because of an error. |
{% hint style="info" %}
**Processing stages:** *Queued* (waiting to start) → *Running* (fetching partner and contact data) → *Enriching* (resolving ad codes) → *Staged* (preparing to send) → *Delivering* (sending emails).
{% endhint %}
The *Status* column names the specific stage rather than the summary card, so the two labels do not always match. A newsletter that finished sending sits on the **Completed** summary card with a *Sent* status, and the **Status** filter lists it as *Completed*.
Use the controls above the table to narrow a long list further.
| Control | What it does |
| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Search by name** | Filters the table to newsletters whose name matches your text. |
| **Status** | Opens a drop-down menu of the stages available on the summary card you are on. Select **Select All** or **Clear** to add or remove all of them at once. |
| **Clear All** | Resets the search box and the status selection together. |
| **Sort Order** | Sorts the table by *Newsletter* or *Created*. |
The **Status** filter offers only the stages the summary card you are on can hold: *Draft* and *Active* on the **Drafted** summary card, and *Queued*, *Running*, *Enriching*, *Staged*, and *Delivering* on the **Processing** summary card. Before you select a summary card it offers all nine stages. The **Completed** and **Failed** summary cards hold a single stage each, so they have no **Status** filter.
## Choose an action
Hover your cursor over a newsletter to see the actions available for it. What you can do depends on the stage the newsletter has reached: before it sends you can change it, while it processes you can follow its progress, and once it finishes you can read its results. The most common actions appear on the row — select  **\[More]** for the rest.
| Action | Available for | What it does |
| ---------------------- | --------------------------------------- | --------------------------------------------------------------------- |
| **Edit** | *Draft*, *Active* | Makes changes to the newsletter. |
| **Send Test Email** | *Draft*, *Active* | Sends a copy to yourself before the newsletter reaches your partners. |
| **Send**, **Schedule** | *Draft* | Sends the newsletter immediately, or sets it to send later. |
| **Events Log** | Every stage except *Draft* and *Active* | Opens the newsletter's processing history. |
| **View Report** | *Sent*, *Failed* | Opens the statistics for the newsletter. |
| **Duplicate** | Every stage | Creates a copy of the newsletter. |
| **Delete** | *Draft*, *Active*, *Sent*, *Failed* | Removes the newsletter. Not available while it processes. |
## Review the columns for each summary card
Select  **\[Columns]** on the right of the screen to add or remove columns. Each summary card shows the counts that matter at that point in the lifecycle.
Drafted summary card
| Column | Description |
| ------------ | -------------------------------------------------------- |
| *Newsletter* | The newsletter's name, with its subject line beneath. |
| *Segment* | The audience segment the newsletter targets. |
| *Created* | The date and time you created the newsletter. |
| *Status* | The newsletter's stage, with the last edit time beneath. |
Processing and Failed summary cards
| Column | Description |
| -------------------- | ----------------------------------------------------- |
| *Newsletter* | The newsletter's name, with its subject line beneath. |
| *Segment* | The audience segment the newsletter targets. |
| *Est. Partners* | Partners the newsletter is expected to reach. |
| *Processed Partners* | Partners impact.com has processed so far. |
| *Processed Contacts* | Contacts impact.com has processed so far. |
| *Status* | The newsletter's stage, with a timestamp beneath. |
Completed summary card
| Column | Description |
| ------------ | --------------------------------------------------------------- |
| *Newsletter* | The newsletter's name, with its subject line beneath. |
| *Segment* | The audience segment the newsletter targets. |
| *Partners* | Partners the newsletter reached. |
| *Delivered* | Contacts that received the newsletter, with the delivery rate. |
| *Opened* | Contacts that opened the newsletter. |
| *Clicked* | Contacts that selected a link. |
| *Failed* | Contacts the newsletter could not reach, with the failure rate. |
| *Status* | The newsletter's stage, with the send time beneath. |
## Newsletters FAQ
Why do the columns change when you select a different summary card?
Each summary card shows the counts that matter at that point in the lifecycle. The **Processing** and **Failed** summary cards show how many partners and contacts impact.com has worked through, and the **Completed** summary card shows delivery and engagement results.
Where do you see why a newsletter failed?
Select **Events Log** on the newsletter's row to open its processing history. 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).
Why are the Delivered, Opened, and Clicked counts lower than expected?
Engagement metrics take between 1 hour and 24 hours to update fully after a newsletter sends. See [Create & Send Newsletters to Partners](/brand/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/newsletters/create-and-send-newsletters-to-partners.md).
## Related articles
To read a newsletter's engagement metrics, see [Review Newsletter Engagement Performance](/brand/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/newsletters/review-newsletter-engagement-performance.md).
To create a newsletter, see [Create & Send Newsletters to Partners](/brand/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/newsletters/create-and-send-newsletters-to-partners.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/manage-newsletters-as-a-brand.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.