--- schema_version: "1" id: 6df34bedd5972ba5b19707cb1d35c9f628edde7f25d56c74058a19159317ceb3 title: Data 360 Profiles License Billable Profiles Calculations collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/data/264-0-0/c360_a_d360_profiles_billable_profile_calcs.md canonical_url: https://help.salesforce.com/s/articleView?id=data.c360_a_d360_profiles_billable_profile_calcs.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: ff0c00e0525a60f3f1f25c2d652f6a58cd6669ee4a3710e388f23eb9b58cea5a description: In orgs with a Data 360 Profiles license, the billable number of profiles is based on whether you have active Identity Resolution rulesets. You’re billed at your overage rates for additional profiles if the number of billable profiles exceeds your entitlement. products: - Data 360 release: "264" --- # Data 360 Profiles License Billable Profiles Calculations In orgs with a Data 360 Profiles license, the billable number of profiles is based on whether you have active Identity Resolution rulesets. You’re billed at your overage rates for additional profiles if the number of billable profiles exceeds your entitlement. ## Counting Profiles in Data Spaces with Active Identity Resolution Rulesets If you’re using identity resolution to link source profiles to Unified Profiles, the billable unified profile count is the sum of your known unified profiles, 4% of your anonymous profiles, and the total number of records in all DLOs mapped to DMOs categorized as Profile that aren’t used by identity resolution. - **Known Unified Profiles:** The number of known Unified Profile records output by active identity resolution rulesets. To determine how many known Unified Profile records you have, view the Identity Resolution Summary for each active ruleset. Add the number of known Unified Profiles across all active rulesets. - **Anonymous Unified Profiles:** 4% of the number of anonymous unified profile records output by active identity resolution rulesets. To calculate this number, view the Identity Resolution Summary for each active ruleset. Multiply the number of anonymous profiles by 0.04. Add the number of anonymous unified profiles across all active rulesets. - **Ununified Source Profiles:** The number of all records in all DLOs, regardless of category, that are mapped to DMOs categorized as Profile, excluding Unified data model objects (Unified DMOs) output by an identity resolution ruleset. ## Counting Profiles in Data Spaces without Active Identity Resolution Rulesets In a data space that isn’t using identity resolution, the billable profile count is the sum of all records in all data lake objects (DLOs), regardless of category, mapped to data model objects (DMOs) categorized as Profile type. Both known and unknown profile records are counted. DLOs that are mapped only to the following DMOs are excluded from this count. - Account Contact - Contact Point Address - Contact Point App - Contact Point Consent - Contact Point Email - Contact Point OTT Service - Contact Point Phone - Contact Point Social - Device - Party Identification ![Example](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) Example Suppose your org has two identity resolution rulesets: Unified Individual.1 with 10,000 records and Unified Individual.2 with 8,000 records. There are also two DLOs that are categorized as Profile and mapped to other DMOs that are categorized as Profile: the Account DLO has 2,000 records, and the Custom DLO has 5,000 records. For this customer, the total billable Unified Profiles is 10,000 + 8,000 + 2,000 + 5,000 = 25,000. ## Factors That Affect Unified Profile Counts Address these factors to ensure that your profile counts accurately reflect your business needs. **Multiple Identity Resolution Rulesets** Unified profile counts from all active identity resolution rulesets are used to calculate total billable known and anonymous profiles. Validate the number of active identity resolution rulesets. If more than one is active, determine if all are needed for an active business purpose. **Data Stream Growth** As you connect different source systems to Data Cloud and increase the volume of data ingested through new data streams, the number of source profiles increases. Review all data streams and sources categorized as Profile. Determine if any duplicate, dev, test, or staging sources are connected and whether they’re still needed. **Data Model Object Category** Data lake objects (DLOs) mapped to data model objects (DMOs) that are categorized as Profile are available to segment on and are included in the Unified Profile count. Review all mappings from DLOs to DMOs. Determine if all data streams mapped to DMOs categorized as Profile contain a population that you want to segment by or use as the starting population for a segment. Determine if any DMOs are categorized incorrectly as Profile. If a DMO is categorized incorrectly as Profile, you can change its category to Other. You can change a DMO’s category only if it isn’t used in segmentation or activation. Delete all segments and activations that use the DMO before changing the category from Profile to Other. See [Change the Category of a Data Model Object](https://help.salesforce.com/s/articleView?id=data.c360_a_change_data_model_object_category.htm&release=264.0.0&type=5 "In most cases, a data model object’s category can’t be changed after the object is created. The category can be changed only if it’s changing from Profile to Other or from Other to Profile on an object that isn’t used in segmentation or activation."). **Additional Unified Profile Count Considerations** - Records in a DLO that is included in multiple data spaces are only counted once. The number of records in the source DLO is counted, regardless of how many records are included in data space-specific views of the DLO. - Data created from a transform that is output as an unmapped DMO isn’t counted toward billable Unified Profiles. If a DLO isn’t mapped, it doesn’t count. - A DLO that is mapped to the Individual DMO and also to a DMO of type Profile isn’t counted twice. - All DLOs that are mapped to a DMO with type Profile count toward billable Unified Profiles. This count includes these scenarios. - Data streams outside of identity resolution counts - Consent DMOs outside of identity resolution counts - Data transform or stream transform DLOs mapped to DMOs of type Profile outside of identity resolution counts #### See Also - [_Salesforce Help_: Data 360 Billable Usage Types](https://help.salesforce.com/s/articleView?id=data.c360_a_data_usage_types.htm&release=264.0.0&type=5 "Usage of certain Data 360 features impacts credit consumption. If you purchased credits before February 24, 2026, your org consumes Data Services credits for Data 360 services. Orgs purchasing or renewing after February 24, 2026 can have either Data Services or Flex Credits. To monitor your usage in these Data Services usage categories, access your org’s Digital Wallet. If your org has a Data 360 Profiles-type license, some usage types aren't consumed. For more information on how usage is billed, refer to your contract or contact your account executive.")