Connect MailerLite to Qualisend

• A Qualisend account. You can sign up for free.
• To connect MailerLite, the Owner or Admin role in Qualisend (who can do what).
• Access to Integrations → API in your MailerLite account, to create an API token.
• Enough credits for the active subscribers you plan to check.

Under What to clean, the picker offers three kinds of source:

• Subscribers, with one entry, All subscribers: every active subscriber in the account. Subscribers with another status, such as unsubscribed, bounced or unconfirmed, are left out.
• Groups: the active members of one group. The picker lists your first 1,000 groups.
• Segments: the people MailerLite currently includes in that segment. The picker lists your first 300 segments.

For All subscribers and groups, the line under the picker shows how many active subscribers Qualisend found and the most credits the clean can use. Segments show no number there, because MailerLite's segment counts aren't reliable; they're counted while being read.

If MailerLite doesn't return your segments, only Subscribers and Groups appear. Reload the page later to get them back.

Tag contacts with results fills five custom fields on each subscriber it checks, unknown results included. Qualisend creates the fields in your account the first time it writes results, and every new result overwrites the last one. Nothing else on the subscriber changes: status, groups and consent stay as they are.

The status guide explains each verdict.

Keep bad addresses out of your sends

To leave bad addresses out of a campaign, create a segment in MailerLite with a condition on Qualisend Status that excludes undeliverable, and send to that segment. Exclude risky too if you'd rather be strict; What to do with each result lists an action for every verdict.

Qualisend Score is a number field, so segment conditions can compare it: for example, hold back anything below a score you choose.

Deleting or unsubscribing the bad addresses is up to you; Qualisend never does it.

Real-time checks verify each new subscriber soon after MailerLite reports them, and write the result into the same five fields. Turning them on takes one click, because Qualisend creates the webhook in your MailerLite account for you.

For sign-up forms on your own site, you can also check addresses before they reach MailerLite with the verification API.

• The same address is checked at most once in 7 days, whichever option you picked.
• Subscribers who haven't confirmed a double opt-in yet are checked; unsubscribed, bounced and junk subscribers are skipped.
• Imports and API sign-ups may trigger checks as well. Before a large import, read Real-time checks, which also covers credits and a zero balance.
• Under Webhooks pointing at Qualisend, the card lists the MailerLite webhooks that send here and shows Working, Needs a fix or Can't check next to each. A webhook with a problem comes with a note saying what's wrong.
• Prefer an automation? The card's Set it up manually instead section explains how to add a Webhook step, available on paid MailerLite plans, to an automation that starts When subscriber joins a group. Its URL identifies your workspace, so don't share it.

Pick an auto-clean interval under Repeat and click Verify & clean: the clean runs now and then repeats (how schedules run). Each source has one schedule, so scheduling the same source again replaces it. If this schedule's previous run hasn't finished, writing results back included, the next one waits and tries again about an hour later.

Schedules are listed under Scheduled auto-cleans on the MailerLite page, where a run may also be marked:

• Last run: no contacts: the group, or the whole account, had no active subscribers.
• Skipped - reconnect MailerLite: MailerLite wasn't connected when the run was due. After you connect again, the schedule carries on from its next date.

• Each run, auto-cleans included, reads up to 1,000,000 active subscribers from the source. A bigger source gets its first 1,000,000 cleaned on every run.
• The credits a clean needs are set aside from MailerLite's own count when it starts. A segment has no reliable count, so Qualisend sets aside an estimate of up to 5,000 credits and adds more while reading.
• If your balance runs out while subscribers are still being read, Qualisend stops reading and cleans the subscribers it already has.
• Credits set aside beyond what was actually read come back once reading ends. The other credit rules are in How credits are counted.

Click Disconnect on the MailerLite page. There's no confirmation step, and it takes the Owner or Admin role.

What happens next:

• Qualisend removes your API token and deletes its Qualisend real-time verification webhook from MailerLite. If that fails, a message says so; then delete the webhook yourself under Integrations → API, Webhooks.
• Your subscribers keep the Qualisend fields and the values already written.
• Schedules stay, but each run shows Skipped - reconnect MailerLite until you connect again.
• A clean that's still reading subscribers ends with Verification failed, and one that's still writing results stops writing them.
• Results of past cleans remain in Qualisend.

To connect again, paste a token as in the first steps. Real-time checks are off after reconnecting, so turn them on again.

If Qualisend tells you your real-time webhook URL changed, paste the new URL into any MailerLite automation that sends subscribers to Qualisend.