Loops email verification in three steps: export your audience, verify the file in PricklyMails, then unsubscribe the addresses that cannot receive mail.
There is no native Loops connector: you export the list, PricklyMails verifies it, and you bring the result back into Loops. New addresses can go through the API before they ever reach Loops.
Tip
To verify part of your audience only, such as the contacts still subscribed, set a filter first: the file then holds the contacts it shows. It has a column for every contact property, so keep the email column alone in a spreadsheet before moving on.
Note
Every address gets a recommendation: the action to take. The report writes it with the dashboard's label; the API returns a short form of it.
Note
Behind each recommendation sit a verdict (Valid, Risky, Invalid or Not verifiable), a reason and a score from 0 to 100, each in its own column of the report. When a server never answers, the address comes back "Not verifiable" and the checks that got no answer are refunded.
Open the report in a spreadsheet and filter the Recommendation column.
They get unsubscribed: Loops stops sending them your campaigns and workflow emails, and no longer counts them toward your plan.
A CSV upload updates each contact it matches by email address, and a Subscribed column holding false marks it unsubscribed.
Email.Subscribed, write false on every row, and save the file as CSV.They deserve a look before your next campaign. To find them in Loops, upload them the same way with a column such as emailCheck holding review instead of Subscribed: Loops stores it as a custom contact property, which a filter on the Audience page can select.
They stay subscribed: nothing to do.
Note
An unsubscribed contact still receives your transactional emails: unsubscribing only stops campaigns and workflow emails.
Warning
Set Subscribed to false only for the addresses to remove: Loops cannot re-subscribe a contact through a CSV upload or from the Audience page, only through its API.
Does your signup form or backend add contacts to Loops through its API, with the Create a contact (opens in a new tab) call? Ask PricklyMails first. If the recommendation is remove, don't create the contact.
One call starts the verification and already flags a likely typo, a second one reads the verdict. Depending on your plan, a signed webhook can also send it to you as soon as it's ready.
curl -s https://api.pricklymails.com/api/verify \
-H "Authorization: Bearer pm_live_9f3a..." \
-H "Content-Type: application/json" \
-d '{ "email": "ana.silva@gmail.con" }' \
| jq '{job_uuid, suggestion}'
{
"job_uuid": "8f1c2a9e-4b7d-4e2a-9c61-3d5f0b7a2e18",
"suggestion": "ana.silva@gmail.com"
}
curl -s https://api.pricklymails.com/api/verify/$JOB_UUID \
-H "Authorization: Bearer pm_live_9f3a..." \
| jq '.verifications[0] | {status, reason, score, recommendation}'
{
"status": "invalid",
"reason": "no_mx_records",
"score": 0,
"recommendation": "remove"
}
Loops' guide to bounce rates does not recommend running your audience through external verification services: it says they flag valid mailboxes as invalid, can generate probe traffic that hurts your sender reputation, and leave the usual cause, signup hygiene or sending to disengaged contacts, untouched. PricklyMails recommends remove only when the domain or mailbox does not exist, or the address is disposable or mistyped; one it cannot confirm gets review. It checks from its own servers and domain and sends no email, so your sender reputation is not involved. And its API checks each address at signup, before it reaches Loops, where that guide puts the fix.
Loops suppresses an address after a hard bounce or a complaint: by then the email has gone out and the bounce has counted. Its guide calls a bounce rate under 2% healthy and deliverability at risk above 5%. It traces bounces on a mailbox that does not exist to stale addresses, often from old imported lists, and those on a domain not found to typos. Those are the addresses verification finds before you send.
Unsubscribe them. Loops' help suggests keeping unsubscribed contacts in your audience: deleted and added back later, they may end up subscribed again. An unsubscribed contact does not count toward your plan and gets no campaigns or workflow emails, but still receives your transactional emails. If one of those bounces, Loops suppresses the address, which blocks every send to it.
No, there is no native connector: you go through a file export, as above. You can also call the PricklyMails API from your own code before an address reaches Loops.
These trademarks belong to their respective owners. Naming them implies no partnership.
1,000 tokens free when you sign up, no credit card. After that, you only pay for answers.