// email marketing and newsletters
Via APICustomer.io email verification with pingutil
Customer.io sends onboarding and lifecycle email to every person your app identifies, including signups made with throwaway or mistyped addresses. The "Send and receive data" webhook action can call pingutil directly, save the verification status as a customer attribute from the response, and let the next branch decide whether the person gets email at all. No server of your own is needed.
Where it connects: Customer.io campaign "Send and receive data" webhook action calling pingutil directly, with a Response attribute saved to the person
What goes wrong without it
- Our onboarding campaign fires for every signup, and a lot of the bounces come from people who never typed their real email.
- Trial abusers create accounts with temp-mail domains and still go through the full drip, which wrecks our activation numbers.
- We want one attribute in Customer.io that says whether an email is real, so every campaign can filter on it.
What you can do with Customer.io and pingutil
Verify as the first step of onboarding
The campaign triggers on signup, the webhook action calls /v1/verify, and the Response tab stores status on the person before any email goes out.
Suppress invalid people automatically
A True/False branch on email_status sends invalid people to a Create or update person action that sets unsubscribed to true.
Segment trial abuse
Store the reason too, then build a segment on email_reason = disposable_domain to see which signups came from throwaway domains.
Set it up
- 1
Create a pingutil API key and save it in Customer.io as a secret you can reference in webhook headers.
- 2
In your signup-triggered campaign, add a Send and receive data action as the first step and click Add Request.
- 3
Set the method to POST, the URL to https://pingutil.com/v1/verify, add the Authorization and Content-Type headers, and paste the body from the snippet.
- 4
On the Response tab, add customer attributes: email_status from response.status, email_reason from response.reason and email_did_you_mean from response.did_you_mean.
- 5
Add a True/False branch on email_status; on the invalid path set unsubscribed to true, and let valid, risky and unknown continue.
{
"method": "POST",
"url": "https://pingutil.com/v1/verify",
"headers": {
"Authorization": "Bearer pk_live_your_key",
"Content-Type": "application/json"
},
"body": {
"email": "{{customer.email | strip}}"
},
"response_tab_customer_attributes": {
"email_status": "response.status",
"email_reason": "response.reason",
"email_did_you_mean": "response.did_you_mean"
}
}What to do with each result
| pingutil result | Action in Customer.io |
|---|---|
| response.status = "invalid" | Branch to Create or update person and set unsubscribed to true. |
| response.reason = "disposable_domain" | Same invalid path; also filter these people out of trial-conversion reports. |
| response.status = "risky" | Continue onboarding but keep the person out of high-volume newsletters. |
| response.status = "unknown" | Continue; add a later step that calls the webhook again after a delay. |
| response.did_you_mean is not empty | Trigger an in-app message asking the user to fix their address. |
Limits to plan for
- Customer.io times out webhook requests after 16 seconds and retries up to 11 times over about an hour. Most checks finish well within that, but a slow mail server can push a check past it. For a pure disposable screen, call /v1/lookup with skip_enrichment: true instead, which answers in milliseconds.
- If every retry fails, the person moves on without the Response attributes, so treat an empty email_status as unchecked, not as valid.
- pingutil checks up to 300 addresses per account per day (3,000 a month) and allows 60 requests a minute; a large signup spike can hit 429 responses. Those are Free plan limits; Enterprise has custom limits.
Customer.io documentation
Customer.io is a trademark of its owner. This integration uses Customer.io's documented extension points; it is not an official Customer.io app.
Common questions
- Do I need my own server for this?
- No. The Send and receive data action calls pingutil directly and the Response tab writes the result to the person. You only need code if you want to call more than one endpoint or add custom logic.
- Should I use /v1/verify or /v1/lookup here?
- Use /v1/verify when you want to know whether the mailbox exists. Use /v1/lookup with skip_enrichment when speed matters more and you only need to catch disposable and machine-generated addresses.
Stop bad addresses in Customer.io today
Sign in with your email, create an API key and paste it into the step above. Test on a few real addresses first: the live demo shows exactly what your Customer.io setup will receive.