Does Qualisend have a native CleverTap 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 CleverTap, verify in Qualisend, then mark the dead addresses unsubscribed via the Subscribe API or a profile upload — or verifying at the point of capture through the API. Both work with any CleverTap plan.

Will cleaning my list lower my CleverTap bill?

Not the direct way it would on a contact-count ESP. CleverTap bills on Monthly Billable Users — derived from your active users and data points, not from how many profiles you store — so a dormant dead address isn't automatically billable. The saving is indirect but real: CleverTap counts events and profile-property updates as data points, so cleaning stops you spending sends and data points on addresses that will always bounce, and it avoids re-uploading or re-engaging dead profiles — which is itself billable activity that can pull them back into your MAU. The bigger win is deliverability, not the invoice line.

How do I actually remove a bad address in CleverTap?

You suppress it rather than delete it — CleverTap doesn't offer routine profile deletion for hygiene. To retire a dead mailbox completely, pass the address to the Subscribe API with status Unsubscribe; that unsubscribes it across every profile that shares the address. If you only need to silence one profile, set MSG_email to false with the Upload User Profiles API or a CSV profile upload — but note this is per-profile, so any other profile on the same email keeps receiving until it's unsubscribed too. For list hygiene, the Subscribe API is the one to reach for.

Doesn't CleverTap already catch bounces and unsubscribes?

It does, but reactively — it needs your ESP to report a hard bounce or complaint, or the user to opt out, before the address is retired, which means the address has already been messaged and the reputation hit has already landed. (A soft bounce isn't even suppressed — it's just logged in the campaign report.) Never-messaged invalids from SDK calls, imports, and offline uploads have never bounced, so they stay active and keep qualifying for campaigns until you verify them yourself.

Can I verify addresses before they enter CleverTap?

Yes — it's the highest-leverage option. Verify at the point of capture through the REST API (or a Zapier/Make/n8n flow) so an address is checked before your identify or track call creates the profile, keeping typos and disposable addresses out of your audience — and out of your broadcasts — entirely.

Native connector returning — CSV & API work today

Keep your CleverTap audience deliverable before the campaign fires, not after the bounce

CleverTap tracks hard bounces, soft bounces, spam complaints, and unsubscribes, and once an address hard-bounces or a recipient complains or opts out it stops mailing that address — but it can't judge an address it has never messaged. Because CleverTap is event-driven, profiles are born from SDK identify and track calls, third-party imports, and offline uploads, so those never-messaged invalids sit in your audience looking healthy until an event pulls them into a broadcast or journey — which is exactly when a mailbox provider forms its first impression of your domain. Qualisend closes that gap: export your audience, verify every address, and mark the dead ones unsubscribed before they ever fire. Here's the workflow that works today, plus the API and no-code options.

Clean a list for free

One-click CleverTap 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 CleverTap 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 CleverTap clean right now.

CleverTap handles

What CleverTap cleans for you

CleverTap's native hygiene tracks hard bounces, soft bounces, spam complaints, and unsubscribes across campaign stats, user profiles, and exports, and it leans on your ESP's callback: for SendGrid, Postmark, Mandrill, and generic SMTP, CleverTap receives real-time bounce, drop, and unsubscribe events at a callback URL you configure. A soft bounce is only logged in the campaign report — the user is not suppressed — but a hard bounce and an opt-out both fold into "unsubscription": the email's communication preference is set to false (the MSG_email Do-Not-Disturb flag on the profile) and no further email is attempted. CleverTap also honors one-click (RFC 8058) list-unsubscribe automatically. The important caveat is that all of this depends on CleverTap being notified of a real failure — your ESP or SMTP relay has to report the bounce or complaint back before the address is retired. For addresses CleverTap has actually messaged and seen fail, that's reliable, automatic hygiene.

The gap it leaves

What it can't catch

The catch is that every one of those mechanisms is reactive — it needs a send, then a bounce, complaint, or opt-out to fire. CleverTap makes the blind spot sharper because a profile is created the moment your app fires an identify or track call, you import from a previous tool, or you push an offline CSV — none of which have ever been messaged. A signup typo (jane@gmial.com), a disposable address accepted at capture, a role address like info@ or support@, and a mailbox that has since decayed all look active until an event triggers the first email. Worse, because CleverTap is event-driven, those dead profiles don't sit quietly: they keep qualifying for broadcasts and journeys whenever an event matches, so the same bad address gets mailed again and again. An imported or uploaded audience is the sharpest case — it arrives with its bounce history stripped, so addresses that were already failing elsewhere look brand new.

Why a clean CleverTap list matters

CleverTap bills on Monthly Billable Users — derived from your Monthly Active Users and processed data points, whichever is higher — not on how many email addresses you store, so a dormant dead profile isn't automatically a line item the way a contact is on a contact-count ESP. That makes deliverability, not a stored count, the real stake. Every never-verified address you message becomes a hard bounce or a spam complaint, and those are precisely the signals Gmail and Yahoo's 2024 sender rules — and CleverTap's own IP reputation and warmup — are judged on; on a warming or shared IP, a wave of bounces is especially costly. There is a quieter cost too: CleverTap counts an event, event property, or profile-property update as a data point, so every send that records a Notification Sent event and every re-upload or re-engagement of a dead profile spends data points — and re-touching a dormant profile can pull it back into your MAU. Churning through addresses you'll never reach spends real activity on sends that were always going to fail. Cleaning before the send protects the reputation your inbox placement depends on and stops you burning sends and data points on addresses that can't convert.

The workflow that works today

CleverTap is an API- and SDK-driven engagement platform, not a simple list tool, so the reliable path is: export your audience (a Segments CSV download or the export API), verify it in Qualisend, and suppress the failures by marking them unsubscribed — email-level via the Subscribe API, or per-profile via an MSG_email=false profile upload.

Export your audience from CleverTap

In the dashboard, open Segments, find the people you want to clean, open View Details, and use the download under Total users to export the segment to CSV — make sure the email identity column is included. For large audiences or a repeatable pipeline, use CleverTap's export API or a partner/data-warehouse export instead, which delivers full and incremental user profiles as CSV, JSON, XML, or Parquet (chunked into ~100 MB files) on a schedule.

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 a sample into the free checker first. The free plan's 100 one-time credits, which never expire, cover an initial spot-check before you commit.

Read the results

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

Suppress the undeliverables in CleverTap

CleverTap has no routine "delete profile" button for hygiene — the mechanism is to mark the address unsubscribed so it's held out of every future send. Filter your results to undeliverable, then choose the scope you need. The Subscribe API with status Unsubscribe is the email-level option: post a d array of {type:"email", value, status:"Unsubscribe"} objects (up to 1,000 per request) and CleverTap unsubscribes that address across every profile that shares it — which is what you want for retiring a dead mailbox. Setting the MSG_email flag to false via the Upload User Profiles API (or a CSV profile upload) is the per-profile alternative — be aware it only silences the profile you touch, so any other profile sharing that email keeps receiving unless it's unsubscribed too. For whole-address hygiene, prefer the Subscribe API.

Or automate it at signup

Prefer to keep junk out from the start? Verify at the point of capture with the Qualisend REST API (scoped keys, rate limits, webhooks), or wire a no-code flow through Zapier, Make, or n8n so an address is checked before your SDK identify or track call creates the CleverTap profile — that way typos and disposable addresses never enter your audience, never qualify for a broadcast, and never fire a wasted send.

What Qualisend flags on every address

Never-messaged invalid addresses that would hard-bounce the first time an event pulls them into a campaign
Disposable / throwaway domains accepted at capture that were built to expire
Role addresses (info@, support@) that skew the engagement data your journeys 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 CleverTap connector is part of the platform we're rebuilding — it's returning, not deprecated. Until it ships, the export-verify-suppress loop above and the API are the fully supported path, and they work with any CleverTap plan.

What to do with each result

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

deliverableKeep messaging as normal.

deliverable + role flagKeep for transactional and account mail; exclude from engagement-judged journeys.

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 flagMark unsubscribed via the Subscribe API (status Unsubscribe) — the inbox was built to expire.

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

undeliverableSuppress with the Subscribe API (status Unsubscribe) so the address is held out across every profile that shares it; don't wait for the bounce to prove it.

CleverTap verification FAQ

Clean your CleverTap 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