You are here:
Billing Considerations for Data Ingestion
Data Ingestion uses Data 360 to ingest data from external sources. Use of Data Ingestion 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.
If you have certain licenses or editions, such as a Data 360 Profiles license or Agentforce 1 Edition, some types of usage aren’t metered. Check your licenses and review license documentation for more information.
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 you have any active Data Services credits, those credits are consumed first. If you run out of Data Services credits or never had any, your org consumes Flex Credits for Data 360 services. 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 Consumption Card | Usage Type | Usage Type Description | Notes |
|---|---|---|---|
| Data Services | 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. When you use ingestion API in bulk mode, it uses the Batch Data Pipeline usage type instead. |
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. This usage type is consumed when data is ingested by streaming connectors. |
| Data Services | 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. | This usage type is consumed when data is ingested by batch connectors. |
| Data Services | 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 |
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 Credits aren’t consumed for usage that falls into this usage type. Metrics for Internal Data Pipeline usage are still being collected but aren’t shown in Digital Wallet because they don’t consume credits. If you need to view metrics for this uage type, contact your Account Executive. |
| Flex Credits | 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 the ingestion API when used in streaming mode. Bulk mode of ingestion API is not included. For streaming data transforms, usage is calculated based on the higher of the number of rows read or the number of rows written. When performing joins, the number of rows read is calculated by multiplying the number of records from the streaming input object by the number of joined objects. For 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. |
For more information on how Data 360 usage is billed, refer to your contract or contact your account executive.
Reduce Data Ingestion Costs
You can lower consumption rates for data ingestion by changing the data stream settings and refresh modes on your data connectors. Ingesting less data, less frequently reduces credit consumption.
These settings are the most efficient settings for lowering cost. Not all settings are available on all connectors.
- Refresh Mode--When Full Refresh mode is selected, the connector re-ingests all data in every ingestion batch. Reduce your usage by selecting an Incremental or Upsert refresh mode.
- Conditional Settings--Reduce your consumption by using a data filter to ingest just the data you need to fulfill your use cases.
- File Settings--For connectors running in Full Refresh mode, don’t select
Refresh initial file immediately. To avoid an extra consumption cycle, allow the connector to refresh data on its regular schedule. - Schedule Frequency--To reduce usage for connectors running in Full Refresh mode, opt to ingest data less frequently.
