Data 360 Profiles License Billing Considerations

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 the total number of known unified profiles, the total number of anonymous unified 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.

Identity Resolution Rulesets

Credits aren’t consumed by the Batch Profile Unificiation 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 360and the features’ Billing Considerations.