We had a tremendous amount of contact updates in April. This month, 430,398,739 contacts were updated and 5,323,351 were flagged as a recent_job_change. Our multi-sourced efforts are paying off as we increased the number of professional email addresses by 1,633,848 and mobile phones by 501,741.
Full details can be downloaded here within our Data Dictionary.
We have also made significant progress identifying inactive contacts in the dataset. We did not delete these records as they have a distinct LinkedIn URL, however, they are flagged with the contact_active_ru_id field pointing to the active ruid. The active contact was chosen based on several factors like the most recent updated date, most recent job start date, number of connections and if record has been flagged as contact_linkedin_url_is_inactive (records with a LinkedIn URL that has a 404 response.)
We recommend that you merge the duplicate records out of your system with the ruid in contact_active_ru_id field. That is what we did within our own application. Out of the 925,027,354 records we are delivering this month, 831,004,920 are available in the app.
Speaking of the app we have made the following updates:
- When a user selects Local Office Required in Contact List Building, the system will limit the search results to records that have Address / City / State / Postal Code / Country populated in the Local Office fields. Local Office data is populated with the contact’s location is within the same metro area as the employer’s Headquarters or Branch office.
- Contact RUID is now an option for Data Appending in the API and the User Interface. The use case being that you can now use our unique ID instead of other fields like email address.
- We are adding Funding to our company database. The search criteria within our interface allows a user to limit results by funding stage, round, amount, and date. This data will be exposed in separate fields in the CSV download along with the investors that participated in the funding event.
Lastly, we are researching the feasibility of adding subsidiary as an entity_type in the company data. Currently we have two entity types, parent and affiliate. Affiliates share the same root_domain and the parent is selected based on the highest employee_count and social_followers. The subsidiary will be identified based on a corporate hierarchy available on public records, company websites, and social media pages. We will also purpose our own alerts intelligence when we receive mergers and acquisitions notifications.
Funding and M&A are two of the fields we monitor for Company Alerts. You can search for this data in the Real-Time alerts database or sign up for daily notifications.