Fixing Zerobounce Column Issue in Custom Email Waterfall

Ruadhán Ó Cúláin · 2024-12-15 18:13:46.812085+00

Whenever I create a custom email waterfall, no matter how many times I refresh or update the settings, it always populates a Zerobounce validation column and it's nearly cost me an awful lost of credits a good few times now - How do I fix this, seems like a bug?

Fixing Zerobounce Column Issue in Custom Email Waterfall | Clay

8 comments

· Sorted by Oldest

Channeled
APP
·
·
This behavior is actually by design - Clay's email waterfalls include email validation as part of the process, with ZeroBounce being the default validation service. The validation columns exist behind the scenes even when not displayed to ensure data quality.To manage this and prevent unwanted credit usage, you have a few options: 1. Turn off auto-update: By default, the integration auto-updates every 24 hours. You can disable this toggle if you don't want automatic updates. 2. Use conditional runs: You can set specific criteria for when the validation should run by using conditional run formulas. This gives you more control over when validation occurs. 3. Adjust the "Safe to Send" toggle: This setting can help you be more selective about which emails get validated, as it will only return emails categorized as "valid" rather than including catch-all emails. Sources: Enrich People (Waterfalls) [Clay 101] - Clay University Zerobounce integration overview | Clay University Enrich People (Waterfalls) [Automated Inbound] - Clay University
Channeled
APP
·
·
Looks like you're still looking for help. We're escalating this over to our support team and someone should be in touch soon. In the meantime, feel free to include any other information that may be helpful in solving your issue!
Daniela Debebs (Clay)
·
·
Hey Ruadhán! Thanks for reaching out. Happy to help. Could you share a table example (link in your browser tab)? We'll check this. To confirm, you tried to exclude a validation provider from the waterfall but it always adds Zerobounce or it doesn't allow you to remove (the current provider) or select a different provider?
Joe Rhew (wfco.co/team/joe)
·
·
Yeah I’ve been having the same issue
Joe Rhew (wfco.co/team/joe)
·
·
I have a debounce plan and my own API key so always set it to debounce when creating an email waterfall. This time I’ve even checked the hidden email validation columns and saw that when initially created, they were debounce. Then I ran a few rows and checked again and the validation columns had turned to Zerobounce. Definitely a bug.
Anaum (Clay)
·
·
Hi Ruadhán! I’m really sorry for the trouble here — it definitely looks like we’ve got a bug on our hands. I’ve escalated this to our engineering team so they can investigate further. We’ll follow up with you as soon as we have more information. Thank you for flagging this, and I appreciate your patience while we sort it out!
🙌1
Anaum (Clay)
·
·
Good news! Happy to report that we heard back from the team and this issue should be fixed. Thank you for your patience as we worked on it. Please let us know if the problem has been resolved on your end, or if you still have trouble.
Channeled
APP
·
·
Hi Ruadhán Ó Cúláin! This thread was recently closed by our Support team. If you have a moment, please share your feedback:

Channeled
APP
·
·
This behavior is actually by design - Clay's email waterfalls include email validation as part of the process, with ZeroBounce being the default validation service. The validation columns exist behind the scenes even when not displayed to ensure data quality.To manage this and prevent unwanted credit usage, you have a few options: 1. Turn off auto-update: By default, the integration auto-updates every 24 hours. You can disable this toggle if you don't want automatic updates. 2. Use conditional runs: You can set specific criteria for when the validation should run by using conditional run formulas. This gives you more control over when validation occurs. 3. Adjust the "Safe to Send" toggle: This setting can help you be more selective about which emails get validated, as it will only return emails categorized as "valid" rather than including catch-all emails. Sources: Enrich People (Waterfalls) [Clay 101] - Clay University Zerobounce integration overview | Clay University Enrich People (Waterfalls) [Automated Inbound] - Clay University
Channeled
APP
·
·
Looks like you're still looking for help. We're escalating this over to our support team and someone should be in touch soon. In the meantime, feel free to include any other information that may be helpful in solving your issue!
Daniela Debebs (Clay)
·
·
Hey Ruadhán! Thanks for reaching out. Happy to help. Could you share a table example (link in your browser tab)? We'll check this. To confirm, you tried to exclude a validation provider from the waterfall but it always adds Zerobounce or it doesn't allow you to remove (the current provider) or select a different provider?
Joe Rhew (wfco.co/team/joe)
·
·
Yeah I’ve been having the same issue
Joe Rhew (wfco.co/team/joe)
·
·
I have a debounce plan and my own API key so always set it to debounce when creating an email waterfall. This time I’ve even checked the hidden email validation columns and saw that when initially created, they were debounce. Then I ran a few rows and checked again and the validation columns had turned to Zerobounce. Definitely a bug.
Anaum (Clay)
·
·
Hi Ruadhán! I’m really sorry for the trouble here — it definitely looks like we’ve got a bug on our hands. I’ve escalated this to our engineering team so they can investigate further. We’ll follow up with you as soon as we have more information. Thank you for flagging this, and I appreciate your patience while we sort it out!
🙌1
Anaum (Clay)
·
·
Good news! Happy to report that we heard back from the team and this issue should be fixed. Thank you for your patience as we worked on it. Please let us know if the problem has been resolved on your end, or if you still have trouble.
Channeled
APP
·
·
Hi Ruadhán Ó Cúláin! This thread was recently closed by our Support team. If you have a moment, please share your feedback: