Customer says: "Tell us all the changes for this profile (what fields got updated) via a webhook. From our client's POV, who might do a yearly campaign, if we notify when new versions of data and what fields got changed, they might pay for re-enrichment. A webhook and field based changelog in 1 payload would be best." This renders the features on this card into an API https://peopledatalabs.canny.io/admin/feedback/feature-requests/p/id-changelog-person-data-split-files-by-etl-action-insert-update-delete-merge-op?boards=feature-requests&search=changelog%2520api

In phone array, show premium field for occurrence metadata i.e. : how many profiles does this number occur across these profiles. New Fields: *matching_phone_profiles: how many different profiles have this same phone. *matching_phone_full_name_profiles: how many different profiles have this same phone & full_name *matching_phone_company_profiles: how many different profiles have this same phone & also same job_company_name The idea is if a phone appears across 10 profiles, it's probably a company main phone number. If it occurs only 1-2 times, it's probably belongs to a single person.

Expand coverage in Japan and other countries like Korea and Singapore

When you invite a user to the PDL Dashboard that has a personal email, the only error message says, "Error occurred." A more verbose error message that informs the user they may only invite a user with a professional email would be preferential.

We've gotten feedback that phone number tagging similar to email tagging (personal/professional) would be helpful. In some cases, phone numbers that are displayed in the phone_numbers field are duplicated across profiles, especially when affiliated with a company, but it is difficult to disambiguate these at the individual profile level

API to fetch counts of results for a boolean query. Similar to https://www.elastic.co/guide/en/elasticsearch/reference/current/search-count.html . Currently, we are setting page_size parameter to 1 and getting the count of results and further narrowing down/ filtering with more boolean queries. This way multiple stages of credit consumption and filtering costs can be reduced.

We made 15,000 calls to API with the same parameters. Obviously, it was our bad, but would love detection so we might be alerted of obvious duplicate calls to a profile of say over x calls to the same API in a month.

Have ability to view whether companies added, updated, etc for each release i.e. an ID Changelog for company data.

Include generic business phone numbers associated with the person's current role.

When using the autocomplete API, enable historical and alternative names to appear as optional results in the return