Understanding predictive lead and account scoring
Predictive Lead and Account Scoring uses a tree-based (random forest/gradient boosting) machine learning method to build the predictive lead scoring model.
Administrators have the ability to configure multiple profile scoring goals, also referred to as models, one for each configured conversion event, allowing for separate scores to be generated for each configured goal.
Predictive lead and account scoring supports the following conversion goal types and fields:
Goal type | Fields |
---|---|
leadOperation.convertLead |
|
opportunityEvent.opportunityUpdated |
|
The algorithm takes the following attributes and input data into consideration:
- Person profile
XDM field | Required/ Optional |
---|---|
personComponents.sourceAccountKey.sourceKey | Required |
workAddress.country | Optional |
extSourceSystemAudit.createdDate | Required |
extendedWorkDetails.jobTitle | Optional |
sourceAccountKey.sourceKey
field in the Person:personComponents field group.- Account profile
XDM field | Required/ Optional |
---|---|
accountKey.sourceKey | Required |
extSourceSystemAudit.createdDate | Required |
accountOrganization.industry | Optional |
accountOrganization.numberOfEmployees | Optional |
accountOrganization.annualRevenue.amount | Optional |
- Experience Event
XDM field | Required/ Optional |
---|---|
_id | Required |
personKey.sourceKey | Required |
timestamp | Required |
eventType | Required |
Multiple models are supported, with the following hard limits set in place:
- Each production sandbox is entitled to five models.
- Each development sandbox is entitled to one model.
The data quality requirements are as follows:
- Ideally there is two year’s of most recent data for training purposes.
- The minimum length of data required is six months plus prediction window.
- For each prediction goal, at least 10 qualified conversion events are required.
Scoring jobs are run daily and the results are saved as profile attributes and account attributes, which can then be used in segment definitions and personalization. Out-of-the-box analytics insights are also available on the account overview dashboard.
See the documentation for more information about how to manage predictive lead and account scoring service.
View predictive lead and account scoring results
After the job run, the results are saved in a new system dataset for each model under the name LeadsAI.Scores
- the score name. Each score field group can be located at {CUSTOM_FIELD_GROUP}.LeadsAI.the_score_name
.
Attribute | Description |
---|---|
Score | The relative likelihood for a profile to achieve the predicted goal within the defined time frame. This value is not to be treated as a probability percentage but rather the likelihood of a profile compared to the overall population. This score ranges from 0 to 100. |
Percentile | This value provides information regarding the performance of a profile relative to other similarly scored profiles. Percentiles range from 1 to 100. |
Model type | The selected model type, indicates whether this is a person or account score. |
Score date | The date on which scoring occurred. |
Influential factors |
Predicted reasons on why a profile is likely to convert. Factors are comprised of the following attributes:
|
View customer profile scores
To view the predictive scores for a person profile, select Profiles under the customer section in the left panel, and then enter the identity namespace and identity value. Once finished, select View.
Next, select the profile from the list.
The Detail page now includes the predictive scores. Click the chart icon next to the predictive score.
A popup dialog shows the score, the overall score distribution, the top influential factors for this score, and the score goal definition.