PrestaShop email verification in three steps: export your customers, verify the file in PricklyMails, then unsubscribe the addresses to remove.
There is no native PrestaShop connector: you export the list, PricklyMails verifies it, and you bring the result back into PrestaShop. New addresses can go through the API before they ever reach PrestaShop.
Tip
PricklyMails only needs the addresses: copy the email address column into a new file for the batch.
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 from your newsletter, and from partner offers where they had accepted them. The customer account stays.
PrestaShop unsubscribes a customer from the customer list itself, one address at a time: filter the list on the address, then clear its checkmarks.
They deserve a look before your next newsletter. To look one up in PrestaShop, filter the list on its address the same way, then click View at the end of its row.
They stay subscribed: nothing to do.
Note
PrestaShop's documentation offers no way to unsubscribe several customers at once from the back office.
Does your app or sync script create customers through PrestaShop's webservice, on the customers (opens in a new tab) resource? Ask PricklyMails first. If the recommendation is remove, don't create the customer with its newsletter field set to 1.
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"
}
Unsubscribe them. In PrestaShop's documentation, the green checkmark of the Newsletter column unsubscribes the customer from your newsletter, the one of the Enabled column disables the whole account, and the delete action trashes the account forever. A customer who asks for their data to be erased goes through the GDPR module: once erased, the account and its addresses are deleted, while the invoices stay with the orders.
With Enable partner offers turned on, PrestaShop shows a Receive offers from our partners checkbox at registration, so that you can suggest your business partners' newsletters to the customers who tick it. An address that cannot receive your newsletter cannot receive theirs either. PrestaShop's documentation adds that you must never subscribe a customer to partner offers without their consent, as this is considered spam.
It is John DOE, the default customer PrestaShop creates when it is installed with sample data, so that you can test your shop as a regular user would. Its documentation asks you to delete it, or at least change its credentials, before you open your shop to the public: malicious visitors could otherwise use it to make fake purchases. Take it out of the file before verifying.
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 PrestaShop.
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.