Hey Clay S., the DeBounce validate email integration is showing an error on some rows while it's working well for others. Any reason for why that's happening?
The DeBounce validate email integration may show errors on some rows while working well on others due to differences in the email addresses being processed. Common reasons include: ** Some emails may be invalid, misspelled, or formatted incorrectly, which causes the validation to fail for those specific rows. ** If you have enabled options like "Only 'Safe to Send' Emails" or "Exclude 'Free' Emails," certain addresses may be filtered out or marked as invalid based on DeBounce's classification. * The integration checks each email individually, so results can vary depending on the quality and type of each address in your data set. Review the specific error messages for more details, and consider checking your input settings or the affected email addresses for issues like typos or unsupported formats.
No, I want to talk to a human
Hi Tim, thank you for reaching out. The emails returned in the last column of a waterfall are by default already verified. As such, there is no need for an extra validation column at the end, you would essentially be double validating emails. However, if you still want to do this, I would be happy to take a look at your table. Tim - Do you mind sending the link (url) to the table so we can take a look?