Wavelength has very accurate data. Wavelength matches ~70% of email addresses that it receives with enriched data (e.g. career, location, social profiles). 90-95% of the enriched data is accurate.
How Wavelength gets data
Wavelength works with data aggregators to search for available information about constituents. We connect with them via API and pay to get the data they find. In our API call, we send as many fields as we can about an individual so that we have the highest confidence in getting the right person.
Using just "Chris Gibson" will return many generic results. We send along more information like email address, name, location, and gender.
Read more about how Wavelength's data aggregators work in Where does Wavelength Data come from.
Wavelength's Data Accuracy
When acquiring this data, Wavelength can set a minimum confidence level required to consider it matched. Wavelength sets its confidence level at the strictest setting and throw out all other results.
All that being said, Wavelength doesn't have 100% accuracy. Wavelength finds up to 5% of profiles matched might have incorrect data. If data quality is ever a concern, Wavelength can use manual methods to improve it.
How Wavelength Communicates to Alumni about Data
During onboarding, Wavelength communicates to people where we get the data, how we get the data, acknowledge that it may not be 100% correct, and ask them to update it.
We have spoken to actual alumni on our product about our data quality / messaging. They think we handle data well and understand where their data is coming from. They also haven't raised concerns about the 5% inaccuracies.
All users with enriched data will see an enrichment card on their profile:
The "Learn More" button communicates how we got the data in-depth. For those people interested in getting their data off public sources, they can download the Data Removal Workbook. This will teach them privacy best practices on other platforms.
Want to read more about Wavelength and Data? Read our Data Polices, Privacy Policy, and Terms of Service.
Comments
0 comments
Article is closed for comments.