July 2021 Release Notes

Person v15.0 was released on 7/6/2021

​

Search API Changes

​

Index Mapping Changes

V15 (This Release)

We have changed the mapping of the job_title and experience.title.name fields in our search API index from text default, with an inner keyword mapping to keyword default with an inner text mapping. While we are seeing a high volume of customers make requests with job_title or experience.title.name in the search API, most of them are mistakenly treating the default mapping (text) as a keyword mapping, yielding fewer results than they intended.

V16 (October Release)

In October, we will be changing the mapping of all date fields to date type. This will allow range searches on dates, but should have minimal impact on search API users.

​

Tracking 0 Results as 404s instead of 200s

To avoid future confusion, search API results that return 0 records will now return a 404 response code instead of a 200

​

Changing the default de-duplication in the search API

Previously, any record in any of our datasets would be returned by default in the search API. This caused confusion due to the rate of duplication between datasets. We will now by default return records in the resume dataset, with a new parameter dataset that will let you expose data from the other datasets. See our Person Search API docs for examples.

​

Company Search API

In May we released our Company Search API, which allows you to find specific segments of companies that you need in order to power your projects and products. This product gives you direct access to query our full Company dataset. There are many degrees of freedom which allow you to find any kind of company with a single query. The company search API is now also available via our self-serve portal. We provide 100 free credits / month and tiered packages for purchase.

​

Data Field Changes

​

Person Schema

​

Freshness

This quarter, we made great strides in updating our datasets and have updated job titles for over 164mm of our global profiles and locations for over 74mm. We also updated jobs for 46mm of our United States profiles and locations for 25mm.

​

Coverage

We are continuing to make strides to link more PII to our core datasets. See some highlights below and click the links on each slice to see the full set of stats for each.

​

API Dataset

​

Resume Dataset

​

Street Address Dataset

​

Email Dataset

​

Commentary

• We improved linkages between work emails and LinkedIn profiles, this is one of our key initiatives in 2021.
• We increased our overall email coverage by ~30mm emails, adding 25mm profiles with emails
• We increased the granularity of locations in the resume set for ~45mm people, adding a postal_code
• We improved linkages between mobile_phone <> current address <> email significantly
• We doubled the number of profiles in the street address slice with interests

​

Improvements

• We now support name + postal_code matching in the person enrichment API for US postal codes. When inputting a postal code, it is assumed to be a US postal code. If you are using a non-US postal code, please include the country parameter.
• We improved error messaging for enrichment and search requests with invalid parameters to help with debugging.
• We improved name matching for our company enrichment API by making our fuzzy matching less strict. This should increase the recall of the API.
• We now allow requests using international phone numbers to start with either ‘+’ or ‘00’
• We increased our geocoordinate coverage for localities
• We no longer map “tech” to “technician” in job titles, avoiding erroneous mappings

​

Bug Fixes

• We fixed a bug with bulk enrichment API requests that ignored min_likelihood parameters within each request.
• We fixed a bug in our company cleaner API where we weren’t returning all companies
• We removed a set of invalid Linkedin URLs from our data
• We fixed merging issues for various locations
• We re-enabled a number of records erroneously tagged as bad records in our previous release

​

Pre-July 2021 Release Notice

​

Changes to the Search API

We are anticipating a few minor changes to our Person Search API which we wanted to give advanced warning about.

​

Index Mapping Changes

We will be changing the mapping of the job_title and experience.title.name fields in our search API index from text default, with an inner keyword mapping to keyword default with an inner text mapping. While we are seeing a high volume of customers make requests with title in the search API, most of them are mistakenly treating the default mapping (text) as a keyword mapping, causing them to get less results than they intend.

​

Tracking 0 Results as 404s instead of 200s

To avoid future confusion, search API results that return 0 records will now return a 404 response code instead of a 200

​

Changing the default de-duplication in the search API

Previously, any record in any of our datasets would be returned by default in the search API. This caused confusion due to the rate of duplication between datasets. We will now by default return records in the resume dataset, with a new parameter that will let you expose data from the other datasets.