> For the complete documentation index, see [llms.txt](https://support.emarketeer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.emarketeer.com/references/references/email/checklist-explained.md).

# Understanding the Email Checklist

You see this page when sending an email. Review it to confirm your sendout reaches the right audience and to understand any exclusions.

<div align="left" data-with-frame="true"><img src="/files/Fc38er2S8AljtpbhxRVF" alt="Screenshot of the email checklist content"></div>

## Checklist categories

**Addressed email by you**\
This is the total number of contacts included in the recipient lists used for this sendout.

**Duplicates**\
The number of duplicate email addresses found. Usually only relevant when you use more than one recipient list.

**Unsubscribed**\
The number of intended recipients unsubscribed from the subscription list used to categorize this email. Only relevant when you use such a list.

**Consent Withdrawn**\
The number of contacts who have revoked their consent to receive sendouts from you. The specific consent setting is the contact's Marketing Consent. [This article](/references/references/emarketeer-gdpr-overview/how-does-consent-work.md) explains consent in more detail.

**Undeliverable Email Addresses**\
The number of contacts whose email addresses have previously reported they cannot receive email. [This article](/references/references/email/deliverability/bounce-handling.md) explains how eMarketeer handles bounces.

**Deliverable but Unengaged**\
The number of contacts that can receive email but have not read your messages or had any registered activity for a long period. You choose whether to send to these contacts in Step 2 of the email sendout, via the Exclude Inactive Recipients setting. [This article](/references/references/email/exclude-inactive-recipients.md) explains Exclude Inactive Recipients.

**Emails with Blocked Domains**\
If your account blocks specific domains for sendouts, any contacts on those domains in your recipient lists are counted here.

**Blocked Contacts**\
If a setting on your sendout dynamically blocks some contacts, they are counted here. Examples include "Exclude contacts that have already been sent this email" or actively blocking a recipient source, such as when sending reminder emails as described in [this guide](/guides/guides/email-content/configuring-reminder-email.md).

**Invalid Sender Email Address**\
Recipients fall under this category when the sender email address for this email component is invalid. This can be because of an invalid email domain or an incorrectly formatted address. Fix it on the email's editing page by updating the sender email in the left-side menu.

**Missing Required Double Opt-In**\
The number of contacts in the recipient list that have not completed the double opt-in process, in cases where double opt-in is required before a contact can receive email from your account.

**Emails that will be addressed**\
The number of contacts that will be addressed by this sendout after exclusions.

**Email that will not be addressed**\
The total number of contacts that will not be addressed by this sendout.


---

# 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:

```
GET https://support.emarketeer.com/references/references/email/checklist-explained.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
