Customer.io email verification options
When mailfloss finds an invalid email in Customer.io, the Cleanup tab of your Customer.io integration decides what happens. You have five options. The setting applies to every list in the connection, and you can change it any time.
Before you choose an option, connect Customer.io to mailfloss. You only do this once. From then on, mailfloss verifies the emails in the connected Customer.io account automatically.
Here are the five options in the Cleanup tab:

Ask me first. The safest option. mailfloss lists invalid emails in the Waiting for you tab, and nothing changes in Customer.io until you decide.

In Waiting for you, select emails and choose Unsubscribe, Delete, or Update custom fields. You can also mark them Report incorrect or Ignore, and filter the list by category.
Unsubscribe. The recommended option. mailfloss unsubscribes the contact in Customer.io, so it stops receiving campaigns. You see the contact as Unsubscribed in Customer.io. You can resubscribe it in Customer.io at any time. When you choose this option, mailfloss asks you to confirm. Turn on the switch under Unsubscribe to also update the fields.

Delete from Customer.io. Irreversible. mailfloss removes the contact for good, and you won’t find it in Customer.io anymore. Before this option turns on, mailfloss shows what your last run would have deleted and asks you to type the account name to confirm.
Update a field. mailfloss writes the verification result to custom fields in Customer.io, so your segments can exclude invalid emails. You can also use them to sync with your other databases and CRMs, and to run automations, segments, and reports. This is reversible.
For more information about our custom fields check this article.

Report only. mailfloss emails you a report of the latest floss session. Nothing changes in Customer.io. Choose this option if you only want the verification statuses for the connected Customer.io account, like a traditional email validation service.
For an overview of what mailfloss does for Customer.io, see the Customer.io integration page.