Hi all!
I followed this tutorial to get emails for my list. Once I pulled people’s names and added a ‘company website’ column, I noticed that for many people in my list, the company cell remained empty (even if when I manually check the person’s LinkedIn profile, I can find it). So, how do I get emails for those kinds of people on my list?
Once the list is built in clay - are there any other steps (like cleaning with email validation tools, elaborating on catch-all emails) still worth doing? If so, what workflow have you found effective?
Thank you!
I didn't completely understand this part, but if you have the persons's name + company website, you can find their email addresses without even enriching their profile. If the Find Email enrichment didn't return results for some of the rows, that's normal, as email finding tools can't find all emails - the best tools find emails for around 70% - 80% of the rows.
Yes, a DeBounce / NeverBounce email validation is a must to protect the health of your email accounts. If your TAM is big enough, a best practice is to not send emails to catch-alls. If your TAM is small and you want to validate catch-alls, you can use something like Scrubby to do this.
Here's a video on how to set up a waterfall in Clay to maximize coverage and minimize the amount of credits you spend by combining providers- https://www.clay.com/learn/find-work-emails-from-linkedin
yes, as long as you have company domain and full name its possible
got it thanks
Also, is there a way to pull some data (NOT all columns) to my table in Clay from another CSV that I have?
delete claygent as an option
For all of these you can actually use Clay credits. You must set up an API for the Claygent only. However, if you don't want to use that one, you can click on the Settings button and delete Claygent.
Only allows API key for this workflow
Hey Daria! It will import the available columns you have in your CSV, so if you don't want all of them, it's best to clean this up before downloading the CSV from the other source.Alternatively, you can still hide the columns once you finish the import into Clay. And, you do get the option to map columns if you're adding another CSV to that existing table, that's in case the headers don't match.