When you use Salesforce Catalog, you process unstructured data and search index configurations in Data 360. Use of Salesforce Catalog with Data 360 impacts the consumption of credits in these usage types.
Use Digital Wallet to check which consumption cards are active in your org, find out how many credits are available on each card, and determine how many credits have been consumed in each usage type.
Some usage types aren’t metered for certain licenses or editions, such as a Data 360 Profiles license or Agentforce 1 Edition. Check your licenses and review license documentation for more information.
Unstructured data processing features such as search index are not available for orgs operating Data 360 under the Customer Data Platform (CDP) license.
Data 360 Usage
When you use Data 360 for data collection and processing, your org consumes credits from either the Data Services consumption card or the Flex Credits consumption card.
- If your contract included Data Service Credits, those are consumed for all Data 360 usage.
- If you run out of Data Service Credits, your org is billed at your Data Service Credit overage rate for the remainder of your term unless more credits are added.
- If you have Flex Credits for Data 360, those credits are consumed instead.
Data Services and Flex Credits organize data services within different usage type groupings. For more information, see Data Services Billable Usage Types for Data 360 and Flex Credits Usage Types for Data 360. To check multipliers for each usage type, see the Multipliers for Data Services Rate Card or the Agentforce & Data 360 Flex Credits Rate Card. The cost of each credit is determined by your contract.
| Digital Wallet Card Consumption Card | Usage Type | Usage Type Description | Notes |
|---|---|---|---|
| Data Services | Unstructured Data Processed |
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 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. 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. |
In Data 360, unstructured data may be chunked and vectorized using an embedding model. Usage is computed only once across all these activities. For example, if one 100 MB PDF document is chunked and vectorized, usage is computed as 100 MB, not as 200MB. The cost of creating a search index remains the same for vector search index and hybrid search index. |
| Flex Credits | 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. |
In Data 360, unstructured data may be chunked and vectorized using an embedding model. Usage is computed only once across all these activities. For example, if one 100 MB PDF document is chunked and vectorized, usage is computed as 100 MB, not as 200MB. The cost of creating a search index remains the same for vector search index and hybrid search index. |
| Data Services | 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. |
For hybrid search queries against unstructured data, the number of vectors and keyword records in the search index are counted. In a typical search index, the number of keyword records is the same as the number of vectors. |
| Flex Credits | 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 |
For hybrid search queries against unstructured data, the number of vectors and keyword records in the search index are counted. In a typical search index, the number of keyword records is the same as the number of vectors. |
Data 360 Storage Usage
Storage costs are determined by your contract. Use Digital Wallet to check your current usage.
| Digital Wallet Consumption Card | Usage Type | Usage Type Description | Notes |
|---|---|---|---|
| Data Storage | Storage Beyond Allocation | Usage is calculated based on the amount of storage used above the amount allocated. |
Every file ingested and table created, including unstructured data lake objects (UDLO), unstructured data model objects (UDMO), CDMO, or index data model objects (index DMO), count toward Data 360 data storage, such as, the chunk and index DMOs generated when vector or hybrid search indexes are created. |