You are here:
Billing Considerations for Communication Capping
Use of Communication Capping 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.
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 and 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 | 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. The number or underlying object records takes into account data space filters. If there are no changes to the underlying objects, there will be no charge for the Insight job processing. In the case an object is used multiple times in the Insight definition, the records processed will only be counted once. |
|
| Data Services | Batch Activations | Usage is calculated based on the number of records processed. | |
| Data Services | Segmentation | Usage is calculated based on the number of records processed. | |
| 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. |
Data queries are consumed when joining the activation audience with calculated insights counts to determine qualification. |
| Flex Credits | 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. |
|
| Flex Credits | Data 360 Activation | Usage is calculated based on the number of records processed for a Data 360 activation. | |
| Flex Credits | Data 360 Segmentation | Usage is calculated based on the number of records processed by a Data 360 segment. | |
| 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 more information on how usage is billed, refer to your contract or contact your account executive.
Reduce Communication Capping Costs
You can lower credit consumption rates for communication capping in several ways.
-
Since communication capping is tied to activation, ensure it is bypassed for all activations pertaining to sending transactional messages.
-
Create rules rationally and delete them when no longer used so that the rules never proliferate - the compute cost grows nonlinearly with the count of rules.
