Will cleaning my list lower my Bloomreach bill?

It can, but the mechanism matters. Engagement's usage fee is driven by billable profiles, and a profile is billable the moment it carries an email, phone, or hard ID. Adding an address to the custom suppression list (or flagging it email_invalid) stops the mail but keeps the email, so the profile stays billable — only anonymizing or deleting the customer strips the identifier and takes it off the count. Verifying before an import is what keeps junk from ever becoming a billable profile in the first place.

What's the difference between the custom suppression list and deleting a customer?

The custom suppression list (CSL) blocks sending to an address or domain but keeps the profile and its email — it's good for a modest blocklist, but it caps at 5,000 entries and won't reduce billing. For a large undeliverable set, import the verdict back as a customer property, segment on it, and exclude that segment from your campaigns; anonymize or delete the customers when you also want to drop them off your billable profile count. Note the CSL never blocks transactional or general-consent email by design.

Won't Bloomreach's bounce handling and managed suppression list catch bad addresses for me?

Only after the fact. Bounce handling flags an address email_invalid once it has failed on a real send, and the Bloomreach-managed list blocks obvious known-bad and spam-trap domains. Neither can catch a never-messaged invalid on a real domain, a disposable address, a role address, or a catch-all before the first message — those only surface once you've already spent the send and taken the reputation hit, which is exactly what verifying first avoids.

Can I verify addresses before they enter Bloomreach?

Yes — it's the highest-leverage option, because Engagement creates a profile the moment an email lands via a customer update or import. Verify at the point of capture through the REST API (or a Zapier/Make/n8n flow) so typos and disposable addresses never enter Bloomreach and never become billable profiles.

Native connector returning — CSV & API work today

Keep your Bloomreach audience clean before the campaign fires

Q: Does Qualisend have a native Bloomreach integration?

A native one-click connector is being rebuilt as part of our platform upgrade and will return. Today the supported path is the export loop — export from the Customers UI, the Data Exports feature, or the customer-export API, verify in Qualisend, then suppress or anonymize the dead addresses — or verifying at the point of capture through the REST API. Both work with any Bloomreach Engagement plan.

Bloomreach Engagement auto-suppresses addresses that hard-bounce or keep soft-bouncing — it flags them email_invalid and holds them out of every future campaign — and its Bloomreach-managed global list blocks known-bad and spam-trap domains at the door. But it can't judge an address it has never messaged, and on a CDP that bills by billable profile every never-messaged invalid is both a deliverability risk and a line on your usage bill. Qualisend closes that gap: export your audience, verify every address, and suppress or anonymize the dead ones before your next campaign fires. Here's the workflow that works today, plus the API and no-code options.

Clean a list for free

One-click Bloomreach sync is paused while we rebuild the platform

We've deliberately paused our one-click native connectors while we re-engineer the sync layer they run on — hardening how we authenticate, respect each platform's rate limits, and write results back — so that when the native Bloomreach integration returns, it stays dependable at any list size rather than fragile at scale. None of this touches how Qualisend verifies an address.

Everything you need works today: the CSV export → verify → reimport loop below, and the API for verifying at signup, are both fully supported and running in production — that's how teams keep Bloomreach clean right now.

Bloomreach handles

What Bloomreach cleans for you

Bloomreach's native hygiene collects failure feedback from mailbox providers and sorts it into soft and hard bounces. On a hard bounce — or a preblocked status, or enough cumulative soft bounces — Engagement doesn't delete the contact; it sets the customer's email_invalid attribute to true, which excludes that profile from every future email campaign. By default, three consecutive soft bounces temporarily suppress an address for 14 days to ride out a transient inbox problem; those defaults are visible under Campaigns > Channels > Emails and adjustable via Bloomreach support. On top of bounce handling, Engagement runs a project-wide email list hygiene filter that can automatically exclude customers who haven't engaged in 180+ days or who recently soft-bounced, plus two suppression lists: a Bloomreach-managed global list (GSL) that blocks known-bad, invalid, and spam-trap domains, and a custom suppression list (CSL) you edit yourself under Project settings > Campaigns > Channels > Emails, which blocks by address or domain up to a cap of 5,000 entries. A deliverability dashboard and hard/soft bounce-reason reports show you the aftermath. For addresses Bloomreach has actually messaged, that's reliable, automatic hygiene.

The gap it leaves

What it can't catch

The catch is that bounce handling is reactive — it needs a send and a failure to fire — and the managed list only catches obvious known-bad and spam-trap domains. A valid-looking but dead mailbox on a real domain, a full mailbox, a disposable address, a role address like info@ or support@, and a catch-all domain all pass straight through until an event triggers the first message, which is exactly when a mailbox provider forms its first impression of your domain. Engagement makes the blind spot sharper because it's event-driven: a profile is created the moment your app fires a customer update or you import an audience, so those dead profiles don't sit quietly — they keep entering broadcasts and scenarios whenever an event matches, and a bad address gets messaged again and again. An imported audience is the sharpest case: it arrives with its bounce history stripped, so addresses that were already failing on your old tool look brand new to Bloomreach.

Why a clean Bloomreach list matters

On Bloomreach the stakes are double, because Engagement prices on a module fee plus a usage fee, and the usage tier is driven by billable profiles (alongside monthly unique visitors) — and a profile becomes billable the moment it carries an email, phone, or hard ID. Suppression doesn't change that arithmetic: a suppressed or email_invalid address still holds its email, so it stays a billable profile; only anonymizing or deleting the customer removes the identifier that makes it count. So a never-messaged invalid is a fully billable profile that will never convert while it drives your bounce rate up. And that first wave of hard bounces is precisely the signal Gmail and Yahoo's 2024 sender rules — and Bloomreach's own deliverability dashboard and bounce-rate thresholds — judge you on, deciding whether the rest of your campaigns reach the inbox at all. Cleaning before a send does two jobs at once: it keeps junk off the count your usage fee is based on, and it protects the inbox placement of the campaigns that actually convert.

The workflow that works today

Bloomreach Engagement is an enterprise CDP driven by APIs and data pipelines rather than a simple CSV loop, so the reliable path is: export your audience from the Customers UI, the Data Exports feature, or the customer-export API, verify it in Qualisend, then suppress the failures via the custom suppression list — or, past its 5,000-entry cap, by importing the verdict back as a customer property you segment on and exclude, and anonymizing the truly dead profiles to take them off your billable count.

Export your audience from Bloomreach

For a targeted clean, open Data & Assets > Customers, filter to the segment you want to check, then use the three-dot menu > Download customer data, pick the email property and any IDs, and download the CSV. For a whole-database clean or an automated pipeline, use the Data Exports feature (or Engagement BigQuery), which streams raw customer data to your file storage as CSV or JSON — Bloomreach steers large pulls here rather than through the customer API, which is meant for smaller or single-customer exports.

Verify the file in Qualisend

Upload the CSV to Qualisend bulk cleaning — up to 1,000,000 addresses per job, duplicates charged once — or paste addresses directly. The free plan's 100 one-time credits, which never expire, cover a first sample so you can see the shape of your audience before you commit.

Read the results

Every address returns deliverable, risky, undeliverable, or unknown with a reason code, a 0–100 confidence score, and sub-flags (catch-all, disposable, role, full mailbox), plus the MX provider and probe detail as evidence. Download the cleaned CSV.

Suppress or anonymize the failures in Bloomreach

For a modest number of dead addresses, add them to the custom suppression list under Project settings > Campaigns > Channels > Emails — but that list caps at 5,000 entries and keeps the profile (and its email) billable, so it won't scale to a large undeliverable dump. For volume, import the verdict back as a customer property (for example email_status = undeliverable), build a segment on it, and exclude that segment from every campaign and scenario. To also take the dead addresses off your billable profile count, anonymize or delete those customers — the bulk anonymize API strips the email hard ID and PII that make a profile billable, while deletion removes the record and its event history entirely.

Or automate it at signup

Bloomreach is API-first, so the highest-leverage option is to verify at the point of capture — before your app's customer update or import creates the profile. Call the Qualisend REST API (scoped keys, rate limits, webhooks) at signup, or wire a no-code flow through Zapier, Make, or n8n, so a new address is checked before it's ever tracked into Engagement and becomes a billable profile.

What Qualisend flags on every address

Never-messaged invalid addresses that would hard-bounce the first time an event triggers a send
Disposable / throwaway domains built to expire that Bloomreach's managed list doesn't cover
Role addresses (info@, support@) that skew the engagement data your scenarios and segments run on
Catch-all domains, flagged so you can move them to a dedicated segment and throttle
A 0–100 confidence score and machine-readable reason code for every address

Native connector status

A native, one-click Bloomreach connector is part of the platform we're rebuilding — it's returning, not deprecated — and until it ships, the export-verify-suppress loop above and the REST API are the fully supported path on any Engagement plan.

What to do with each result

Every address comes back with a verdict and sub-flags. Here's the action that keeps your Bloomreach list clean without throwing away contacts you can still reach.

deliverableKeep messaging as normal.

deliverable + role flagKeep for transactional and consent-based mail; exclude from engagement-judged campaigns and scenarios.

risky + catch-all flagMove to a dedicated segment and throttle — the domain accepts everything at the door, so the mailbox behind it can't be confirmed.

risky + disposable flagAdd to the custom suppression list, or anonymize — the inbox was built to expire.

unknownKeep active and re-verify next clean — usually greylisting or rate-limiting, not a verdict on the mailbox.

undeliverableFor a few, add to the custom suppression list; for volume, segment-exclude the verdict and anonymize to take them off your billable profile count — don't wait for the bounce to prove it.

Bloomreach verification FAQ

Clean your Bloomreach list in minutes

Start free with 100 credits that never expire — no card required. Export, verify, reimport, and protect your next campaign.

Clean a list for free All integrations