You are here:
Billing Considerations for Segmentation
Segmentation uses Data 360 for processing and publishing segment data. Use of segmentation 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, 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 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 | Segmentation | Usage is calculated based on the number of records processed. | Credits are consumed in this usage type when the segment is published. |
| Flex Credits | Data 360 Segmentation | Usage is calculated based on the number of records processed by a Data 360 segment. | Credits are consumed in this usage type when the segment is published. |
| 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 for several purposes when viewing, processing, and publishing a 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 |
|
| Data Services | Sub-second Real-Time Events & API | Usage is calculated based on the sum of the number of profile events, engagement events, API calls, and data actions processed in the sub-second real-time layer and real-time ingestion API, including web and mobile SDKs traffic. Profile events, engagement events, API calls, and data actions 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, 20 API calls, and 5 data actions are processed during a particular billing period, the total processed is 38. |
This category applies only to real-time segmentation. |
| Flex Credits | Data 360 Real-Time Pipeline | Usage is calculated based on the sum of the number of profile events, engagement events, API calls, and data actions processed in the sub-second real-time layer, including web and mobile SDKs traffic and real-time ingestion API. Profile events, engagement events, API calls, and data actions 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, 20 API calls, and 5 data actions are processed during a particular billing period, the total processed is 38. |
This category applies only to real-time segmentation. |
| Data Storage | Storage Beyond Allocation | Usage is calculated based on the amount of storage used above the amount allocated. | Segmentation stores the output of publishes in data model objects. |
| Data Services | Data Federation or Sharing Rows Accessed | For data federation, usage is calculated based on the number of records retrieved from the source. For a data share, usage is calculated based on the number of rows returned to fulfill an external data lake’s request. For data sharing between Data 360 orgs, this usage type applies to the target org for all queries. For external data shares, this usage type applies only to cross-cloud and cross-region queries. There’s no credit consumption if the query originates from the same region and the same cloud. |
Credits are consumed in this usage type when a DMO with Value Suggestions enabled has external DLOs associated with it. |
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. | Segmentation stores the output of publishes in data model objects. |
For more information on how Data 360 usage is billed, refer to your contract or contact your account executive.
Reduce Segmentation Costs
You can lower credit consumption rates for segmentation in several ways.
- Before publishing a segment, ensure quality of results by previewing them on a sample data set.
- Run quality checks on your segments by verifying segment membership before publishing.
- Nest common filters in multiple segments in last membership mode for reuse and lower costs.
Update these settings on segments to minimize consumption.
- Run Mode--If your use case allows for it, don’t schedule segment publishes. For example, you can reduce costs when you’re testing and refining a segment by running it only when you’re ready.
- Frequency, Run Every, and Start Date--Reduce credit consumption by reducing the frequency of scheduled publishes.
- Ends--Limit the time period during which the segment runs by setting it to stop running.
- Lookback Window--Reduce the number of records processed by refining your lookback window to only the necessary amount of time required by your use case.
