Bounces
A bounce is the receiving server refusing the message. There are two kinds and they are treated very differently.Hard bounce (permanent)
The address does not exist, or the domain does not. It will never work, and retrying it damages your reputation. Three things happen at once:- The message is marked bounced.
- The address is blocked platform-wide, so no sender in any organization mails it again.
- The list contact is marked
bounced, so it disappears from the sendable set of every list it is on.
Soft bounce (transient)
The mailbox was full, the server was busy, the message was greylisted. The message is marked deferred. Nothing is blocked on the first one, because a transient failure is usually exactly that. After three soft bounces in a row from the same sender, the address is blocked for your organization and that sender. In a row means three separate sends from that sender, one after another, with no delivery to that address in between; a single delivery resets the count, and sends from your other senders are not part of it. Three transient failures like that is no longer a busy server; it is an address that does not accept your mail. Bounces caused by the message itself, such as one rejected for its content or size, and temporary rate limiting by the receiving provider, do not count toward the three and do not interrupt them: they say something about the message or about your sending pace, not about the address. The block is not platform-wide, because unlike a hard bounce this is a fact about the relationship, not the address. A deferral is never charged a second time. The send was already billed when it went out.Complaints
A complaint is a recipient pressing “report spam”. It is the single most expensive event in email, and it is treated accordingly: the address is blocked at three scopes at once, for the sender identity, for your organization, and platform-wide. That is deliberately heavier than an unsubscribe. Someone who unsubscribes is telling you they do not want this mail. Someone who reports spam is telling Gmail you should not be sending mail at all, and the only correct response is to make certain it cannot happen again from anywhere. The list contact is markedcomplained and is never sent to again.
Unsubscribes
There are three ways a recipient can opt out, and all three work on every message you send:
The default scope is the sender identity, since that is the relationship the
recipient acted on. The hosted page is where they can widen it to the whole
sending domain if what they want is to hear from nobody on it. Organization-wide
unsubscribes are yours to write (a do-not-contact upload, an address added by
hand, or the API), never a recipient’s choice.
Resubscribing. A recipient who left one sender can come back from the same
page. That lifts the sender unsubscribe and puts them back on every list of
yours they had unsubscribed from, so the next campaign reaches them again.
Rows that left for another reason (a bounce, a complaint, an invalid address)
stay removed, and an organization-wide opt-out is not undone by a sender
resubscribe.
Unsubscribes are honored synchronously. There is no batch window in which a
recipient who just opted out can still receive a queued message. A provider
retrying a one-click request does not produce a second unsubscribe event either;
a recipient unsubscribes from one send exactly once.
When these records are applied
Twice, on purpose:- When the campaign’s audience is compiled. Unsubscribed, bounced, and complained addresses are removed before the recipient count you see is calculated, which is why the number in the builder is often lower than the list total.
- Again at send time, per message. A campaign that was compiled an hour ago and is still sending re-checks each address as it goes.
Where an unsubscribe applies
Unsubscribes and blocks live at three scopes and you can manage them yourself:
All three apply automatically. There is nothing to attach to a campaign and so
nothing to forget. Writes are bulk, up to 5,000 addresses per call, malformed
addresses come back in an
invalid array rather than failing the batch, and
lifting an entry that was never set is not an error. Over the API these records
are read and written at /v1/email/suppressions.
Uploading a do-not-contact file
To load your own do-not-contact file, go to Assets > File Uploads, drop the file, and choose Do not contact on the setup card. Choose the email column and whether it applies to the whole organization or to one sending domain, and every campaign in that scope skips those addresses from then on. A file that also has a phone column adds those numbers to an opt-out list at the same time. The emails are applied in the background, which takes minutes for a large file; they then show under Assets > Lists > Do not contact > Unsubscribes and bounces. Applying them also marks those people unsubscribed on your lists, so the counts you see are the counts that will actually send. To add a few addresses by hand, use Add addresses on the same page.Holding out a list from one campaign
To exclude a set of people from a single campaign without unsubscribing them everywhere, choose an ordinary list under Suppression lists on the campaign. Any list can be used this way, exactly as a texting project holds out a list: both pickers on the campaign read from the same set of lists, and the campaign decides which are the audience and which are held out. A suppression tag does the same for everyone carrying a tag. Both are a choice for that one campaign: unsubscribes and bounces always apply, and neither a suppression list nor a suppression tag lifts or creates one. See Tags.Downloading your unsubscribes and bounces
Use Download CSV under Assets > Lists > Do not contact > Unsubscribes and bounces. The file lists every entry for your organization, with its reason, scope, sender or domain, and date, so your own system of record can be reconciled against what the platform is actually blocking. Platform-wide entries, such as hard bounces, are not included.Why removing a contact does not delete it
Removing an address from a list unsubscribes it rather than deleting the row, and that surprises people often enough to be worth explaining. The row is what carries the bounce and complaint history. Delete it, re-import the same file six weeks later, and you have resurrected an address that already complained, and you will mail it again. Keeping the row is the entire mechanism that keeps an address unmailed across imports. To erase an address completely, use forget this address, which is a deliberately heavier and irreversible operation for genuine deletion requests.The sunset policy
Mailing people who never open anything is the fastest way to lose a sending reputation, because that is precisely the pattern mailbox providers use to identify senders who are not paying attention. The sunset policy handles it, per list, controlled bysunset_enabled:
Engagement is recorded on every list your organization has that contact on.
Opens seen through Gmail’s and Yahoo’s image proxies count as activity, because
those proxies load the image when the person opens the message, even though
they are not counted as opens in your reports. Other automated opens, such as
Apple’s mail privacy proxy and security scanners, do not count, and neither do
automated clicks.
Contacts added in the last 90 days are never held: someone who has not had the
chance to engage yet is not an unengaged contact.
Winning people back before the drop
The window between the hold and the drop is your chance to recover the people worth recovering. There is a re-permission starter template for exactly this: one short message asking whether they still want to hear from you. A campaign marked as a re-permission send is the one case that is allowed to reach held contacts, and it also ignores the frequency cap, because a message asking permission is worthless if the policy protecting you from over-mailing prevents it from arriving. Keep it plain, keep it short, and make the “yes, keep me” action a click, since a click is what resets engagement. Everyone who ignores it was going to cost you deliverability anyway. Letting them sunset is the right outcome, not a failure.Rate alarms
Two thresholds pause a campaign automatically, well below the point at which the sending infrastructure would intervene:
The complaint rate divides by messages to providers that report complaints;
Gmail reports none, so Gmail sends are left out, the same way the sending
account is measured. Neither is judged until at least 500 messages have been sent, and a
complaint pause also needs at least 3 complaints, so a handful of early
bounces or a single spam click on a small send cannot trip them. See
Campaigns and deliverability
for what happens when one trips and how to resume.
Separately, if our sending infrastructure disables one of your sender
identities, every in-flight campaign on that identity is paused
automatically and your organization is notified, rather than the sends failing
message by message. See
Sender identities.
