Email Validation: Identifying the Issue of Emails Ending Up in Incorrect Boxes

When looking at this example. Why are some emails ending up in the validated email boxes and some not? It will be too much work to correct this afterwards in the spreadsheet export

8 comments

Clay Team
APP
·
·
Hey hey! Can you drop the URL for your table here? (if applicable) 🫶 Don't worry, only admins will be able to open your table 😉
Jesse B.
·
·
https://app.clay.com/workspaces/154849/tables/t_3B9ZmsNVqu5Q/views/gv_JgTMT9LCsTMW
Juan P.
·
·
I think this is because debounce detect them as invalid, so it keeps populating in the waterfall and if a new email is not generated it leaves a blank cell
✨1
Jesse B.
·
·
Thank you Juan P.. Ok so I should consider the email not generated? In other words, what does is mean exactly when an email is invalid? That we better not use it?
Juan P.
·
·
Is not safe to send emails to that direction, could be a catch-all email or an invalid email, so you can land in spam and the deliverability of your domain will be affected. I would not take the risk.
✨1
Clay Team
APP
·
·
Hey, thanks for reaching out! Appreciate you jumping in, Juan!
Clay Team
APP
·
·
Here's an example if it helps clarify a bit more :) The waterfall gives you the option to add a validation provider to check results from each email finder. When the validation tool determines the email is invalid, the next email finder tries to find a new one, but if it finds the same email as the previous column it won't try to validate it again because it already tried to validate once before, and this could result in no final output because none were valid.We automatically hide validation columns helping keep tables clean and that's why it's not evident at first glance. Let me know if you still have any questions though!Example and explanation: https://www.loom.com/share/e79acd92841a4706b1710c4ce1bddaa4
Clay Team
APP
·
·
By the way, Jesse B., I replied to your other threads in the web chat. Let me know