---
schema_version: "1"
id: 77c09b1944aca76e39abf67c48f6962109ee32490e541464f6796afbfff9e3f8
title: Billing Considerations for Communication Capping
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/data/264-0-0/c360_a_billing_considerations_for_communication_capping.md
canonical_url: https://help.salesforce.com/s/articleView?id=data.c360_a_billing_considerations_for_communication_capping.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 539d82851052722333d5b89879b45094d18757baf86658aa36a1b9b5e5e8d343
description: Use of Communication Capping impacts the consumption of credits in these usage types.
products:
  - Data 360
release: "264"
---
# Billing Considerations for Communication Capping

Use of Communication Capping 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 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](https://help.salesforce.com/s/articleView?id=data.c360_a_data_usage_types.htm&type=5&language=en_US) and [Flex Credits Usage Types for Data 360](https://help.salesforce.com/s/articleView?id=data.c360_a_flex_credits_for_data360.htm&type=5&language=en_US). To check multipliers for each usage type, see the [Multipliers for Data Services Rate Card](https://www.salesforce.com/data/rates/multipliers/) or the [Agentforce and Data 360 Flex Credits Rate Card](https://www.salesforce.com/agentforce/rates/). The cost of each credit is determined by your contract.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:16.666666666666664%">
          <col style="width:16.666666666666664%">
          <col style="width:33.33333333333333%">
          <col style="width:33.33333333333333%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d113636e85">Digital Wallet Consumption Card</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d113636e88">Usage Type</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d113636e91">Usage Type Description</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d113636e94">Notes</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Digital Wallet Consumption Card" class="slds-cell-wrap" style="vertical-align:top;" headers="d113636e85 "><span>Data Services</span></td>

            <td data-label="Usage Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d113636e88 ">Batch Calculated Insights</td>

            <td data-label="Usage Type Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d113636e91 ">
              <p>Usage is calculated based on the number of
                records in all underlying objects used in creating the Calculated Insight each time it
                runs.</p>
              <p style="margin-bottom:0;">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. </p>
            </td>

            <td data-label="Notes" class="slds-cell-wrap" style="vertical-align:top;" headers="d113636e94 ">&nbsp;</td>

          </tr>
          <tr class="">
            <td data-label="Digital Wallet Consumption Card" class="slds-cell-wrap" style="vertical-align:top;" headers="d113636e85 "><span>Data Services</span></td>

            <td data-label="Usage Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d113636e88 ">Batch Activations</td>

            <td data-label="Usage Type Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d113636e91 ">Usage is calculated based on the number of records
              processed.</td>

            <td data-label="Notes" class="slds-cell-wrap" style="vertical-align:top;" headers="d113636e94 ">&nbsp;</td>

          </tr>
          <tr class="">
            <td data-label="Digital Wallet Consumption Card" class="slds-cell-wrap" style="vertical-align:top;" headers="d113636e85 "><span>Data Services</span></td>

            <td data-label="Usage Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d113636e88 ">Segmentation</td>

            <td data-label="Usage Type Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d113636e91 ">Usage is calculated based on the number of records
              processed. </td>

            <td data-label="Notes" class="slds-cell-wrap" style="vertical-align:top;" headers="d113636e94 ">&nbsp;</td>

          </tr>
          <tr class="">
            <td data-label="Digital Wallet Consumption Card" class="slds-cell-wrap" style="vertical-align:top;" headers="d113636e85 "><span>Data Services</span></td>

            <td data-label="Usage Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d113636e88 ">Data Queries</td>

            <td data-label="Usage Type Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d113636e91 ">
              <p>Usage is calculated based on the number of records
                processed. </p>
              <p style="margin-bottom:0;">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.</p>
            </td>

            <td data-label="Notes" class="slds-cell-wrap" style="vertical-align:top;" headers="d113636e94 ">Data queries are consumed when joining the activation audience with calculated
              insights counts to determine qualification.</td>

          </tr>
          <tr class="">
            <td data-label="Digital Wallet Consumption Card" class="slds-cell-wrap" style="vertical-align:top;" headers="d113636e85 "><span>Flex Credits</span></td>

            <td data-label="Usage Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d113636e88 ">Data 360 Prep</td>

            <td data-label="Usage Type Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d113636e91 ">
              <p>Usage is calculated based on the data object type.</p>
              <p>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. </p>
              <p>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.</p>
              <p>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.</p>
              <p style="margin-bottom:0;">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.</p>
            </td>

            <td data-label="Notes" class="slds-cell-wrap" style="vertical-align:top;" headers="d113636e94 ">&nbsp;</td>

          </tr>
          <tr class="">
            <td data-label="Digital Wallet Consumption Card" class="slds-cell-wrap" style="vertical-align:top;" headers="d113636e85 "><span>Flex Credits</span></td>

            <td data-label="Usage Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d113636e88 ">Data 360 Activation</td>

            <td data-label="Usage Type Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d113636e91 ">Usage is calculated based on the number of records processed for a Data 360
              activation.</td>

            <td data-label="Notes" class="slds-cell-wrap" style="vertical-align:top;" headers="d113636e94 ">&nbsp;</td>

          </tr>
          <tr class="">
            <td data-label="Digital Wallet Consumption Card" class="slds-cell-wrap" style="vertical-align:top;" headers="d113636e85 "><span>Flex Credits</span></td>

            <td data-label="Usage Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d113636e88 ">Data 360 Segmentation</td>

            <td data-label="Usage Type Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d113636e91 ">Usage is calculated based on the number of records processed by a Data 360
              segment.</td>

            <td data-label="Notes" class="slds-cell-wrap" style="vertical-align:top;" headers="d113636e94 ">&nbsp;</td>

          </tr>
          <tr class="">
            <td data-label="Digital Wallet Consumption Card" class="slds-cell-wrap" style="vertical-align:top;" headers="d113636e85 "><span>Flex Credits</span></td>

            <td data-label="Usage Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d113636e88 ">Data 360 Queries</td>

            <td data-label="Usage Type Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d113636e91 ">
              <p>Usage is calculated based on the number of records processed. </p>
              <p>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.</p>
              <p style="margin-bottom:0;">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</p>
            </td>

            <td data-label="Notes" class="slds-cell-wrap" style="vertical-align:top;" headers="d113636e94 ">&nbsp;</td>

          </tr>
        </tbody>
      </table>

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

## Reduce Communication Capping Costs

You can lower credit consumption rates for communication capping in several ways.

- Since communication capping is tied to activation, ensure it is bypassed for all activations pertaining to sending transactional messages.
- Create rules rationally and delete them when no longer used so that the rules never proliferate - the compute cost grows nonlinearly with the count of rules.