> 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/guides/contacts-lists/clean-up-contacts.md).

# How to clean up your contacts

How to find contacts that are no longer relevant, such as undeliverable contacts, contacts who withdrew consent, contacts you haven't used in a year and unengaged contacts, and how to remove them.

This guide shows how to find contacts that are no longer relevant for your account, so you can remove them.

Cleaning up regularly keeps your contact count within your plan. It also helps you follow [GDPR](https://support.emarketeer.com/references/references/emarketeer-gdpr-overview.md), which says you shouldn't keep personal data for longer than you need it. And a tidy contact database is easier to work with.

## Find contacts with the filter builder

All the examples below use the filter builder. Click **Contacts** in the left sidebar, then click **Filter** above the contact list. To learn how the filter builder works, see [How to build and use Contact Filters](https://support.emarketeer.com/guides/contacts-lists/how-to-build-contact-filters.md).

Click **Save As Segment** to save a filter you want to run again, so the clean-up becomes a routine.

## Undeliverable contacts

Undeliverable contacts are contacts whose email delivery has failed. To find them, add a **Delivery** condition with **E-mail** **Equals** **Undeliverable**.

<div align="left" data-with-frame="true"><img src="https://2894606528-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0ywqCs3au1x0DqPhEJTR%2Fuploads%2Fgit-blob-b6e64536387d68698dc8bf2fe7b40a81a9e08fa7%2Fclean-up-contacts-undeliverable-condition.png?alt=media" alt="Add condition dialog for Delivery with Field E-mail, Condition Equals and Value Undeliverable"></div>

They are safe to remove, because eMarketeer already excludes them from sendouts. See [Email bounce handling](https://support.emarketeer.com/references/references/email/deliverability/bounce-handling.md).

eMarketeer remembers that an address is undeliverable. If you delete the contact and add it again, it's still flagged as undeliverable.

{% hint style="info" %}
A few undeliverable contacts can be false positives. Rather than keeping all of them, make a routine of checking the bounces after each sendout for anything unexpected.
{% endhint %}

## Contacts who withdrew consent

These contacts have opted out of marketing emails. To find them, add two **Consent** conditions: **Legal Basis** is **Withdrawn**, and **Purpose** is **Marketing sendouts**.

<div align="left" data-with-frame="true"><img src="https://2894606528-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0ywqCs3au1x0DqPhEJTR%2Fuploads%2Fgit-blob-b3f43bf31be93359b0526f1dd4b9d45d2e6b944c%2Fclean-up-contacts-consent-withdrawn-filter.png?alt=media" alt="Filter contacts dialog with the conditions Legal Basis Is Withdrawn and Purpose Is Marketing sendouts"></div>

They are excluded from sendouts automatically and are safe to remove. eMarketeer keeps their consent history, so if you import them again, it still knows they withdrew consent and won't send them marketing emails.

## Contacts you haven't used in a year

Every contact has a **Last Email Sent** date, which is set each time an email is sent to the contact. Use it to find contacts you haven't emailed in a full year:

1. Add a **Dates** condition: **Last Email Sent**, **Days Passed (or more)**, **365**.
2. Add an **Engagement** condition: **Any form**, **Not Submitted**, at least 1 time, last 365 days. This keeps contacts who have submitted a form during the year.

<div align="left" data-with-frame="true"><img src="https://2894606528-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0ywqCs3au1x0DqPhEJTR%2Fuploads%2Fgit-blob-9db02bee1f41aa5759f71b11cb027aab4c032c98%2Fclean-up-contacts-unused-filter.png?alt=media" alt="Filter contacts dialog with the conditions Last Email Sent Days Passed (or more) 365 and Any form Not Submitted in the last 365 days"></div>

The result is contacts that exist in eMarketeer but that you haven't emailed, and that haven't submitted any forms, for a year. If you have good [lead scoring](https://support.emarketeer.com/guides/lead-board-scoring/how-lead-scoring-works-in-emarketeer.md) rules, you can use a **Score** condition in the same way.

## Deliverable but unengaged contacts

These contacts can receive your emails, but they don't open them or click any links. To find them, add a **Delivery** condition with **E-mail** **Equals** **Deliverable but unengaged**.

<div align="left" data-with-frame="true"><img src="https://2894606528-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0ywqCs3au1x0DqPhEJTR%2Fuploads%2Fgit-blob-df3069f6d3f4e6e5678c908c19e55ac1aad42620%2Fclean-up-contacts-unengaged-filter.png?alt=media" alt="Filter condition E-mail Equals Deliverable but unengaged"></div>

They may be worth removing, but consider giving them a chance first with a re-engagement [Journey](https://support.emarketeer.com/guides/journeys.md). To read more about unengaged contacts, see [Exclude inactive recipients](https://support.emarketeer.com/references/references/email/exclude-inactive-recipients.md).

## Remove the contacts

When the filter shows the contacts you want to remove, select them and choose **Bulk actions** › **Permanently delete contacts**. See [How to manage contacts in bulk](https://support.emarketeer.com/guides/contacts-lists/bulk-actions-tool.md).

{% hint style="warning" %}
Deleted contacts can't be restored from within eMarketeer. If you might need their data later, click **Export** to save a copy before you delete them.
{% endhint %}

Deleting contacts doesn't change the counters or metrics in your reports, but the deleted contacts no longer show in them. See [What happens to reports when I delete a contact?](https://support.emarketeer.com/references/faq.md#what-happens-to-reports-when-i-delete-a-contact).


---

# 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://support.emarketeer.com/guides/contacts-lists/clean-up-contacts.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.
