This month, we are happy to report, RampedUp added 13,393,413 new contact records while updating 228,873,700 in total. That includes an additional 1,363,072 VALID and 8,908,120 professional email addresses overall. In terms of key consumer attributes, we added 223,200 mobile phones and 960,097 personal email addresses this month. Our additional sourcing efforts are paying dividends in terms of quantity and quality.
September’s Data Dictionary with Counts
The consumer attributes have received extra scrutiny this summer due to new privacy laws in California and New Jersey. As a reminder, these states have added extra layers of protection in terms of what data brokers can provide to their customers. So, while our additions this month are points of growth, they also abide by the latest regulations for these states.
That is one of the main reasons we are introducing data provenance for key consumer fields in the coming releases. While we have always provided provenance with social profile links and employer websites, we are going to go even further by providing the web source of email addresses and phone numbers when available. This practice will allow us to publish email addresses and phone numbers in certain locations that require a web source. But in areas without this requirement, this should give our customers greater confidence in RampedUp’s accuracy and legitimacy. More to come on this subject......
Lastly, we are going to update our website to be better identified as an authority by AI and Search Engines. Not that this will impact your service with us, but we are taking this opportunity to create a more comprehensive approach for our API endpoints, data counts, and privacy center. Instead of providing a link to our data dictionary on the website, the dictionary itself will be available on its own searchable page. The same is true of counts by country, industry, position, and title level. Every technology will be represented as well as a count engine for segments and categories. Also, look for practical use cases for each of our API end points and linkage to our schema on the site.