You are here:
Data Services Billable Usage Types for Data 360
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 Servuces 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.
In Digital Wallet, Data 360 consumption for customers with Data Services is tracked on the following consumption cards.
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.
Data Service Usage
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.
| Billing Category | Description |
|---|---|
| Internal Data Pipeline | Usage is calculated based on the number of rows of structured data ingested from Salesforce via the Salesforce CRM connector, Marketing Cloud connector, Commerce Cloud connector, and Marketing Cloud Personalization connector. As of August 7, 2025, usage of this type is included with Data 360 and doesn't consumes credits. For details, see Ingest Salesforce Data into Data 360 for Free |
| Batch Data Pipeline (External Data Pipeline) | Usage is calculated based on the number of rows batch data processed by Data 360 data streams across all connectors, with the exception of structured data ingested via the Internal Data Pipeline. |
| Streaming Data Transforms | Usage is calculated based on the number of records processed. |
| Batch Data Transforms | Usage is calculated based on the higher of the number of rows read or number of rows written. For incremental batch data transforms, after the first time a transform runs, usage is based on the number of rows that have changed since the previous run. |
| Streaming Data Pipeline (External Data Pipeline) | 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 ingested via the Internal Data Pipeline. Data streams that report usage with this usage type include streams created by the Website and Mobile App connector and streaming ingestion API. |
| Unstructured Data Processed | Usage is calculated based on the amount of unstructured data that is processed. 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 360, 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. |
| 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 Share Rows Shared (Data Out) | Usage is calculated based on the total number of records processed when you first create a data share and link to a data share target. This applies only to the initial full batch of data; subsequent incremental changes don't count toward this usage type. For data sharing between Data 360 orgs, this usage type isn’t applicable to the source org. |
| Data Federation or Sharing Rows Accessed | For data federation, usage is calculated based on the number of records retrieved from the source. For a data share, usage is calculated based on the number of rows returned to fulfill an external data lake’s request. For data sharing between Data 360 orgs, this usage type applies to the target org for all queries. For external data shares, this usage type applies only to cross-cloud and cross-region queries. There’s no credit consumption if the query originates from the same region and the same cloud. |
| Private Connect Data Processed | Usage is calculated based on the volume of data in GBs that are transferred over the private network route. This applies to the transfer of data into Data 360 and the transfer of data to an external data source. |
| Batch Profile 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. |
| Sub-second Real-Time Events & API | 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 and real-time ingestion API, including web and mobile SDKs traffic. 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. |
| 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. |
| Streaming Calculated Insights | Usage is calculated based on the number of records processed. |
| Inferences | Usage is calculated based on the number of unique inferences produced by a predictive model. A single inference includes one prediction and, optionally, one or more prescriptions and one or more top predictors. Inferences are consumed for any predictive AI model used, whether internal (built in Einstein Studio AI) or external (Bring Your Own Model). |
| Data 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. |
| Streaming Actions (including lookups) | Usage is calculated based on the number of records processed. A lookup is an enrichment from a related object. |
| Segmentation | Usage is calculated based on the number of records processed. |
| Batch Activations | Usage is calculated based on the number of records processed. |
| Activate DMO - Streaming | 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. |
| 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. |
| Accelerated Data Queries | As of August 16, 2024, usage is no longer billed to this category. |
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. |
Segmentation and Activation
As of September 4, 2025, this consumption card is no longer in use. Usage consumed by the Segmentation, Batch Activations, and Activate DMO - Streaming usage types after September 4, 2025 is recorded against the same usage types on the Data Services card.
| Billing Category | Description |
|---|---|
| Segmentation | Usage is calculated based on the number of records processed. |
| Batch Activations | Usage is calculated based on the number of records processed. |
| Activate DMO - Streaming | 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. |
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. |
Data 360 Real-Time Profiles
Service usage calculations for real-time service is based on the number of records associated with real-time data graphs.
| Billing Category | Description |
|---|---|
| Sub-second Real-Time Profiles & Entities | Usage is calculated based on the total number of unique real time data graph records (Profiles for users) that appeared in real time record cache during the billing month. Even if a single unique record appears more than once, it’s only counted once. For example, if a real-time data graph’s primary data model object has 10 million rows cached on the first day of the month, and 1 million unique records are added to the real time cache daily for 30 days, the total count is 40 million. |
