# Verify emails for Klaviyo with Spaw

Verify new Klaviyo profiles through Zapier or Make, store the verdict as a profile property for segments and flows, and clean an existing list with a bulk run.

Updated: 2026-09-03

Klaviyo profiles arrive from storefront sign-ups, pop-ups and checkout, and a welcome flow fires within minutes. Verifying the address before that first send keeps bounces out of the account's reputation. Spaw has no Klaviyo app; the flow below uses Klaviyo's trigger in Zapier or Make, a verification step, and a profile update that stores the verdict as a custom property your segments can read.

## Verify new profiles

1. Create a secret API key on the API keys page of your Spaw dashboard.
2. In Zapier or Make, start with the Klaviyo trigger for a new profile or a new list subscription.
3. Add the verification step: a Webhooks by Zapier POST or a Make HTTP request to `https://spaw.co/api/v1/email` with the header `Authorization: Bearer sk_live_…` and this body, mapping the profile's email:

```json
{
  "email": "mia@acme.com"
}
```

The [Zapier page](/integrations/zapier) and the [Make page](/integrations/make) list every setting. Once the Spaw apps for those platforms are listed, the step becomes a Verify Email action with a saved connection.

4. Add the Klaviyo action that updates a profile, match on the email, and write custom properties from the response: `spaw_verdict` from `data.deliverable`, `spaw_reason` from `data.reason`, and `spaw_risk_score` from `data.risk_score`.
5. Build a segment in Klaviyo where `spaw_verdict` equals `undeliverable` and exclude it from your flows and campaigns, or invert it and send only to profiles whose verdict equals `deliverable`.
6. Test by subscribing `deliverable@spaw.test`, a free test address that answers a fixed result and is never logged.

Because the welcome flow may fire before the Zap finishes, add a short delay at the start of the flow, or make the first email conditional on the property being set. A few minutes is enough.

## Clean an existing list

Export the list or segment to CSV, run the email column through a bulk verification on the Spaw dashboard or with the [bulk endpoint](/docs/api/create-bulk-job), and import the result CSV back into Klaviyo with the verdict columns mapped to the same custom properties. The result keeps your original columns. Undeliverable rows also join your Spaw suppression list, so the next run answers them without a probe.

## What to do with the verdict

Keep the decision in segments so it applies to every flow at once. `deliverable` profiles get the full program. `risky` profiles need the reason: [`disposable`](/docs/reasons/disposable) addresses are throwaway inboxes that will never convert, `catch_all` addresses are unconfirmed but often real, and `role` inboxes such as info@ are shared. `undeliverable` profiles should be suppressed in Klaviyo rather than deleted, because a filled `data.did_you_mean` is a customer who mistyped at checkout and can be reached through another channel, for example SMS, with the corrected address. For stores on Shopify, the [Shopify page](/integrations/shopify) covers the customer-side flow.

## Cost

Each new profile that answers deliverable or risky spends 1 credit; undeliverable answers and repeats within seven days are free. Zapier and Make bill their own tasks. Bulk runs bill per processed row and verify duplicates once.

Reference: https://spaw.co/integrations/klaviyo