ZapBounce

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

  1. Verify before the contact reaches Omnisend

    Between your store and the Omnisend API, so the contact is created with a verdict already on it.

  2. Store the verdict as a custom property

    Omnisend segment conditions read custom properties, so a catch-all contact can take a different automation path.

  3. 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.

  4. Check at checkout with the typo suggestion

    The did_you_mean field catches gmial.com while the customer is still on the page, which is the only moment the fix is free.

Setting it up

  1. Export contacts from Omnisend as CSV with custom properties.
  2. Verify the file and wait for the completion webhook.
  3. Create a custom property for the verdict and import the results.
  4. Add a verification call between your store and the Omnisend contact API.
  5. Build segment conditions on the verdict for your email automations.
  6. Show the typo suggestion at checkout rather than applying it automatically.

Omnisend: common questions

Does this verify phone numbers?

No. Email addresses only, and SMS validation is a different service.

Where should the check go in an ecommerce flow?

At checkout on field blur, with the typo suggestion 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.

Reference

Check a Omnisend export today

100 free checks a month, no card. Unknown results and duplicates are never billed.

Get an API keySee pricing