Billing Considerations for Clean Rooms

Clean rooms uses Data 360 to ingest data securely into a clean room collaboration. Use of Clean rooms 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.

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 360for 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.

Usage Types Consumed on the Provider Org

A provider org is a Data 360 org that contributes data to the clean room for querying.

Digital Wallet Consumption Card Usage Type Usage Type Description Notes
Data Services Data Share Rows Shared (Data Out)

Usage is calculated based on the total number of records processed when you first create a data share and link to a data share target. This applies only to the initial full batch of data; subsequent incremental changes don't count toward this usage type.

For data sharing between Data 360 orgs, this usage type isn’t applicable to the source org.

 
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. The number of rows accessed depends on the structure of the query and isn’t the same as the number of rows in the source data.

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.

 
Flex Credits Data 360 Zero Copy Sharing-Out

Usage is calculated based on the number of rows returned to fulfill an external data lake’s data share request. The number of rows accessed depends on the structure of the query and isn’t the same as the number of rows in the source data.

For data sharing between Data Cloud orgs, this usage type applies to the target org for all queries.

Data 360 is hosted only on Amazon Web Services (AWS) across multiple AWS regions. Same region is when Data Cloud and the data share target are hosted in the same AWS region. Same cloud is when Data Cloud and the data share target are hosted on the same cloud.

 

Usage Types Consumed on the Consumer Org

The consumer org is the org that typically queries data in a clean room to derive audience insights.

Digital Wallet Consumption Card Usage Type Usage Type Description Notes
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 Services Data Share Rows Shared (Data Out)

Usage is calculated based on the total number of records processed when you first create a data share and link to a data share target. This applies only to the initial full batch of data; subsequent incremental changes don't count toward this usage type.

For data sharing between Data 360 orgs, this usage type isn’t applicable to the source org.

 
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. The number of rows accessed depends on the structure of the query and isn’t the same as the number of rows in the source data.

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.

 
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 Zero Copy Sharing-Out

Usage is calculated based on the number of rows returned to fulfill an external data lake’s data share request. The number of rows accessed depends on the structure of the query and isn’t the same as the number of rows in the source data.

For data sharing between Data Cloud orgs, this usage type applies to the target org for all queries.

Data 360 is hosted only on Amazon Web Services (AWS) across multiple AWS regions. Same region is when Data Cloud and the data share target are hosted in the same AWS region. Same cloud is when Data Cloud and the data share target are hosted on the same cloud.

 

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

Reduce Clean Rooms Costs

You can lower consumption rates for Clean Rooms in several ways.

  • If you're ingesting data to Data 360 for clean rooms, hash the personally identifiable information (PII) to avoid transforms.
  • Avoid running a query too often. Unless a segment is refreshed, consecutive query results don't show a significant difference.