You are here:
Flex Credits Billable Usage Types for Data 360
Usage of certain Data 360 features impacts credit consumption. To monitor your usage in Flex Credits 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.
Review your org’s licenses and Digital Wallet to determine how your org is billed.
- If your org operates Data 360 under a Customer Data Platform license, refer to Customer Data Platform Billable Usage Calculations instead.
- If your org operates under a Data Cloud license and has an active Data Services consumption card, refer to Data Services Billable Usage Types for Data 360 instead. If you also have a Data 360 Profiles license, some usage is unmetered. Refer to Data 360 License Billing Considerations for details.
- If your org operates Data 360 under a Data Cloud license but doesn’t have an active Data Services consumption card, this article describes how credits are consumed.
The number of credits consumed is based on the number of units of each usage type used multiplied by the multiplier listed on the rate card for the usage type.
Actual usage is summed for each usage type and credits are decremented at a fractional rate. The minimum number of credits decremented from a usage type is 1, where fractional usage amounts to 1 or more credits over the monthly billing period.
Data 360 Profiles Licenses
If a Data 360 Profiles or Data 360 Enterprise Profiles license is added to your Data 360 org, some features stop consuming credits. Refer to Data 360 Profiles License Billing and Limits for more details or review the feature’s Billing Considerations article.
Flex Credits Usage Types for Data 360
Service usage calculations are based on records processed, queried, or analyzed. Service usage applies to Data 360, Data 360 for Marketing, and Data 360 for Tableau customers.
In Digital Wallet, Data 360 consumption for customers with Flex Credits is tracked on the Flex Credits consumption card in the following usage types.
| Billing Category | Description |
|---|---|
| Data 360 Prep | Usage is calculated based on the data object type. For local data lake objects and data model objects, the number of rows used for billing calculations is limited to the number of rows in the object. For external data lake objects, the actual count of rows read or written is used. This number can exceed the number of rows in the object if an object’s rows are read multiple times in a single transform run. For incremental batch transforms, after the first time a transform runs, usage is calculated based on the number of rows that changed since the previous run. For batch calculated insights, usage is calculated based on the number of records in all underlying objects used in creating the Calculated Insight each time it runs. |
| Data 360 Unification | Usage is calculated based on the number of source profiles processed by an identity resolution ruleset. After the first time a ruleset runs, only new or modified source profiles are counted. A source profile is an individual and their related records, such as contact points and party identifiers, which are included in the identity ruleset. For example, modified means deleted profiles, or profiles marked as suppressed via Consent API preferences. |
| Data 360 Segmentation | Usage is calculated based on the number of records processed by a Data 360 segment. |
| Data 360 Activation | Usage is calculated based on the number of records processed for a Data 360 activation. |
| Data 360 Zero Copy Sharing-Out | Usage is calculated based on the number of rows returned to fulfill an external data lake’s data share request. The number of rows accessed depends on the structure of the query and isn’t the same as the number of rows in the source data. For data sharing between Data Cloud orgs, this usage type applies to the target org for all queries. Data 360 is hosted only on Amazon Web Services (AWS) across multiple AWS regions. Same region is when Data Cloud and the data share target are hosted in the same AWS region. Same cloud is when Data Cloud and the data share target are hosted on the same cloud. |
| Data 360 Queries | Usage is calculated based on the number of records processed. The count of records processed depends on the structure of a query as well as other related factors such as the total number of records in the objects being queried. When an object is queried in the context of a data space, the number of rows processed is based on the total number of processed rows in the source object, not the number of rows pertaining to the particular data space |
| Data 360 Unstructured Processing | Usage is calculated based on the amount of unstructured data that is processed without using AI assisted content processing and extraction. For example, if the search index processes 100 PDF documents that are 1 MB each, usage is calculated as 100 MB. If the search index processes five audio/video files that are on average 100MB each, usage is calculated as 500MB. In Data Cloud, unstructured data may be chunked and vectorized using an embedding model. Usage is computed only once across both these activities. For example, if one 100 MB PDF document is chunked and vectorized, usage is computed as 100 MB, not as 200MB.If you create a search index that uses a data model object (DMO) as a data source and select Text data type fields from the DMO, all strings from those fields are indexed and the sum total of all bytes processed is reported as Unstructured Data Processed. |
| Data 360 Intelligent Processing | Usage is calculated based on the amount of unstructured data that is processed using AI-assisted features such as LLM-based parsing, LLM-based visual data preprocessing, image processing, and Intelligent Context. |
| Data 360 Streaming Pipeline | Usage is calculated based on the data object type. For streaming data ingestion, usage is calculated based on the number of rows of streaming data processed by Data 360 across all data streams with stream processing, with the exception of structured data that is ingested via the Internal Data Pipeline. Data streams that report usage with this usage type are streams created by Website and Mobile App Connector and streaming ingestion API. For streaming data transforms and streaming calculated insights, usage is calculated based on the number of records processed. For streaming data actions, usage is calculated based on the number of records processed in the DMO. Records processed are based on the number of new records created or updated in the DMO per activation. If a data graph is being used with the activation, the number of records processed will be doubled in the final calculation. For example, when a data graph is being used with the activation, if there is 1 new record change in the DMO, this will count as 2 records processed. |
| Data 360 Real-Time Pipeline | Usage is calculated based on the sum of the number of profile events, engagement events, API calls, and data actions processed in the sub-second real-time layer, including web and mobile SDKs traffic and real-time ingestion API. Profile events, engagement events, API calls, and data actions are processed in the real-time layer if they are associated with a real-time data graph. For example, if 3 profile events, 10 engagement events, 20 API calls, and 5 data actions are processed during a particular billing period, the total processed is 38. |
| Data 360 Code Extension | Usage in this type is measured in Compute Units. The number of Compute Units consumed per hour depends on the compute size selected. The total number of Compute Units is calculated based on the hourly consumption rate and the total compute time your code consumes. |
For information about Flex Credits fuselage types or Agentforce and Speech Foundations, see Flex Credits Billable Usage Types for AI.
To review current and historical standard rates and multipliers, see Data 360 Multipliers. Review your contract to determine your contracted rates.
Data Storage Allocation
Storage refers to the amount of data stored in Data 360. Storage used outside of Data 360, such as data stored on the Salesforce Lightning Platform, isn't counted toward this limit. Storage usage applies to Data 360, Data 360 for Marketing, and Data 360 for Tableau customers.
| Billing Category | Description |
|---|---|
| Storage Beyond Allocation | Usage is calculated based on the amount of storage used above the amount allocated. |
Data Spaces
Data space usage applies to Data 360, Data 360 for Marketing, and Data 360 for Tableau customers.
| Billing Category | Description |
|---|---|
| Data Spaces | Usage is calculated based on the number of data spaces beyond the default data space. |
Ad Audiences Service Usage
Service usage calculations for ad audiences are based on the number of audiences.
| Billing Category | Description |
|---|---|
| Ad Audiences | Usage is calculated based on the number of ad audience targets. |
