You are here:
Anonymous and Known Profiles in Identity Resolution
A unified individual profile is considered known if any source profile was designated as known in the source data. A unified individual profile created only from anonymous source profiles is considered an anonymous unified profile. Account profiles are always known profiles.
If a source individual profile is identified later, an anonymous profile becomes a known profile. Unifying known and anonymous profiles creates richer unified individual profiles for use in segmentation and activation.
Suppose a Data Cloud org with a Customer Data Platform license has two rulesets based on the Individual data model object (DMO). The first ruleset created 8 million known profiles in the Unified Individual Main DMO. The second ruleset created 8.5 million known profiles and stored them in the Unified Individual Test DMO. All 16.5 million known profiles in both Unified Individual DMOs count toward the entitlement limit. Because your org is using rulesets, profiles in the Individual DMO aren't counted toward the entitlement.
The ID for the first ruleset is Main. The ID for the second ruleset is Test. These ruleset IDs appear in the object label and API name on the object that each ruleset outputs to.
| Object Label | Object API Name | Anonymous Profiles | Known Profiles |
|---|---|---|---|
| Individual | ssot_Individual__c | 3M | 10M |
| Unified Individual Main | UnifiedIndividualMain__dlm | 2M | 8M |
| Unified Individual Test | UnifiedssotIndividualTest__dlm | 2.5M | 8.5M |
| Account | ssot__Account__dlm | 1M | |
| Unified Account | UnifiedLinkssotAccount__dlm | 900,000 | |
| Other Record in Profile DMOs Categorized as Profile | CustomProfileDMO__dlm | 5M | |
| Total Counted Against Entitlement | 22.4M |
- Unify Anonymous and Known Individual Profiles Example
This example shows how known and anonymous individual profiles are unified.
