> For the complete documentation index, see [llms.txt](https://postman-v1.guides.gov.sg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://postman-v1.guides.gov.sg/campaign-guide-email/email/statistics.md).

# Email Statistics

Understand the statistics you can view for your campaign.

The campaign dashboard shows you all the campaigns that you have sent in the past. Campaigns with an export button mean that there are errors or invalid emails in that particular campaign.

![View of campaign dashboard](https://4126954886-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MAQH3DF49Lq0AJudrbF%2Fuploads%2Fgit-blob-0ae53d5ca4c8630589db72aa2b0b59ca376f2281%2Fpostman-email-stat.jpg?alt=media)

You can click into your campaign to see the dashboard of summary statistics.

<figure><img src="https://4126954886-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MAQH3DF49Lq0AJudrbF%2Fuploads%2Fg15RhwkwCNmR1PzWim3L%2Fimage.png?alt=media&amp;token=293305dd-6f36-4ae5-81c1-c228feb02a3b" alt=""><figcaption><p>View of summary statistics dashboard</p></figcaption></figure>

## Types of statuses for emails sent

### Summary Statistics Dashboard

Once your campaign is sent, you can view the statuses of the emails in your summary statistics dashboard:

<table><thead><tr><th width="186.44921875">Status</th><th width="289.90625">Description</th><th>Recommended Action</th></tr></thead><tbody><tr><td><strong>SENT</strong></td><td>Your email was successfully delivered to the recipient.</td><td>No action.</td></tr><tr><td><strong>INVALID</strong></td><td>The email address hard or soft bounced, or is blacklisted.</td><td>Download delivery report and check <code>errorCode</code> column for more information.</td></tr><tr><td><strong>ERROR</strong></td><td>Could not be sent.</td><td>Download delivery report and check <code>errorCode</code> column for more information.</td></tr><tr><td><strong>UNSENT</strong></td><td>In the queue.</td><td>Check back later as your campaign sending is still in progress.</td></tr><tr><td><strong>UNSUBSCRIBER</strong></td><td>Recipient indicated to unsubscribe.</td><td>Remove unsubscribers from your recipient list to avoid campaigns being marked as spam and affecting the reputation of Postman Legacy and your agency. <a href="https://go.gov.sg/postman-unsubscribe-guide">Learn more</a></td></tr></tbody></table>

### Delivery Report

To investigate the `errorCode`s of emails that were not sent, you can view the delivery report by clicking on the `Export` button.&#x20;

{% hint style="warning" %}
Note that Delivery Reports are available for only **30 days** after the campaign is sent. This is an added security measure to prevent unintended access to the entire contact list.
{% endhint %}

Once you click on the `Export` button, you will get a CSV file with the following columns: `recipient`, `status`, `errorCode`, and `updatedAt`.

![](https://4126954886-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MAQH3DF49Lq0AJudrbF%2Fuploads%2Fgit-blob-ca52b42c06f40a8bf1b40cfddce890b575963a70%2Fpostman-statistics.png?alt=media)

#### `status`

See below for how each delivery report status corresponds to the summary statistics dashboard status.

| Delivery report (downloaded CSV) status | Summary statistics dashboard (web app) status |
| --------------------------------------- | --------------------------------------------- |
| Blank                                   | UNSENT                                        |
| SENDING, SUCCESS, READ                  | SENT                                          |
| ERROR                                   | ERROR                                         |
| INVALID\_RECIPIENT                      | INVALID                                       |
| UNSUBSCRIBED                            | UNSUBSCRIBER                                  |

<details>

<summary>Why does my email show SUCCESS/READ in the delivery report but does not appear in my recipient's inbox?</summary>

Neither SUCCESS nor READ is a direct indication that the email is in the inbox, it is only an event callback from our downsteam email provider. SUCCESS means the recipient’s mail server accepted the email. READ means something loaded a hidden image in the email commonly used for read status tracking. That “something” can be a security scanner instead of a person.

**Why SUCCESS but not in the inbox**

* Our email provider marks an email as delivered once the recipient’s mail server accepts it. After that, the email is under the recipient’s mail server, which can still:
  * Move it to spam or junk.
  * Quarantine it. It is likely only an organisation's IT team can see or release these emails.
  * Apply mailbox rules. A rule can move the email to another folder, such as “Other” in Outlook’s Focused Inbox, or delete it.

**Why READ but not in the inbox**

* Our email provider detects an “open” when the email’s hidden tracking image loads. This may lead to false READ statuses:
  * Security scanners can load the image. Many government and corporate mail servers scan emails before delivery, and the scan can load the image. The email then shows READ even if no person opened it, or if it went to quarantine.
  * The recipient may have accidentally opened it, then moved or deleted it. A real open also triggers READ, so the email may now be in another folder or in Deleted Items.

</details>

<details>

<summary>My recipient opened and read an email. Why does the delivery report not reflect READ?</summary>

To track READ status of an email, a hidden tracking image is loaded into each email sent. However, some government and corporate mail servers might block this image from loading, preventing our email provider from detecting that an email has been read.

</details>

#### `errorCode`

Read below for the various errorCodes you may see in your delivery report, what each of them mean, and the recommended action.

<details>

<summary>Blacklisted</summary>

<table><thead><tr><th width="323.203125">Description</th><th>Recommended Action</th></tr></thead><tbody><tr><td>We have added this email address to Postman's blacklist given that the email hard bounced. Email will not be delivered as it is unlikely to exist.<br><br>You may have sent emails to this email address before and it hard bounced then.</td><td><p>Please remove this email address from your contact list as it is most likely to be invalid. </p><p></p><p>If you have verified that this email address is valid and is blacklisted mistakenly, please contact us <a href="https://form.gov.sg/68947817cc63b1edce1d52f6">here</a>.</p></td></tr></tbody></table>

</details>

<details>

<summary>Hard Bounce</summary>

{% hint style="warning" %}
Too many hard bounces can cause your campaign to halt. Read more [here](https://postman-v1.guides.gov.sg/campaign-guide-email/email/halting-of-email-campaigns).
{% endhint %}

<table><thead><tr><th width="227.52734375">Description</th><th>Recommended Action</th></tr></thead><tbody><tr><td>The email recipient is not valid and might not exist. We will add this email to our blacklist for future campaigns and emails to this recipient will not be sent for future campaigns.</td><td><p>Please remove this email address from your contact list as it is most likely to be invalid. </p><p></p><p><strong>Note</strong>: Email distribution lists (i.e. group email addresses) will also be hard bounced. Please use individual email addresses in the CSV recipient list.</p></td></tr><tr><td>The email has been delivered, but the recipient marked it as spam. We do not add this email to the blacklist.</td><td><ul><li>Depending on the content of your campaign, we suggest respecting recipients' wishes to mark the email as spam, as repeated spam reports can affect Postman Legacy's reputation score. </li><li>If it is deemed necessary to continue sending, we suggest sending out separate communications to them to inform them not to mark the email as spam.</li></ul></td></tr></tbody></table>

{% hint style="info" %}
**My recipient's email address is valid and can receive other emails. Why does it still hard bounce?**

* The recipient's mail server could be blocking Postman Legacy's sending IP or email address. This rejection looks the same as “user not found", hence marking the email as invalid.
* Ask the recipient's IT team to whitelist Postman Legacy's sending IP address and add `info@mail.postman.gov.sg` to their safe senders list.
  {% endhint %}

</details>

<details>

<summary>Soft Bounce</summary>

<table><thead><tr><th width="285.7578125">Description</th><th>Recommended Action</th></tr></thead><tbody><tr><td>The email inbox might be full or the person might have an out-of-office message.</td><td>Resend later, or ask recipient to clear their inbox.</td></tr></tbody></table>

</details>

<details>

<summary>Error</summary>

<table><thead><tr><th width="285.7578125">Description</th><th>Recommended Action</th></tr></thead><tbody><tr><td>Incorrect email formatting.</td><td>Check for typo, space, and symbols in the recipient field and amend the email address.</td></tr></tbody></table>

</details>

<details>

<summary>Unsubscribed</summary>

<table><thead><tr><th width="285.7578125">Description</th><th>Recommended Action</th></tr></thead><tbody><tr><td>The recipient clicked the unsubscribe link in the email.</td><td><ul><li>Depending on the content of your campaign, we suggest respecting recipients' wishes to unsubscribe, as not doing so may lead to spam reports that can affect Postman Legacy's reputation score. </li><li>If it is deemed necessary to continue sending, we suggest sending out separate communications to them to inform them not to unsubscribe, or why you are continuing the end emails to them in spite of their unsubscription.</li></ul></td></tr></tbody></table>

</details>

#### `updatedAt`

The `updatedAt` column shows the date and time of the most recent status update for each recipient.

For example, a report could be exported once when a message was delivered successfully and unopened and again later only after it was opened.

* In the first report, `updatedAt` would show the estimated time when it was delivered, and then the estimated time it was opened (in the later exported report).&#x20;
* In the second report, `updatedAt` would show the estimated time it was opened.

Delivery statuses can keep changing after sending. This means that if you want to see the most updated activity of your email, you will need to re-download the delivery report.

<details>

<summary>Why doesn't the <code>updatedAt</code> timestamp correspond with the time the email arrived in my recipient's inbox?</summary>

* Postman Legacy only send emails to AWS SES (our email provider) and not to the recipients' inboxes directly. Hence, we are only able to see the AWS SES event callbacks.
* AWS SES reports `SUCCESS` when the recipient’s mail server accepts the email. That server may then scan, filter or hold the email before the inbox shows it. Government and corporate servers often do this, so the inbox time seen by recipients can be later than `updatedAt`.

</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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://postman-v1.guides.gov.sg/campaign-guide-email/email/statistics.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.
