.png){kind=logo}
Logic for Email Selection in Final 'Work Email' Column Explained
What’s the logic determining which emails get copied to the final ‘Work Email’ column? I see some emails being found (marked with green checkmarks) but not appearing in the output.
What’s the logic determining which emails get copied to the final ‘Work Email’ column? I see some emails being found (marked with green checkmarks) but not appearing in the output.
The final 'Work Email' column only includes emails that have passed both the finding and validation processes: 1. When an email is found (marked with green checkmark), it still needs to pass through email validation before appearing in the final column. 2. If you see emails with green checkmarks not appearing in the output, this typically means they were found by a data provider but failed the validation check. The waterfall continues running in these cases to find a valid email.By default, we use ZeroBounce for validation, and while catch-all emails are considered valid, you can make the validation more strict by enabling the "only mark safe to send" option.To understand the specific validation results, you can unhide the validation columns that exist behind the scenes. Sources: Enrich People (Waterfalls) [Clay 101] - Clay University Enrich People (Waterfalls) [Automated Outbound] - Clay University
When an email gets a green checkmark, it still needs to pass validation to appear in the final 'Work Email' column. By default, we use ZeroBounce for validation, and an email will be considered valid in two scenarios: 1. If it's classified as a regular "valid" email 2. If it's classified as a "catch-all" email (by default)You can make the validation process more strict by enabling the "only mark safe to send" option, which will only accept emails classified as "valid" and exclude catch-all emails.If you want to understand why specific emails aren't making it to the final column, you can unhide the validation columns that exist behind the scenes to see the detailed validation results. Sources: Enrich People (Waterfalls) [Automated Outbound] - Clay University Enrich People (Waterfalls) [Clay 101] - Clay University Validate Email with Zero Bounce
Some columns are still outputting results even though they are ’valid catch alls”.
There seems to be an inconsistency
By default, catch-all emails are actually returned as valid in our system. This means they will appear in the output columns because they're considered valid emails, even though they're marked as catch-alls. While these are often real emails, there's some uncertainty about whether they belong to the specific individual or if they're aliases.If you want to exclude catch-all emails from appearing in the output, you can enable the "only mark safe to send" option. This setting will make the validation more conservative and only return emails that are classified as "valid" (excluding catch-all emails). Sources: Enrich People (Waterfalls) [Clay 101] - Clay University Validate Email with Zero Bounce Enrich People (Waterfalls) [Automated Outbound] - Clay University
The apparent inconsistency might be due to different email validation tools using varying criteria to assess catch-all emails. Here's what you should know: 1. By default, catch-all emails are returned as valid in our system, though there's some uncertainty about whether they belong to the specific individual or if they're aliases. 2. Different validation tools (like ZeroBounce and LeadMagic) may have different criteria for classifying catch-all emails, which can lead to varying results.To ensure more consistent and conservative results, you can: ** Enable the "only mark safe to send" option, which will only return emails classified as "valid" and exclude catch-all emails ** Check the validation sub-status in your results to see how specific emails are being classified Sources: Enrich People (Waterfalls) [Automated Outbound] - Clay University Clay Uni - Enrich People Validate Email with Zero Bounce Validate Email with LeadMagic
Thanks! We've reopened this thread. You can continue to add more detail directly in this thread.