Omnisend unsubscribes hard bounces from your list automatically, so it reacts quickly once an address fails. What it can't do is judge an address it has never sent to — the imports, old signups, and typos that sit in your account as subscribed or non-subscribed contacts, counting toward your bill, until the first campaign proves them dead. This guide covers what Omnisend does for you, the addresses it can't see, and the export → verify → act loop that handles the rest.
What Omnisend already does for you#
Omnisend's native hygiene works through automatic status changes:
- Hard bounces are unsubscribed automatically. When an address is undeliverable, Omnisend marks it as bounced — one of its automatic unsubscribe reasons — so it drops out of future sends.
- Soft bounces escalate. An address that keeps soft-bouncing is suppressed after repeated failed attempts.
- Non-subscribed contacts are left alone. Omnisend distinguishes unsubscribed (actively opted out) from non-subscribed (never opted in), and it does not automatically remove or suppress non-subscribed contacts — which matters for your bill, below.
Omnisend behavior above last verified against the Omnisend help center, July 2026.
For addresses Omnisend has mailed, this is dependable automatic hygiene. The gap is the addresses it hasn't mailed — and in Omnisend those often sit as non-subscribed contacts that quietly count toward your plan.
What Omnisend can't catch#
Every mechanism above needs a send and a failure to fire, leaving the blind spot every ESP shares:
- Never-mailed invalid addresses. Contacts imported from another platform, old signups, and typos captured at capture have never bounced because they have never been sent to. Omnisend has no signal on them until your first campaign.
- Disposable addresses accepted at signup that will quietly stop existing.
- Role addresses (
info@,support@) that skew engagement metrics. - Decayed addresses that look healthy today and will bounce next month.
An imported list is the sharpest case: it arrives with its bounce history stripped, so addresses that were already failing elsewhere look brand new — and count toward your billable total from day one. Verify before the import, not after the first send. Even a spotless list still lands in spam if the domain behind it isn't trusted, so authenticate your Omnisend sending domain with SPF, DKIM, and DMARC as the other half of deliverability.
Step-by-step: export, verify, act#
Direct ESP connections are paused while we rebuild our integrations platform (see integrations), so the dependable path today is the CSV loop — the same flow as the Klaviyo and Mailchimp guides, in Omnisend's terms:
- Export from Omnisend. Open Audience, filter to the segment you want to clean, and export it to CSV.
- Verify the file. Upload it to Qualisend bulk cleaning — up to 1,000,000 addresses, duplicates charged once — or paste addresses directly. The free plan's 100 credits cover a first sample.
- Read the results. Every address returns
deliverable,risky,undeliverable, orunknownwith a reason code and sub-flags (catch-all, disposable, role, full mailbox), plus the MX provider and probe detail as evidence. Download the cleaned CSV. - Retire the undeliverables in Omnisend. Filter your results to
undeliverable, then either unsubscribe those contacts — which stops sends and removes them from your billable count, since unsubscribed contacts are the one status Omnisend doesn't bill for — or delete them. - Handle everything else per verdict — the table below.
What to do with each verdict#
| Verdict | Omnisend action |
|---|---|
deliverable | Keep sending as normal. |
deliverable + role flag | Keep for transactional content; exclude from engagement-judged automations — see role, disposable & free. |
risky + catch-all flag | Move to a dedicated segment and throttle — see the catch-all guide. |
risky + disposable flag | Unsubscribe or delete. The inbox was built to expire. |
unknown | Keep and re-verify next clean — greylisting or rate-limiting, not a verdict on the mailbox. |
undeliverable | Unsubscribe or delete. Don't wait for the bounce to prove it. |
Subscribed, non-subscribed, unsubscribed — and the bill#
This is the Omnisend-specific detail that makes cleaning worth it. Omnisend counts your billable contacts on each billing day as your subscribed plus non-subscribed contacts — non-subscribed count because they can still receive transactional automations like order confirmations. The only status excluded from billing is unsubscribed. So a dead never-mailed address imported as a non-subscribed contact is costing you money every billing cycle until you act on it. Moving your verified undeliverables to unsubscribed (or deleting them) is what takes them off the count — automatic bounce handling only reaches the addresses you have already mailed.
How often to re-clean#
There is no universal number, and we won't invent a decay statistic. The real drivers are how fast your list grows and how it is sourced: a double-opt-in list decays slowly, while one fed by imports and pop-ups accumulates junk continuously. Three habits cover most senders:
- Before any high-stakes send — a launch or seasonal campaign.
- After any import, before the first send touches it — and before those contacts start counting toward your plan.
- On a regular cycle sized to your volume, with your per-campaign bounce rate as the tripwire. If bounces climb toward the warning thresholds, clean now (see why bounce rate matters).
Frequently asked questions#
Does cleaning my list lower my Omnisend bill?#
It can. Omnisend counts your subscribed and non-subscribed contacts on your billing day, and only unsubscribed contacts are excluded — so dead never-mailed addresses sitting as non-subscribed contacts are billable until you act. Moving your verified undeliverables to unsubscribed, or deleting them, is what reduces the count; automatic bounce handling only touches addresses you have already sent to.
What's the difference between non-subscribed and unsubscribed in Omnisend?#
Non-subscribed contacts never opted in but can still receive transactional automations, so Omnisend keeps them and bills for them. Unsubscribed contacts actively opted out, are excluded from sends, and are the one status not counted toward your bill. For cleaning purposes, unsubscribed is the "retired" state.
Can I verify addresses before they enter Omnisend?#
Yes, and it is the highest-leverage option: verifying at signup through the API keeps typos and disposable addresses out of Omnisend entirely, so they never become billable contacts. A native Omnisend integration is part of the platform we're rebuilding; until it ships, the CSV loop above is the supported path.
