Search Analytics gives you visibility into search performance through dashboards that show usage and behavior metrics. Search Analytics runs on Data 360 calculated insights, queries, and data prep, which impacts credit consumption in these usage types rather than incurring a flat fee.
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 & 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. |
Search Analytics uses calculated insights to generate the metrics that populate the Search Analytics Dashboard and User Insights Dashboard. |
| 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 used to create Data 360 reports and dashboards. |
| 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 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 360 Storage Usage
Storage costs are determined by your contract. Use Digital Wallet to check your current usage.
| Digital Wallet Consumption Card | Usage Type | Usage Type Description | Notes |
|---|---|---|---|
| Data Storage | Storage Beyond Allocation | Usage is calculated based on the amount of storage used above the amount allocated. | – |
For more information on how usage is billed, refer to your contract or contact your account executive.
Reduce Search Analytics Costs
Search Analytics consumes credits from Batch Calculated Insights, Data Queries, Data 360 Prep, and Data 360 Queries each time dashboards, insights, or reports refresh. You can lower consumption rates for Search Analytics by following these tips.
- Limit how often calculated insights refresh: Refresh frequency has the largest impact on cost. Insights and dashboards that refresh more often than the source data changes consume credits unnecessarily. Align the schedule with when source data changes. To change the calculated insight schedule, see Schedule a Calculated Insight in Data Cloud.
- Reduce the underlying dataset size: Add date filters, for example, 12 months instead of all-time, and use data space filters to limit the records that are processed. Fewer records result in lower prep and insight costs. To update date filters on Search Analytics calculated insights, see Update the Date Filter in Search Analytics Calculated Insights.
- Use incremental refresh instead of full refresh: After initial setup, process only changed or new records rather than rescanning all records.
- Disable or archive unused calculated insights: Calculated insights that continue to run on a schedule consume credits even if no one is using the output.
- Minimize dashboard and report runs: Fewer queries processed means fewer Data Query and Data 360 Query credits consumed.