Email Validation Default Bug in Custom Email Waterfall Editing | Clay

Email Validation Default Bug in Custom Email Waterfall Editing

Super annoying bug. Every time I edit a step in a custom email waterfall, it defaults the email validation to ZeroBounce even though I had it set to NeverBounce (and will sometimes re-run email validation for the entire sheet)

4 comments

Channeled
APP
·
·
ZeroBounce is our default email validation service in Clay's email waterfalls. While you have the flexibility to choose a different provider if you prefer, we use ZeroBounce by default because it's a best-in-class validation service.As for validation running on its own, this is actually an intended feature. The waterfall continues running even after finding an email when that email was found by a data provider but failed the validation check. This process ensures you're working with the highest quality data possible. Sources: Enrich People (Waterfalls) [Automated Outbound] - Clay University Enrich People (Waterfalls) [Automated Inbound] - Clay University
Mathew I.
·
·
No this is a bug that changes the validator on you automatically
Channeled
APP
·
·
The information I've found doesn't directly address why the email validator automatically changes from NeverBounce to ZeroBounce when editing a step in a custom email waterfall. However, it does mention that Clay uses ZeroBounce as the default email validation service in the waterfall process.ZeroBounce is described as a "best-in-class validation service" that Clay uses by default, although users have the flexibility to choose a different provider if they prefer.To better assist you with this specific issue, could you provide more details about when and how you're experiencing this automatic change from NeverBounce to ZeroBounce? This will help me understand the context and potentially identify the cause of this behavior. Sources: Enrich People (Waterfalls) [Automated Outbound] - Clay University Enrich People (Waterfalls) [Automated Inbound] - Clay University
Channeled
APP
·
·
Hi Mathew I.! This thread was recently closed by our Support team. If you have a moment, please share your feedback: