> ## Documentation Index
> Fetch the complete documentation index at: https://docs.peopledatalabs.com/llms.txt
> Use this file to discover all available pages before exploring further.
# PDLScores™ for Person Data
**General Availability**
PDLScores™ for Person Data are now generally available as of the **July 2026 Release (v35.0)**.
Early Access customers will retain access to scores and score factors through the rest of their Early Access period.
***
## Overview
PDLScores™ are generated scoring attributes available across PDL datasets.
There are two PDLScores™ (with supporting Score Factor objects) available for Person Data:
See the [Field Reference](#field-reference) below for a complete list of PDLScores™ and their associated Score Factors.
| Attribute | Description | Availability |
| ------------------------ | --------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ |
| `profile_score` | A bucketed signal indicating whether a profile appears to represent a real person | [Person Base](/docs/person-data-field-bundles#base) and [M\&A](/docs/person-data-field-bundles#ma-bundles) bundles |
| `profile_score_factors` | A set of supporting signals used to generate `profile_score` | [PDL Score Factors](/docs/person-data-field-bundles#pdl-score-factors) bundle |
| `activity_score` | A bucketed signal indicating whether a profile appears to be actively maintained | [Person Base](/docs/person-data-field-bundles#base) and [M\&A](/docs/person-data-field-bundles#ma-bundles) bundles |
| `activity_score_factors` | A set of supporting signals used to generate `activity_score` | [PDL Score Factors](/docs/person-data-field-bundles#pdl-score-factors) bundle |
Use **scores** when you want ready-to-use profile quality or activity signals. Use **score factors** when you want more transparency into the signals behind a score or want to build custom logic.
For field descriptions, value details, and examples, see the PDLScores™ section in the [Person Schema](/docs/fields#pdlscores).
## Availability
The `profile_score` and `activity_score` fields are included in [Person Base](/docs/person-data-field-bundles#base) and [M\&A](/docs/person-data-field-bundles#ma-bundles) bundles.
The `profile_score_factors` and `activity_score_factors` objects are available through the premium [PDL Score Factors](/docs/person-data-field-bundles#pdl-score-factors) bundle. This premium add-on bundle includes only the score factors, not the score fields themselves.
**Resume Slice Only**
PDLScores™ and their associated score factors are only available on records in the [Resume Slice](/docs/resume-stats) of the Person dataset. Profiles outside the Resume Slice return `null` for these fields.
***
## Common Workflows
Customers can use PDL Person Scores to:
* Filter or suppress low-signal profiles before ingestion
* Rank higher-confidence profiles first in search or matching workflows
* Route negative-signal profiles to manual review
* Improve entity resolution by using `profile_score` and `activity_score` as tiebreakers
* Prioritize outreach toward profiles that appear more active
* Reduce storage, compute, and maintenance costs associated with low-quality records
***
## Example Response
```json JSON theme={null}
{
"profile_score": "positive signals",
"profile_score_factors": {
"attribute_fill_rate": 0.625,
"profile_age_months": 110,
"has_valid_url": 1,
"meets_connection_threshold": 1
},
"activity_score": "neutral signals",
"activity_score_factors": {
"connection_change": 0.5,
"profile_change": 1,
"months_since_last_end_resume": 0
}
}
```
***
## Field Reference
| Field | Type | Short Description |
| :----------------------------------------------------------------------------------------------------------------------- | :-------- | :----------------------------------------------------------------------------------------------------------------- |
| [`profile_score`](/docs/fields#profile_score) | `String` | A PDL-generated signal indicating how likely a profile is to represent a real person |
| [`profile_score_factors`](/docs/fields#profile_score_factors) | `Object` | Supporting factors used to generate `profile_score` |
| [`profile_score_factors.attribute_fill_rate`](/docs/fields#profile_score_factorsattribute_fill_rate) | `Float` | The share of selected resume attributes present on the profile |
| [`profile_score_factors.profile_age_months`](/docs/fields#profile_score_factorsprofile_age_months) | `Integer` | The age of the profile in months, based on PDL's first observation of the trusted LinkedIn profile |
| [`profile_score_factors.has_valid_url`](/docs/fields#profile_score_factorshas_valid_url) | `Float` | A signal indicating whether the profile has a valid LinkedIn URL |
| [`profile_score_factors.meets_connection_threshold`](/docs/fields#profile_score_factorsmeets_connection_threshold) | `Integer` | A signal indicating whether the profile meets PDL's LinkedIn connection threshold |
| [`activity_score`](/docs/fields#activity_score) | `String` | A PDL-generated signal indicating how likely a profile is to be actively maintained |
| [`activity_score_factors`](/docs/fields#activity_score_factors) | `Object` | Supporting factors used to generate `activity_score` |
| [`activity_score_factors.connection_change`](/docs/fields#activity_score_factorsconnection_change) | `Float` | A signal indicating whether PDL has observed changes in the profile's LinkedIn connection count |
| [`activity_score_factors.profile_change`](/docs/fields#activity_score_factorsprofile_change) | `Integer` | A signal indicating whether PDL has observed user-edited profile changes recently |
| [`activity_score_factors.months_since_last_end_resume`](/docs/fields#activity_score_factorsmonths_since_last_end_resume) | `Integer` | The number of months since the profile's latest resume end date, when no active experience or education is present |