Verify your Drip subscribers before you send
Drip has no SimpleVerifier connector. Export your people, verify the CSV, then import the results with a tag. Drip warns that importing a file with the same headers as fields you already filled overwrites those fields, so the import file should be small.
The workflow
- In Drip go to People > Active, apply a filter for a subset or leave it blank for everyone, then use the Actions menu to export to CSV and confirm. The download link is emailed to the address in your user settings.
- Upload the CSV on the verify page, signed in; the first 100 checks are free. The email column is found by its header or contents and every other column is kept.
- When the job finishes, download the valid, risky and invalid files. Each keeps all of your original columns.
- Strip the invalid file down to the email column and a result column, so no other custom field is overwritten.
- Start an import from People, upload a CSV, keeping first row as headers on, and map the email column. Drip adds an Imported tag by default; add your own tag such as invalid-email as well, and watch progress on the Bulk Operations page.
- Import unsubscribed people separately from subscribed ones, as Drip advises, and never mark invalid addresses as subscribed. Then add a workflow rule that exits anyone tagged invalid-email.
Menu names follow Drip’s own help articles, checked 12 Nov 2026: export data, import data. Vendors rename menus, so trust what you see on screen if it differs. SimpleVerifier is not a Drip partner and has no Drip connector.
Columns to map
- Email, required on every row; rows without one or with a duplicate create no new person.
- Headers in lowercase with underscores map to Drip's built-in profile fields automatically.
- Skip custom fields you do not mean to change: the same header on an existing person overwrites that field.
What to do with risky and catch-all results
Tag risky people instead of removing them. Hold them out of the first send of a new workflow and let them in once the main group has gone out cleanly. A person with an order history on a catch-all domain is almost always real.
What people use it for
- Clean a store's list before a big promotional send.
- Check addresses that came from a migration out of another ESP.
- Remove dead people before they count against a plan priced by active people.
Using the result
Each address comes back valid (the mail server confirmed the mailbox), risky (delivery could not be confirmed: a catch-all domain, a role address such as info@, or a provider that hides mailbox status) or invalid (it will bounce, or it is a throwaway address).
Full endpoint reference, error codes and an OpenAPI file are in the API docs. For lists of thousands of addresses, upload a CSV on the verify page instead.
Run your 100 free checks on one list before you switch anything
Export one list’s addresses as a CSV and upload it: the first 100 are checked free in the dashboard, no card needed. Compare the results with what you use now, then decide. Nothing in Drip changes until you import a file back.
Common questions
- Which plans include API access for Drip?
- API access comes with Pro, Business and Agency, listed on the pricing page; Starter covers CSV verification only. A key on a plan without API access gets a 402 that says so. Each key can make 120 calls a minute.
- How large a CSV can Drip import?
- Drip's help says accounts created after 2 June 2020 are capped at 200,000 rows per CSV upload and only CSV files are supported.
- Can SimpleVerifier verify new Drip signups automatically?
- Not through a Drip integration, which does not exist. A form of your own could call the SimpleVerifier API (or use our free sign-up form widget) before the address reaches Drip.