You are here:
Billing Considerations for Code Extension
Using code extension in Data 360 impacts the consumption of credits used for billing for orgs operating Data 360 under a Data Cloud license.
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 code extension, your org consumes credits from either the Data Services consumption card or the Flex Credits consumption card. If you have any active Data Services consumption cards, those credits are consumed first. If you run out of Data Services credits or never had any, your org consumes Data 360 Flex Credits for Data 360 services.
To learn more about usage types, see Data 360 Billable Usage Types or 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 | Usage Type | Usage Type Description | Notes |
|---|---|---|---|
| Data Services | 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. | See the sections later for details on compute size and hourly consumption rate. |
| Flex Credits | 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. | Credits are only consumed in this usage type when your org doesn’t have any Data Services credits. |
Compute Size Impact on Billing
The compute size that you select for your custom code deployment directly affects credit consumption.
The available compute size options are:
- Standard - Large - 4 Compute Units per hour
- Standard - X-Large - 8 Compute Units per hour
- Standard - 2X-Large - 16 Compute Units per hour
- Standard - 4X-Large - 32 Compute Units per hour
Compute Unit Consumption Calculation
Compute Unit consumption depends on the compute size you select for your code execution and on total compute time. Total compute time accounts for the total run time of all underlying components. Because the job uses parallel processing for underlying components, total compute time can be greater than the start-to-finish duration.
Compute Unit consumption is calculated by using the following formula:
Compute Unit Consumption = Total Compute Time (hours) x Compute Unit Rate per Hour for the Compute Size
Example: Suppose you execute a code extension script configured for a Standard - Large Compute size. Total compute time is 1.5 hours. When configured to use Standard - Large compute size, the code uses 4 Compute Units for every hour it runs.
- Compute Size: Standard - Large - 4 Compute Units per hour
- Total Compute Time: 1.5 hours (illustrative)
- Compute Unit Rate per Hour for the Compute Size: 4 Compute Units/hour
- Compute Unit Consumption: 1.5 hours x 4 Compute Units/hour = 6 Compute Units
Your code consumes 6 compute units.
Your code could execute in less time if you chose a larger compute size, however, larger compute sizes consume more compute units per hour.
