--- schema_version: "1" id: 95390083237520d901c6b1423931d2b341a8668eec24711cc5e03c32684c17fa title: Data 360 Profiles License Billing Considerations collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/data/264-0-0/c360_a_d360_profile_billing_considerations.md canonical_url: https://help.salesforce.com/s/articleView?id=data.c360_a_d360_profile_billing_considerations.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 594c5014dc1e80f0ad05f300639a409ad8cc88eefd03fdab7b9dde119bcc8631 description: Adding a Data 360 Profile or Data 360 Enterprise Profile license to a Data 360 org changes its consumption billing and adds limits for certain features. products: - Data 360 release: "264" --- # Data 360 Profiles License Billing Considerations Adding a Data 360 Profile or Data 360 Enterprise Profile license to a Data 360 org changes its consumption billing and adds limits for certain features. All limits associated with Data 360 Profiles licenses apply to the production Data 360 home org and its connectioned Data Cloud One companion orgs collectively. Sandbox orgs created from the Data 360 home org inherit the home org's limits. Limits apply to the sandbox org and its connected companion orgs collectively. To review limits for orgs with Data 360 Profiles licenses, see [Data 360 Profiles License Base License Limits](https://help.salesforce.com/s/articleView?id=data.c360_a_limits_and_guidelines_d360_profiles.htm&release=264.0.0&type=5 "Limits in this document represent the base limits of a single Data 360 Profiles or Data 360 Enterprise Profiles license. Some limits can be raised by purchasing multiple copies of the license or buying add-on licenses."). ## Profiles The number of profiles included in your Data 360 org cluster is based on how many Data 360 Profile licenses you purchase. If you exceed your profile entitlement, you’re charged at your overage rate. For production orgs, if identity resolution is active in a data space, the count of profiles in each data space 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. If identity resolution isn’t active, 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, excluding certain DMOs. For sandbox orgs, the same counting logic applies, but the total number of profiles counted toward the limit is 80% of the sum of all profiles in all data spaces on the sandbox org. For a more detailed explanation of how profiles are counted, see [Data 360 Profiles License Billable Profiles Calculations](https://help.salesforce.com/s/articleView?id=data.c360_a_d360_profiles_billable_profile_calcs.htm&release=264.0.0&type=5 "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."). ## Identity Resolution Rulesets Credits aren’t consumed by the Batch Profile Unification or Data 360 Unification usage types when identity resolution runs. ## Data Transforms Credits aren’t consumed by the Batch Data Transforms or Data 360 Prep usage types, but the total number of active batch data transforms in your Data 360 org cluster is limited. For production orgs, the number of batch data transforms counted toward the limit is the sum of all data transforms in all data spaces on the home production org. For sandbox orgs, the number of batch data transforms counted toward the limit is the sum of all data transforms in all data spaces on the sandbox org. ## Calculated Insights Credits aren’t consumed by the Batch Calculated Insights or Data 360 Prepusage types, but the total number of active batch calculated insights in your Data 360 org cluster is limited. For production orgs, the number of batch calculated insights counted toward the limit is the sum of all calculated insights in all data spaces on the home production org. For sandbox orgs, the number of batch calculated insights counted toward the limit is the sum of all calculated insights in all data spaces on the sandbox org. ## Segmentation Credits aren’t consumed by the Segmentation or Data 360 Segmentation usage types, but the total number of active segments (including standard, waterfall and real-time types) in your Data 360 org cluster is limited. For production orgs, the number of segments counted toward the limit is the sum of all segments in all data spaces on the home production org and all segments in all data space on all connected Data Cloud One Companion orgs. For sandbox orgs, the number of segments counted toward the limit is the sum of all segments in all data spaces on the sandbox org. ## All Other Features **Activations:** Credits aren’t consumed by the Batch Activation Data 360 Activation usage types, but the total number of active batch activations on DMOs in your Data 360 org cluster is limited. Streaming DMO activations consume credits. **Data Ingestion:** Credits aren’t consumed when data is ingested via an internal data pipeline from a Salesforce org or via a batch data connection from an external source. Streaming data ingestion consumes credits. **Zero Copy Data Federation:** Data federation via live queries and data federation via file federation don’t consume the Data Federation or Sharing Rows Accessed usage type. This usage type is still consumed by data sharing. Data federation with acceleration doesn’t consume the Batch Data Ingestion usage type. **AI Inferences:** AI inferences don’t consume the Inferences usage type. **Data transforms, identity resolution, insights, and segments:** These features continue to consume supplementary usage types listed in their Billing Considerations, such as Data Queries and data storage. **All Other Features:** All other features continue to consume credits at the regular rates as referenced in the [Data Services Billable Usage Types for Data 360](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.")and the features’ Billing Considerations. - **[Data 360 Profiles License Billable Profiles Calculations](https://help.salesforce.com/s/articleView?id=data.c360_a_d360_profiles_billable_profile_calcs.htm&release=264.0.0&type=5)** 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. #### 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.")