What action options does Valid Email Checker offer for Elastic Email? (Tag / Unsubscribe / Delete)

Pick an Elastic Email list and switch the Valid Email Checker modal to Clean List Automatically, and three actions become available per result category. The dropdown labels read Keep, Unsubscribe, and Delete. The category rows (Invalid, Disposable, Catch-all, Unknown, Risky) are identical across every integration. What changes is how each action behaves inside Elastic Email.

How each action behaves

• Keep — VEC writes nothing back. The contact stays put. Custom fields, segment membership, and engagement history are untouched. Pick this when you want a results report without changing Elastic Email data.
• Unsubscribe — VEC calls the Elastic Email API to flip the contact status to Unsubscribed for the verified list. Custom fields, segment membership, and historical campaign engagement are preserved. The contact stops receiving any further sends but remains in the database.
• Delete — VEC removes the contact from the verified list. If the contact was only on that list, Elastic Email treats it as a full account-level removal.

Default settings

The defaults are the same as every non-ConvertKit integration. Only Invalid and Disposable are enabled out of the box; the more nuanced categories stay off so first-time runs never silently mutate large groups of contacts.

The Use Recommended Settings link snaps the panel back to defaults whenever you want. Combine these settings with the list selection covered in how to select an Elastic Email list to verify.

What Elastic Email preserves on Unsubscribe

• Custom fields — every custom field on the contact remains attached.
• Segment membership — the contact stays in any filter-defined segments they qualified for.
• Historical engagement — opens, clicks, and bounce data remain on the contact record for analytics.
• Subscription source — preserved on the contact profile.

Why the title says Tag and the UI says Keep

Tag/Unsubscribe/Delete is industry shorthand. Valid Email Checker uses Keep in the actual UI because that label honestly describes the no-op behavior. Some other vendors silently tag every contact with their results; VEC leaves Elastic Email data alone unless you explicitly choose Unsubscribe or Delete on a category.

The Risky category on Elastic Email

Risky bundles risky, spamtrap, and role_account from the engine. Spam traps damage Elastic Email deliverability quickly because the platform is shared infrastructure for many senders. Enabling Risky with Unsubscribe protects your sender reputation while keeping the audit trail intact.