Verify your Omnisend contacts before a campaign
Omnisend has no SimpleVerifier connector. For an ecommerce store list the route is export, verify, and re-import with a tag. Omnisend skips a contact when an email or phone repeats in the file, so a clean unique file imports more reliably.
The workflow
- In Omnisend go to Audience > Export and click New Export, choose All contacts or narrow by subscription status and click Export. Open the Exports tab and click Download. Only Owner, Admin and Analyst roles can export, and a large list can take several minutes.
- 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.
- Check the files for repeated emails or phone numbers. Omnisend skips a contact when either one is duplicated in the file.
- Click Add contacts > Import contacts from file (the wizard accepts .csv, .xls, .xlsx or .ods with one sheet and a header row), upload the invalid file, map the columns and create a tag such as invalid-email during import.
- Create a segment on that tag and exclude it from campaigns and automations (welcome series, abandoned cart, win-back). Leave subscription status as it is.
Menu names follow Omnisend’s own help articles, checked 12 Nov 2026: export contacts, import contacts. Vendors rename menus, so trust what you see on screen if it differs. SimpleVerifier is not a Omnisend partner and has no Omnisend connector.
Columns to map
- Email, or a phone number in international format; each row needs one of them.
- Keep dates in ISO 8601 format and any non-Latin text in UTF-8, as the importer expects.
- Leave extra custom properties out unless you want to update them; a single file can hold up to 200.
What to do with risky and catch-all results
On a store list, risky is often a customer using a work address or a catch-all domain. Do not suppress them from order and shipping messages, only from marketing volume. Send a small win-back to the risky segment and suppress anyone who bounces.
What people use it for
- Clean the list before a seasonal sale, when send volume spikes.
- Remove dead addresses that came in through a checkout pop-up or a spin-to-win form.
- Cut contact count on a plan priced by contacts.
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 Omnisend changes until you import a file back.
Common questions
- Which plans include API access for Omnisend?
- 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.
- Does this change the subscription status in Omnisend?
- Only if you set it in the import wizard, which asks you to choose a status. Pick the option that leaves existing status as it is when you only want to add a tag.
- Is there an Omnisend app or Shopify tie-in from SimpleVerifier?
- No. SimpleVerifier has no Omnisend or store-platform connector, and this page is the CSV workflow only.