You are here:
Billing Considerations for Semantic Layer
Use of the semantic layer impacts the consumption of credits used for billing in these usage types.
This feature has access to Digital Wallet, a free account management tool that offers near real-time consumption data for enabled products across your active contracts. Access Digital Wallet and start tracking your org's usage. To learn more, see About Digital Wallet.
| Digital Wallet 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. |
Queries can be generated from any source that calls the semantic layer. This includes queries executed by Tableau Next, via the API, from Data 360 reports, semantic layer test models, or other sources. |
| 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. |
This category can be billed if a query calls for data accessible via data federation. |
For more information on how Data 360 usage is billed, refer to your contract or contact your account executive.
