---
schema_version: "1"
id: a479b54f2aaf91a32fa28d1552aeea357eebdc27365540943ea9cd7d8a5ef858
title: Billing Considerations for Data 360 Reports and Dashboards
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/analytics/264-0-0/rd_dc_reports_dashboards_usage_billing.md
canonical_url: https://help.salesforce.com/s/articleView?id=analytics.rd_dc_reports_dashboards_usage_billing.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 3686f8713c6d6689c8002efd2613a674bdfdfb230ecce011c0f50aed7f055912
description: Use of Data 360 Reports and Dashboards impacts the consumption of credits in these usage types.
products:
  - Cross Cloud
release: "264"
---
# Billing Considerations for Data 360 Reports and Dashboards

Use of Data 360 Reports and Dashboards 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 or Agentforce 1 Edition, 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 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:33.33333333333333%">
          <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="d7416e83">Digital Wallet Consumption Card</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d7416e86">Usage Type</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d7416e89">Usage Type Description</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Digital Wallet Consumption Card" class="slds-cell-wrap" style="vertical-align:top;" headers="d7416e83 "><span>Data Services</span></td>

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

            <td data-label="Usage Type Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d7416e89 ">
              <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>

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

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

            <td data-label="Usage Type Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d7416e89 ">
              <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>

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

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

## Reduce Data 360 Reports and Dashboard Costs

You can lower consumption rates for Data 360 Reports and Dashboards in several ways.

- Turn off **Update Preview Automatically** while editing reports. Each column or filter change runs a query. Compose your report first, and then run it once when you're done.
- Apply filters to limit the data that each report processes. Without filters, every run scans your full dataset. Well-chosen filters, such as date ranges, regions, and status, reduce the processed records.
- Disable detail rows on summary reports unless you need them. Detail rows trigger an extra subquery to fetch the underlying records on top of the summary aggregation.
- Limit how often dashboards refresh. Use scheduled subscriptions only for users who actively need them.
- Use Calculated Insights for metrics that you query repeatedly. Move frequently used aggregations, such as totals, averages, and counts by group, into a Calculated Insight. They're computed once on a schedule and read cheaply by every report and dashboard that needs them.