---
schema_version: "1"
id: a01f916ee100f091c1d4ef616c238a708060b7ae2535fec98b881739877a3364
title: "Identity Resolution Calculated Insight: Outlier Unified Profiles"
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/data/264-0-0/c360_a_resolution_troubleshooting_ci_outlier_unified_profiles.md
canonical_url: https://help.salesforce.com/s/articleView?id=data.c360_a_resolution_troubleshooting_ci_outlier_unified_profiles.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: b1ed14ec89e757b36d5150a1a64a30e84c7b986c4dba8f2c5e9bc9557231917f
description: Review the number of matched contact points for each unified profile. A high number of matches per contact point, like profiles with hundreds of source records matched with the same email address, could indicate issues with data quality or source data. Use this calculated insight after creating unified profiles with an identity resolution ruleset.
products:
  - Data 360
release: "264"
---
# Identity Resolution Calculated Insight: Outlier Unified Profiles

Review the number of matched contact points for each unified profile. A high number of matches per contact point, like profiles with hundreds of source records matched with the same email address, could indicate issues with data quality or source data. Use this calculated insight after creating unified profiles with an identity resolution ruleset.

![Tip](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-data-data_cloud-264-0-0-production-enus/f3569962-3c9b-4f83-9d0c-b6a574e785da/images/icon_tip.png)

Tip

- Use this calculated insight for multiple rulesets by creating a calculated insight for each Unified Data Model Object (DMO).
- To search for outlier profiles in Profile Explorer, use the Unified\_Individual\_Id from the calculated insight.
- Consider removing repeat values from your source data and ingesting data into Data 360 again.
- Consider filtering out repeat values using a formula field in Data Streams.

![Unified Individual - CP Summary](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-data-data_cloud-264-0-0-production-enus/f3569962-3c9b-4f83-9d0c-b6a574e785da/images/icon_example.png)

Unified Individual - CP Summary

![Tip](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-data-data_cloud-264-0-0-production-enus/f3569962-3c9b-4f83-9d0c-b6a574e785da/images/icon_tip.png)

Tip Modify the SQL in the example based on your data mappings.

```sql
SELECT
 UnifiedIndividual__dlm.ssot__Id__c AS Unified_Individual_Id__c,
 APPROX_COUNT_DISTINCT(IndividualIdentityLink__dlm.SourceRecordId__c) AS cnt_Lineage__c,
 APPROX_COUNT_DISTINCT(ssot__Individual__dlm.ssot__FirstName__c) AS unq_FirstNames__c,
 APPROX_COUNT_DISTINCT(UnifiedContactPointPhone__dlm.ssot__Id__c) AS unq_PhoneCPs__c,
 APPROX_COUNT_DISTINCT(UnifiedContactPointEmail__dlm.ssot__Id__c) AS unq_EmailCPs__c,
 APPROX_COUNT_DISTINCT(UnifiedContactPointAddress__dlm.ssot__Id__c) AS unq_AddressCPs__c,
 APPROX_COUNT_DISTINCT(ssot__PartyIdentification__dlm.ssot__Id__c) AS unq_PartyIdentifiers__c
FROM UnifiedIndividual__dlm
 LEFT JOIN  IndividualIdentityLink__dlm ON IndividualIdentityLink__dlm.UnifiedRecordId__c = UnifiedIndividual__dlm.ssot__Id__c
 LEFT JOIN  UnifiedContactPointPhone__dlm ON UnifiedContactPointPhone__dlm.ssot__PartyId__c = UnifiedIndividual__dlm.ssot__Id__c 
 LEFT JOIN  UnifiedContactPointEmail__dlm ON UnifiedContactPointEmail__dlm.ssot__PartyId__c = UnifiedIndividual__dlm.ssot__Id__c 
 LEFT JOIN  UnifiedContactPointAddress__dlm ON UnifiedContactPointAddress__dlm.ssot__PartyId__c = UnifiedIndividual__dlm.ssot__Id__c 
 LEFT JOIN  ssot__PartyIdentification__dlm ON  ssot__PartyIdentification__dlm.ssot__PartyId__c = UnifiedIndividual__dlm.ssot__Id__c 
 LEFT JOIN  ssot__Individual__dlm ON  ssot__Individual__dlm.ssot__Id__c =  IndividualIdentityLink__dlm.SourceRecordId__c
GROUP BY 
 Unified_Individual_Id__c
```