LaGrowthMachine automatically enriches your leads' contact info. By enrichment, we mean “identifying the prospect’s contact information”.
Depending on the audience, LaGrowthMachine will automatically enrich and verify 10-25% of Twitter handles.
How does the magic happen? Read-on!
Table of contents :
Finding Twitter accounts from imports from LinkedIn using Visit & Enrich.
When Leads enrichment is enabled, your identity will visit the lead and extract contact information.
Did you know that you could list your Twitter account in your contact information on LinkedIn? This is the first source of Twitter contact information.
If the prospect doesn’t list any Twitter account on their LinkedIn profile, LaGrowthMachine will automatically do a search on Twitter using the first name + last name + company name.
If there is a match, we return it :)
Lots of people list their Twitter handle on LinkedIn - if they do, we fetch it.
If they don’t, we do a search on Twitter to see if an account matching their contact info exists.
Finding Twitter Accounts from CSV Imports using Visit & Enrich.
Wait, what if I import data from my CRM, and I don’t have the Linked URL?
Fear not, we have you covered as well :
If your CSV contains Firstname + Lastname + CompanyName, LaGrowthMachine will automatically do a search on LinkedIn to find their LinkedIn profile.
For more information on how we automatically find LinkedIn Profiles from import, refer to this article.
If we find it, we loop back to the process above.
If we don’t, we still have enough information to give it a try, namely first name, last name, and company name
You’re only going to be missing LinkedIn as a channel :)
If your CSV is up to date, LaGrowthMachine will match about 80% of your LinkedIn Profile. The remaining 20% are because :
They might have changed jobs. If they do, we won’t provide the LinkedIn Profile
We might have to find homonyms, and we don’t know who to select
LaGrowthMachine doesn’t share contact information across users
Some smart folks told us “Wait, automating for so many people, you must have a great database with people’s contact. Why not use it?”. Well, we don’t and we won’t.
Here’s why we don’t share contact information across users :
This is not very GDPR compliant - in everything we do, we do our best to offer a GDPR compliant approach to enriching contacts
Your information is proprietary, and you probably don’t want to share it. While when you’re using solutions such as Kaspr, Lusha or Prospectin, information will be shared across users, we believe your competitor shouldn’t be able to benefit from your own research.
It’s better to have a transparent approach as to how you got that data.
Sometimes, you will have prospects asking “How did you get my email? How did you get my phone number?” (insert angry tone).
You’ll have it an easier time defusing the bomb by explaining that their email server configuration allows you to test it, or that you’re connected with them on LinkedIn and that’s how you got his phone numbers
This safe and sound approach means we have a slightly lower enrichment rate than solutions that do not respect GDPR and privacy guidelines, but we believe it’s better this way.