You are here:
Data Quality Calculated Insights: Contributing Contact Points
Review occurrences of repeat values for Contact Point Address, Contact Point Email, Contact Point Phone, and Party Identification objects. Use this calculated insight after data ingestion, but before creating an identity resolution ruleset.
Tip Improving data quality in your source data source improves unified profiles in
Data 360. To improve source data:
- 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.
DQ Source - Address Contact Point
Tip Modify the SQL in the example based on your data mappings.
SELECT
ssot__ContactPointAddress__dlm.ssot__AddressLine1__c AS AddressLine1__c,
ssot__ContactPointAddress__dlm.ssot__CityId__c AS CityId__c,
ssot__ContactPointAddress__dlm.ssot__CountryId__c AS CountryId__c,
APPROX_COUNT_DISTINCT( ssot__ContactPointAddress__dlm.ssot__PartyId__c ) AS unq_Individuals__c,
APPROX_COUNT_DISTINCT( ssot__ContactPointAddress__dlm.ssot__Id__c ) AS cnt_Occurances__c,
APPROX_COUNT_DISTINCT(ssot__Individual__dlm.ssot__FirstName__c) AS unq_FirstNames__c
FROM ssot__ContactPointAddress__dlm
LEFT JOIN ssot__Individual__dlm ON ssot__Individual__dlm.ssot__Id__c = ssot__ContactPointAddress__dlm.ssot__PartyId__c
GROUP BY
AddressLine1__c,
CityId__c,
CountryId__c
DQ Source - Email Contact Point
Tip Modify the SQL in the example based on your data mappings.
SELECT
ssot__ContactPointEmail__dlm.ssot__EmailAddress__c AS EmailAddress__c,
APPROX_COUNT_DISTINCT(ssot__ContactPointEmail__dlm.ssot__PartyId__c) AS unq_Individuals__c,
APPROX_COUNT_DISTINCT(ssot__ContactPointEmail__dlm.ssot__Id__c) AS cnt_Occurances__c,
APPROX_COUNT_DISTINCT(ssot__Individual__dlm.ssot__FirstName__c) AS unq_FirstNames__c
FROM ssot__ContactPointEmail__dlm
LEFT JOIN ssot__Individual__dlm ON ssot__Individual__dlm.ssot__Id__c = ssot__ContactPointEmail__dlm.ssot__PartyId__c
GROUP BY
EmailAddress__c
DQ Source - Phone Contact Point
Tip Modify the SQL in the example based on your data mappings.
SELECT
ssot__ContactPointPhone__dlm.ssot__FormattedE164PhoneNumber__c AS FormattedE164PhoneNumber__c,
APPROX_COUNT_DISTINCT(ssot__ContactPointPhone__dlm.ssot__PartyId__c) AS unq_Individuals__c,
COUNT(ssot__ContactPointPhone__dlm.ssot__Id__c) AS cnt_Occurances__c,
APPROX_COUNT_DISTINCT(ssot__Individual__dlm.ssot__FirstName__c) AS unq_FirstNames__c
FROM ssot__ContactPointPhone__dlm
LEFT JOIN ssot__Individual__dlm ON ssot__Individual__dlm.ssot__Id__c = ssot__ContactPointPhone__dlm.ssot__PartyId__c
GROUP BY
FormattedE164PhoneNumber__c
DQ Source - Party Identifier Contact Point
Tip Modify the SQL in the example based on your data mappings.
SELECT
ssot__PartyIdentification__dlm.ssot__PartyIdentificationTypeId__c AS Type__c,
ssot__PartyIdentification__dlm.ssot__Name__c AS Name__c,
ssot__PartyIdentification__dlm.ssot__IdentificationNumber__c AS Number__c,
COUNT(ssot__PartyIdentification__dlm.ssot__Id__c) cnt_Occurances__c,
APPROX_COUNT_DISTINCT(ssot__PartyIdentification__dlm.ssot__PartyId__c) unq_Individuals__c,
APPROX_COUNT_DISTINCT(ssot__Individual__dlm.ssot__FirstName__c) AS unq_FirstNames__c
FROM ssot__PartyIdentification__dlm
LEFT JOIN ssot__Individual__dlm ON ssot__Individual__dlm.ssot__Id__c = ssot__PartyIdentification__dlm.ssot__PartyId__c
GROUP BY
Type__c,
Name__c,
Number__c
Did this article solve your issue?
Let us know so we can improve!
