Insights uses Data 360 to define and calculate multi-dimensional metrics across unified customer data to power real-time personalization and analytics. Use of insights impacts the consumption of credits used for billing 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 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 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 | Streaming Calculated Insights | Usage is calculated based on the number of records processed. | |
| Data Services | 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 |
Data queries are used to create, update, and display the processing history table. |
| Data Services | Sub-second Real-Time Events |
Usage is calculated based on the sum of the number of profile events, engagement events, and API calls processed in the sub-second real-time layer, including accelerated data ingest, web and mobile SDKs traffic, server to server API traffic, and real-time ingestion API. Profile events, engagement events, and API calls are processed in the real-time layer if they are associated with a real-time data graph. For example, if 3 profile events, 10 engagement events, and 20 API calls are processed during a particular billing period, the total processed is 33. |
This category applies only to real-time calculated insights. |
| 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 Real-Time Pipeline |
Usage is calculated based on the sum of the number of profile events, engagement events, and API calls processed in the sub-second real-time layer, including accelerated data ingest, web and mobile SDKs traffic, server to server API traffic, and real-time ingestion API. Profile events, engagement events, and API calls are processed in the real-time layer if they are associated with a real-time data graph. For example, if 3 profile events, 10 engagement events, and 20 API calls are processed during a particular billing period, the total processed is 33. |
This category applies only to real-time insights. |
| 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. |
This category applies only to streaming insights. |
| 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 Data 360 usage is billed, refer to your contract or contact your account executive.
Data 360 Storage Usage
Storage costs are determined by your contract. Use Digital Wallet to check your current usage.
| Digital Wallet Card | Usage Type | Description | Notes |
|---|---|---|---|
| Data Storage | Storage Beyond Allocation | Usage is calculated based on the amount of storage used above the amount allocated. | Insights stores the output of ruleset runs in Data 360 calculated insights objects. |
Reduce Insights Costs
You can lower credit consumption rates for insights in several ways.
- Schedule--Reduce credit consumption by opting to run the insight less frequently.
- Start Date and End Date--Limiting the time period during which the insight runs reduces credit consumption. Set an end date for any insight that doesn’t need to be continuously updated.
- Track History--Turning off the history for your insight reduces the use of data queries.