> For the complete documentation index, see [llms.txt](https://docs.talkfurther.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.talkfurther.com/products/web-data/email-suppression-and-bounce-lists.md).
# Email Suppression and Bounce Lists
### Product explanation and use case
Further’s **Email Suppression List** and **Email Bounce List** work together to protect your sender reputation, keep you compliant, and give you clear visibility into email delivery issues.
They’re designed for operators and marketing teams who:
* Send high‑volume email campaigns through Further’s Marketing Automation Platform (MAP)
* Need to respect opt‑outs and spam complaints automatically
* Want to quickly understand why specific emails bounced and what to fix next
***
### What it is / what it does
#### Email Suppression List
The **Email Suppression List** is a **global, system-level list of email addresses that must never receive email from your organization through Further.**
An email address is automatically added to the suppression list when it:
* **Opts out** of email communication
* Returns a **hard bounce** (invalid / non‑existent address)
* Is tied to a **spam complaint**
* Is **manually added** to the suppression list via an upload
Once suppressed:
* That email address is **blocked from all future sends**, across all communities and campaigns
* Any lead using that email is treated as **non‑emailable**
* Lead profiles clearly show that the email is suppressed
* Every suppression / unsuppression action is **logged for auditing**
#### Email Bounce List
The **Email Bounce List** is a **report of every email address that bounced when you sent a campaign message.**
For each bounce, you can see:
* **Email address** that bounced
* **Campaign email** that triggered the bounce
* **Date and time** the bounce occurred
* **Bounce type** – **Hard** or **Soft**
* **Bounce classification**, including:
* Content
* Frequency or volume too high
* Invalid address
* Mailbox unavailable
* Reputation
* Technical
* Unclassified
You can:
* **Filter** by bounce type, classification, campaign, and more
* **Export** the list as CSV for analysis, list cleanup, or sharing with agencies and IT teams
***
### What problem it solves (customer resonance)
Without strong suppression and bounce controls, teams run into issues like:
* **High hard‑bounce rates** from old or invalid lists
* **Spam complaints** from people who already opted out or don’t recognize your emails
* **Blocked or throttled sending** from providers like Microsoft due to reputation problems
* **Legal and compliance risk** when opt‑outs aren’t reliably honored across tools
In senior living specifically, this shows up as:
* Families getting unwanted emails even after asking to stop
* Agencies or operators hesitant to migrate lists because they don’t trust that suppression will be handled safely
* Good campaigns underperforming because deliverability quietly degraded in the background
The suppression and bounce lists solve this by:
* **Automatically blocking risky or non‑permitted sends** before they go out
* **Centralizing deliverability issues** in one place so you can investigate and act
* Making it easy to **import external opt‑out/suppression lists** when moving from tools like Constant Contact or Mailchimp
***
### Value propositions (why we built it)
1. **Protect sender reputation and inbox placement**
* Prevents emails from going to invalid, opted‑out, or spam‑complaining addresses
* Reduces hard‑bounces and spam complaints that can get your IP blocked or throttled
2. **Single source of truth for “do not email”**
* Suppression is **tied to the email address**, not a single lead record, and applies **globally** across your organization
* Deleting a lead in your CRM **does not** re‑activate a suppressed email
3. **Compliance and trust for opt‑outs**
* Opt‑outs, hard bounces, and spam complaints flow into a central suppression system with **no extra work from your team**
* Every change is auditable so you can show what happened and when
4. **Operational visibility for marketers and CSMs**
* Bounce List gives a concrete **lead‑level view** of delivery problems instead of a single bounce percentage
* Filters and CSV export make it easy to clean lists, coach agencies, or debug a specific campaign
5. **Safer migrations from legacy tools**
* You can upload historical suppression/opt‑out lists so that moving from tools like ActiveDemand or Constant Contact doesn’t mean starting from scratch or risking over‑sending
***
### How it fits in the Further ecosystem
These features sit in the core of **Further’s Marketing Automation Platform** and touch:
* **Campaigns:** Every time a campaign is about to enroll leads into an email step, Further checks the suppression list. Suppressed addresses are **never enrolled**, even if they match the campaign criteria.
* **Lead Profiles:** Suppression status and reason are surfaced on the lead so sales, marketing, and operations teams can see why a person isn’t receiving emails.
* **CRM Integrations:** Because suppression is tied to the email address and lives in Further, it continues to work even as CRM records change, merge, or are deleted.
* **Reporting & Analytics:** Bounce patterns you see in the Bounce List can be tied back to campaigns and templates you measure in Messaging Analytics, helping you connect content and cadence decisions to real delivery outcomes.
***
### How do you set it up
#### 1. Check access
To manage suppression and bounce lists, you’ll typically need:
* Access to **Further MAP**
* An admin or marketing role with permission to manage **Settings → Marketing**
If you don’t see the menus below, ask your internal admin or CSM to confirm your permissions.
***
#### 2. Working with the Email Suppression List
**Navigation**
1. In Further, go to **Settings → Marketing → Email Suppression List**.
**What you’ll see**
The list view shows, for each suppressed email address:
* Email address
* Suppression reason (e.g., opt‑out, hard bounce, spam complaint, manual)
* Date suppressed
**How addresses get added**
Most addresses will be added **automatically** when:
* A contact clicks an **unsubscribe/opt‑out** link
* An email returns a **hard bounce** (invalid address)
* A **spam complaint** is reported by the email provider
You can also **manually add** addresses (for example, to honor an off‑platform legal request or a list from Constant Contact that couldn’t be synced via CRM) by:
1. Clicking the **Add / Upload** option in the suppression list
2. Entering individual addresses or uploading a CSV of email addresses to suppress
Once added, those emails are immediately blocked from future sends across all campaigns and communities.
Manual Upload of Individual Addresses
Bulk Upload of Suppression Lists
**How to remove (unsuppress) an address**
* Only **admin users** can remove addresses from the suppression list.
* In v1, you can only unsuppress addresses that were **manually** added; system‑generated suppressions (hard bounces, spam complaints, opt‑outs) remain blocked for safety.
When you unsuppress a manually suppressed email:
* The suppression record is **soft‑deleted** (kept for history)
* The system records **who** unsuppressed it and **when**
* Any leads with that email become **emailable again**
> **Best practice:** Only unsuppress an address if you’re confident the prior suppression was added in error and you have explicit permission to email that contact again.
***
#### 3. Using the Email Bounce List
**Navigation**
1. In Further, go to **Settings → Marketing → Email Bounce List**.
**What you’ll see**
For each bounced message, you’ll see:
* Email address
* Campaign email that triggered the bounce
* Date and time
* Bounce type (**Hard** or **Soft**)
* Bounce classification, such as Content, Frequency/volume too high, Invalid address, Mailbox unavailable, Reputation, Technical, or Unclassified
**How to work with the list**
* Use filters to focus on:
* **Hard bounces** (good candidates to remove from your CRM or marketing lists)
* Specific **campaigns** you’re troubleshooting
* Specific **classifications** (e.g., lots of “Content” or “Reputation” issues)
* **Export to CSV** to:
* Clean up lists in your CRM
* Share with agencies or IT for deeper analysis
* Keep internal records for compliance and QA
You don’t need to “turn on” the Bounce List; it activates automatically once you start sending campaigns.
***
### FAQs
**1. What’s the difference between the Suppression List and the Bounce List?**
* The **Email Suppression List** is a **rule**: addresses on it **cannot** receive email from Further until they are (in rare cases) unsuppressed. It’s the source of truth for **“never email this address.”**
* The **Email Bounce List** is a **log/report**: it shows **what happened** when you tried to send emails (which addresses bounced, when, and why). You use it to **investigate and clean up**, not to enforce sending rules directly.
***
**2. Does deleting a lead in my CRM remove their suppression?**
No. Suppression is tied to the **email address**, not the lead record. Deleting a lead **does not** remove its email from the suppression list, and that address will remain blocked until (if eligible) manually unsuppressed by an admin.
***
**3. Can I re‑activate an email that hard bounced?**
In general, **no**:
* Hard bounces usually indicate that the address **does not exist**, and SendGrid treats them as invalid and adds them to its own suppression list.
* Even if you unsuppressed it in Further, the email may still fail at the ESP level.
Only consider re‑activating if you’ve **confirmed with the contact and IT** that the address was valid and the bounce was caused by a temporary configuration issue.
***
**4. Can I upload a suppression list from another platform (e.g., Constant Contact)?**
Yes. If you have a historical opt‑out or suppression list that couldn’t be cleanly synced through your CRM, you can upload those emails directly into the **Email Suppression List** so they’re automatically excluded from all future campaigns.
This is especially helpful when migrating from legacy email tools where opt‑out status is stored outside your CRM.
***
**5. Does suppression apply per campaign, per community, or globally?**
Suppression applies **globally across your organization**:
* If an email address is on the suppression list, it will **not receive email from any campaign, for any community**, regardless of campaign‑level targeting.
***
**6. How do these tools help with deliverability issues like Microsoft blocking IPs?**
When deliverability issues happen (e.g., a provider temporarily blocks an IP due to reputation concerns), they’re often driven by:
* High **hard‑bounce rates**
* **Spam complaints**
* Large sends to old or unclean lists
The suppression and bounce lists help you:
* **Prevent future damage** by automatically blocking high‑risk addresses
* **Identify and clean** problematic data sources quickly
* Keep a healthier sending posture so incidents are less likely and easier to resolve with providers like Microsoft and SendGrid.
---
# 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://docs.talkfurther.com/products/web-data/email-suppression-and-bounce-lists.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.