Salesforce Docs Portal

Billing Considerations for Data Actions

Use of Data Actions 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 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 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 Streaming Actions (including lookups) Usage is calculated based on the number of records processed. A lookup is an enrichment from a related object.
  • If you’re creating a data action on a primary object, usage is consumed for change events.
  • If you’re creating a data action on a related object, usage is consumed once per day based on the number of active rows in the object. Consumption is regardless of the number of data actions using the same related object.
  • This usage type applies if you’re publishing an event to a Salesforce platform event through a Data 360-triggered flow, which uses the data action functionality.
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 only consumed if copy field enrichment events exceed 250,000.
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

  
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.
  • If you’re creating a data action on a primary object, usage is consumed for change events.
  • If you’re creating a data action on a related object, usage is consumed once per day based on the number of active rows in the object. Consumption is regardless of the number of data actions using the same related object.
  • This usage type applies if you’re publishing an event to a Salesforce platform event through a Data 360-triggered flow, which uses the data action functionality.

For more information on how usage is billed, refer to your contract or contact your account executive.

Reduce Data Action Costs

You can lower consumption rates for data actions in several ways.

  • Unless you have an enrichment use case, don’t include related objects.
  • Delete all unused and unwanted data actions if downstream systems aren’t consuming any events.
  • Apply filter conditions in data actions rather than sending all events to downstream systems.

See Also