ZapBounce and Omnisend
Omnisend runs email and SMS from the same contact record, aimed at ecommerce. That combination has a specific cost when the data is wrong: a bad import wastes sending reputation and SMS credits at the same time.
SMS credits are spent per message with no refund for a bad number, which makes the case for checking before import rather than after.
One contact record, two channels, two costs
An imported contact with a dead email address and a working phone number still costs you the email bounce. One with a mistyped address that happens to be valid sends an order confirmation to a stranger.
Omnisend's automations trigger on contact and event data, and an ecommerce workflow fires on abandoned carts and purchases without any pause for review.
Checkout typos are the dominant email problem in this platform's data, because the addresses come from a store rather than a signup form where someone was paying attention.
How the data moves
Verify before the contact reaches Omnisend
Between your store and the Omnisend API, so the contact is created with a verdict already on it.
Store the verdict as a custom property
Omnisend segment conditions read custom properties, so a catch-all contact can take a different automation path.
Bulk-verify the existing contact base once
Export, verify, import the verdicts back. Do this before adding segment conditions, so the conditions have data to read.
Check at checkout for typos
A single check on submit flags gmial.com as invalid while the customer is still on the page, which is the only moment the fix is free.
Setting it up
- Export contacts from Omnisend as CSV with custom properties.
- Verify the file and poll the job until it completes.
- Create a custom property for the verdict and import the results.
- Add a verification call between your store and the Omnisend contact API.
- Build segment conditions on the verdict for your email automations.
- Ask the customer to correct an invalid address at checkout rather than changing it automatically.
Omnisend: common questions
Does this verify phone numbers?
It verifies email addresses, the channel your order confirmations and flows depend on. SMS numbers need a phone validation service of their own.
Where should the check go in an ecommerce flow?
At checkout on field blur, with a retype prompt shown. Fail open, because a slow verifier must never block a paid order.
Should I block disposable addresses at checkout?
Rarely. Someone with a card in hand is a customer whatever mailbox they used.
Check a Omnisend export today
100 free checks a month, no card. Unknown results are refunded.