| Data Services |
Internal Data Pipeline |
Usage is calculated based on the number of
rows of structured data ingested from Salesforce via the Salesforce CRM connector, Marketing
Cloud connector, B2C Commerce CDP connector, Salesforce B2C Commerce Intelligence connector,
and Marketing Cloud Personalization connector.
As of August 7, 2025, usage of this type is
included with Data 360 and doesn't consume credits. For details, see Ingest Salesforce Data into Data 360 for
Free.
|
Unmetered |
Unmetered |
|
| Data Services |
Batch Data Pipeline (External Data Pipeline) |
Usage is calculated based on the number of rows
batch data processed by Data 360 data streams across all connectors, with the exception of
structured data ingested via the Internal Data Pipeline. |
Metered |
Unmetered |
|
| Data Services |
Streaming Data Pipeline (External Data
Pipeline) |
Usage is calculated based on the number of
rows of streaming data processed by Data 360 across all data streams with stream processing,
with the exception of structured data ingested via the Internal Data Pipeline.
Data
streams that report usage with this usage type include streams created by the Website and
Mobile App connector and streaming ingestion API. When you use ingestion API in bulk mode,
it uses the Batch Data Pipeline usage type instead.
|
Metered |
Metered |
|
| Flex Credits |
Data 360 Streaming Pipeline |
Usage is calculated based on the data object type.
For streaming data ingestion, usage is calculated based on the number of rows of
streaming data processed by Data 360 across all data streams with stream processing, with
the exception of structured data that is ingested via the Internal Data Pipeline.
Data streams that report usage with this usage type are streams created by Website and
Mobile App Connector, and the ingestion API when used in streaming mode. Bulk mode of
ingestion API is not included.
For streaming data transforms, usage is calculated based on the higher of the number of
rows read or the number of rows written. When performing joins, the number of rows read is
calculated by multiplying the number of records from the streaming input object by the
number of joined objects.
For streaming calculated insights, usage is calculated based on the number of records
processed.
For streaming data actions, usage is calculated based on the number of records processed
in the DMO. Records processed are based on the number of new records created or updated in
the DMO per activation.
If a data graph is being used with the activation, the number of records processed will
be doubled in the final calculation. For example, when a data graph is being used with the
activation, if there is 1 new record change in the DMO, this will count as 2 records
processed.
|
Metered |
Metered |
Streaming data ingestion, streaming data transforms, and streaming calculated insights
consume credits in this usage type if you don’t have any Data Services credits.
Internal and batch data ingestion is unmetered when you’re using Flex Credits.
|
| Data Services |
Batch Data Transforms |
Usage is calculated based on the higher of the
number of rows read or number of rows written.
For incremental batch data transforms,
after the first time a transform runs, usage is based on the number of rows that have
changed since the previous run.
|
Metered |
Unmetered |
|
| 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.
|
Metered |
Metered |
|
| 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.
|
Metered |
Data transforms aren’t metered.
Other usage that falls into this category is metered.
|
You consume credits in this usage type if you don’t have any Data Services
credits. |
| Data Services |
Streaming Data Transforms |
Usage is calculated based on the higher of
the number of rows read or the number of rows written.
When performing joins, the number
of rows read is calculated by multiplying the number of records from the streaming input
object by the number of joined objects.
|
Metered |
Metered |
|
| Data Services |
Streaming Calculated Insights |
Usage is calculated based on the number
of records processed. |
Metered |
Metered |
|
| 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.
|
Metered |
Metered |
This category is billed if a query uses data federation live queries. |
| 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.
|
Metered |
Metered |
Data shares consume credits in this usage type if you don’t have Data Services
credits.
Unaccelerated data federation doesn’t consume credits when you’re using Flex Credits.
|
| 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.
|
Metered |
Unmetered |
Queries can be generated from any source that calls Tableau Next, including the API,
Data 360 reports, semantic layer test models, or other sources.
|
| 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.
|
Metered |
Unmetered |
Queries consume this category when you don’t have Data Services credits. |
