From 2add607401c2a744bc636ea9ad2e91129ab62f23 Mon Sep 17 00:00:00 2001
From: Rosa Trieu <rosa.trieu@datadoghq.com>
Date: Fri, 25 Jul 2025 13:00:53 -0700
Subject: [PATCH 01/24] [DOCS-11631] BigQuery Cost Allocation

---
 config/_default/menus/main.en.yaml            | 28 +++++++++++++------
 .../cost_allocation/_index.md                 | 17 +++++++++++
 .../cost_allocation/bigquery.md               | 18 ++++++++++++
 .../container_cost_allocation.md              |  2 ++
 layouts/partials/nav/left-nav.html            |  2 +-
 5 files changed, 57 insertions(+), 10 deletions(-)
 create mode 100644 content/en/cloud_cost_management/cost_allocation/_index.md
 create mode 100644 content/en/cloud_cost_management/cost_allocation/bigquery.md
 rename content/en/cloud_cost_management/{ => cost_allocation}/container_cost_allocation.md (99%)

diff --git a/config/_default/menus/main.en.yaml b/config/_default/menus/main.en.yaml
index ccaf854547768..0f34bbdf8c693 100644
--- a/config/_default/menus/main.en.yaml
+++ b/config/_default/menus/main.en.yaml
@@ -3617,26 +3617,36 @@ menu:
       parent: cloud_cost
       identifier: cloud_cost_datadog_costs
       weight: 2
-    - name: Container Cost Allocation
-      url: cloud_cost_management/container_cost_allocation
+    - name: Cost Allocation
+      url: cloud_cost_management/cost_allocation
       parent: cloud_cost
-      identifier: cloud_cost_container_cost_allocation
+      identifier: cloud_cost_cost_allocation
       weight: 3
+    - name: Container Costs
+      url: cloud_cost_management/cost_allocation/container_cost_allocation/
+      parent: cloud_cost_cost_allocation
+      identifier: cloud_cost_container_cost_allocation
+      weight: 301
     - name: AWS
-      url: cloud_cost_management/container_cost_allocation/?tab=aws
+      url: cloud_cost_management/cost_allocation/container_cost_allocation/?tab=aws
       parent: cloud_cost_container_cost_allocation
       identifier: cloud_cost_container_cost_allocation_aws
-      weight: 301
+      weight: 101
     - name: Azure
-      url: cloud_cost_management/container_cost_allocation/?tab=azure
+      url: cloud_cost_management/cost_allocation/container_cost_allocation/?tab=azure
       parent: cloud_cost_container_cost_allocation
       identifier: cloud_cost_container_cost_allocation_azure
-      weight: 302
+      weight: 102
     - name: Google Cloud
-      url: cloud_cost_management/container_cost_allocation/?tab=google
+      url: cloud_cost_management/cost_allocation/container_cost_allocation/?tab=google
       parent: cloud_cost_container_cost_allocation
       identifier: cloud_cost_container_cost_allocation_google
-      weight: 303
+      weight: 103
+    - name: BigQuery Costs
+      url: cloud_cost_management/cost_allocation/bigquery_cost_allocation/
+      parent: cloud_cost_cost_allocation
+      identifier: cloud_cost_bigquery_cost_allocation
+      weight: 302
     - name: Custom Allocation Rules
       url: cloud_cost_management/custom_allocation_rules
       parent: cloud_cost
diff --git a/content/en/cloud_cost_management/cost_allocation/_index.md b/content/en/cloud_cost_management/cost_allocation/_index.md
new file mode 100644
index 0000000000000..b7928c894b581
--- /dev/null
+++ b/content/en/cloud_cost_management/cost_allocation/_index.md
@@ -0,0 +1,17 @@
+---
+title: Cost Allocation
+
+further_reading:
+  - link: "/cloud_cost_management/"
+    tag: "Documentation"
+    text: "Learn about Cloud Cost Management"
+---
+
+
+## Overview
+
+## Further reading
+
+{{< partial name="whats-next/whats-next.html" >}}
+
+[1]: 
\ No newline at end of file
diff --git a/content/en/cloud_cost_management/cost_allocation/bigquery.md b/content/en/cloud_cost_management/cost_allocation/bigquery.md
new file mode 100644
index 0000000000000..625cdf09c908d
--- /dev/null
+++ b/content/en/cloud_cost_management/cost_allocation/bigquery.md
@@ -0,0 +1,18 @@
+---
+title: BigQuery Cost Allocation
+description: 
+further_reading:
+  - link: "/cloud_cost_management/"
+    tag: "Documentation"
+    text: "Learn about Cloud Cost Management"
+---
+
+## Overview
+
+## 
+
+## Further reading
+
+{{< partial name="whats-next/whats-next.html" >}}
+
+[1]: 
\ No newline at end of file
diff --git a/content/en/cloud_cost_management/container_cost_allocation.md b/content/en/cloud_cost_management/cost_allocation/container_cost_allocation.md
similarity index 99%
rename from content/en/cloud_cost_management/container_cost_allocation.md
rename to content/en/cloud_cost_management/cost_allocation/container_cost_allocation.md
index e9fd97bc75249..9b888b461dc4c 100644
--- a/content/en/cloud_cost_management/container_cost_allocation.md
+++ b/content/en/cloud_cost_management/cost_allocation/container_cost_allocation.md
@@ -2,6 +2,8 @@
 title: Container Cost Allocation
 private: true
 description: Learn how to allocate Cloud Cost Management spending across your organization with Container Cost Allocation.
+aliases:
+- /cloud_cost_management/container_cost_allocation
 further_reading:
 - link: "/cloud_cost_management/"
   tag: "Documentation"
diff --git a/layouts/partials/nav/left-nav.html b/layouts/partials/nav/left-nav.html
index 6600d00011ca5..6ef5e91c77fb2 100644
--- a/layouts/partials/nav/left-nav.html
+++ b/layouts/partials/nav/left-nav.html
@@ -67,7 +67,7 @@
                                         </a>
                                         {{ if .HasChildren }}
 
-                                            <ul class="list-unstyled sub-menu {{ if not (in (slice "automatic_instrumentation" "custom_instrumentation" "observability_pipelines_reference_processing_language" "observability_pipelines_vector_configuration" "cloud_cost_saas_cost_integrations" "csm_setup_enterprise" "csm_setup_pro" "csm_setup_cloud_workload_security" "cspm_frameworks_benchmarks" "cspm_findings_explorer" "cws_workload_security_rules" "otel_integrations" "otel_collector_configuration" "rum_dashboards" 
+                                            <ul class="list-unstyled sub-menu {{ if not (in (slice "automatic_instrumentation" "custom_instrumentation" "observability_pipelines_reference_processing_language" "observability_pipelines_vector_configuration" "cloud_cost_container_cost_allocation" "cloud_cost_saas_cost_integrations" "csm_setup_enterprise" "csm_setup_pro" "csm_setup_cloud_workload_security" "cspm_frameworks_benchmarks" "cspm_findings_explorer" "cws_workload_security_rules" "otel_integrations" "otel_collector_configuration" "rum_dashboards" 
                                             "rum_browser_setup" "rum_session_replay_browser" "rum_session_replay_mobile" "rum_mobile_android" "rum_mobile_ios" "rum_mobile_flutter" "rum_mobile_kotlin" "rum_mobile_react_native" "rum_mobile_roku" "rum_mobile_unity" "pa_session_replay_mobile" "pa_session_replay_browser" "cloudcraft_api_aws_accounts" "cloudcraft_api_azure_accounts" "cloudcraft_api_blueprints" "cloudcraft_api_budgets" "cloudcraft_api_users" "appsec_enabling_single_step" "appsec_enabling_tracing_libraries" "synthetics_platform_dashboards" "synthetics_private_location" "synthetics_results_explorer" "ndm_netflow" "dashboards_ddsql_editor_reference" "application_security_software_composition_analysis_setup"
                                             "application_security_code_security_setup" "appsec_threats_management_setup" "observability_pipelines_log_volume_control" "observability_pipelines_dual_ship_logs" "observability_pipelines_archive_logs" "observability_pipelines_split_logs" "observability_pipelines_sensitive_data_redaction" "observability_pipelines_log_enrichment" "csm_setup_agentless_scanning" "observability_pipelines_generate_metrics" "log_explorer_calculated_fields" "test_impact_analysis_setup" "dbm_setup_postgres_rds" "sca_setup_runtime" "ndm_setup" "otel-setup-collector-exporter" "otel-setup-intake-endpoint" "otel_guides_migration" "otel-api-dd-sdk" "otel-setup-agent" "ide_plugins_idea" "otel_guides_migration" "agent_configuration_proxy" 
                                             "software_catalog_set_up" "software_catalog_entity_model" "asm_serverless") .Identifier) }}d-none{{ end }}">

From d49ef0cb05775abd0c58f75f1768a700ea4dc702 Mon Sep 17 00:00:00 2001
From: Rosa Trieu <rosa.trieu@datadoghq.com>
Date: Fri, 25 Jul 2025 13:05:51 -0700
Subject: [PATCH 02/24] landing page content

---
 .../cost_allocation/_index.md                 | 95 ++++++++++++++++++-
 1 file changed, 92 insertions(+), 3 deletions(-)

diff --git a/content/en/cloud_cost_management/cost_allocation/_index.md b/content/en/cloud_cost_management/cost_allocation/_index.md
index b7928c894b581..981d92b8113ca 100644
--- a/content/en/cloud_cost_management/cost_allocation/_index.md
+++ b/content/en/cloud_cost_management/cost_allocation/_index.md
@@ -1,17 +1,106 @@
 ---
 title: Cost Allocation
-
+description: Learn how to allocate cloud costs across your organization with Datadog Cloud Cost Management
 further_reading:
   - link: "/cloud_cost_management/"
     tag: "Documentation"
     text: "Learn about Cloud Cost Management"
+  - link: "/cloud_cost_management/cost_allocation/container_cost_allocation"
+    tag: "Documentation"
+    text: "Container Cost Allocation"
+  - link: "/cloud_cost_management/cost_allocation/bigquery"
+    tag: "Documentation"
+    text: "BigQuery Cost Allocation"
 ---
 
-
 ## Overview
 
+Datadog Cloud Cost Management (CCM) provides comprehensive cost allocation capabilities that help you understand and optimize your cloud spending by breaking down costs across different resources and organizational dimensions. Cost allocation enables you to:
+
+- **Track resource-level spending**: Allocate costs down to individual containers, pods, tasks, and data warehouse queries
+- **Optimize resource utilization**: Identify idle resources and underutilized capacity
+- **Chargeback and showback**: Attribute costs to specific teams, projects, or business units
+- **Make informed decisions**: Understand the true cost of your applications and services
+
+## Cost allocation methods
+
+CCM offers multiple cost allocation methods to help you understand your cloud spending at different levels of granularity:
+
+### Container cost allocation
+
+Automatically allocate the costs of your cloud clusters to individual services and workloads running in those clusters. Use cost metrics enriched with tags from pods, nodes, containers, and tasks to visualize container workload cost in the context of your entire cloud bill.
+
+**Supported platforms:**
+- **AWS**: ECS clusters, EKS clusters, and all Kubernetes clusters
+- **Azure**: AKS clusters and all Kubernetes clusters  
+- **Google Cloud**: GKE clusters and all Kubernetes clusters
+
+Learn more about [Container Cost Allocation][1].
+
+### BigQuery cost allocation
+
+Allocate BigQuery costs to individual queries, users, and projects to understand your data warehouse spending at a granular level. Track query performance costs, storage costs, and slot utilization across your organization.
+
+Learn more about [BigQuery Cost Allocation][2].
+
+## How cost allocation works
+
+Cost allocation divides host compute and other resource costs from your cloud provider into individual workloads associated with them. These divided costs are then enriched with tags from related resources so you can break down costs by any associated dimensions.
+
+### Resource allocation methods
+
+CCM uses different allocation methods depending on the resource type:
+
+| Resource Type | Allocation Method | Description |
+|---------------|-------------------|-------------|
+| **Compute** | Resource-based | Allocates costs based on CPU, memory, and GPU usage with configurable splits (for example, `60:40` for `CPU:memory`) |
+| **Storage** | Usage-based | Allocates costs based on actual storage usage, IOPS, and throughput |
+| **Data Transfer** | Traffic-based | Allocates costs based on network traffic volume and bandwidth usage |
+| **Managed Services** | Attribution-based | Allocates costs based on service usage and API calls |
+
+### Tag enrichment
+
+All allocated costs are enriched with tags from various sources:
+
+- **Kubernetes tags**: Pod labels, node labels, namespace information
+- **Cloud provider tags**: AWS tags, Azure tags, Google Cloud labels
+- **Custom tags**: Business-specific tags for team, project, environment
+- **Out-of-the-box tags**: Automatically applied tags for orchestration platform, cluster name, etc.
+
+## Understanding spend types
+
+CCM categorizes costs into different spend types to help you understand resource utilization:
+
+| Spend Type | Description |
+|------------|-------------|
+| **Usage** | Cost of resources actually used by workloads |
+| **Workload Idle** | Cost of resources reserved but not used by workloads |
+| **Cluster Idle** | Cost of resources not reserved by any workloads |
+| **Not Monitored** | Cost of resources not monitored by Datadog |
+
+## Cost metrics
+
+When cost allocation is enabled, the following metrics become available:
+
+- `aws.cost.amortized.shared.resources.allocated` (AWS)
+- `azure.cost.amortized.shared.resources.allocated` (Azure)  
+- `gcp.cost.amortized.shared.resources.allocated` (Google Cloud)
+
+These metrics include all your cloud costs and allow you to visualize spending across different dimensions and resources.
+
+## Getting started
+
+To get started with cost allocation:
+
+1. **Set up Cloud Cost Management** by configuring your cloud provider integration on the [Cloud Cost Setup page][3].
+2. **Enable container monitoring** by installing the Datadog Agent in your containerized environments.
+3. **Configure tag extraction** for detailed cost breakdown.
+4. **Set up BigQuery integration** for data warehouse insights.
+
 ## Further reading
 
 {{< partial name="whats-next/whats-next.html" >}}
 
-[1]: 
\ No newline at end of file
+[1]: /cloud_cost_management/cost_allocation/container_cost_allocation
+[2]: /cloud_cost_management/cost_allocation/bigquery
+[3]: https://app.datadoghq.com/cost/setup 
\ No newline at end of file

From c70e515a65c2d70fc4108fade80b675d3b015a81 Mon Sep 17 00:00:00 2001
From: Rosa Trieu <rosa.trieu@datadoghq.com>
Date: Fri, 25 Jul 2025 13:14:34 -0700
Subject: [PATCH 03/24] remove duplicate info

---
 .../cost_allocation/_index.md                 | 50 -------------------
 1 file changed, 50 deletions(-)

diff --git a/content/en/cloud_cost_management/cost_allocation/_index.md b/content/en/cloud_cost_management/cost_allocation/_index.md
index 981d92b8113ca..92b312e868904 100644
--- a/content/en/cloud_cost_management/cost_allocation/_index.md
+++ b/content/en/cloud_cost_management/cost_allocation/_index.md
@@ -30,11 +30,6 @@ CCM offers multiple cost allocation methods to help you understand your cloud sp
 
 Automatically allocate the costs of your cloud clusters to individual services and workloads running in those clusters. Use cost metrics enriched with tags from pods, nodes, containers, and tasks to visualize container workload cost in the context of your entire cloud bill.
 
-**Supported platforms:**
-- **AWS**: ECS clusters, EKS clusters, and all Kubernetes clusters
-- **Azure**: AKS clusters and all Kubernetes clusters  
-- **Google Cloud**: GKE clusters and all Kubernetes clusters
-
 Learn more about [Container Cost Allocation][1].
 
 ### BigQuery cost allocation
@@ -43,51 +38,6 @@ Allocate BigQuery costs to individual queries, users, and projects to understand
 
 Learn more about [BigQuery Cost Allocation][2].
 
-## How cost allocation works
-
-Cost allocation divides host compute and other resource costs from your cloud provider into individual workloads associated with them. These divided costs are then enriched with tags from related resources so you can break down costs by any associated dimensions.
-
-### Resource allocation methods
-
-CCM uses different allocation methods depending on the resource type:
-
-| Resource Type | Allocation Method | Description |
-|---------------|-------------------|-------------|
-| **Compute** | Resource-based | Allocates costs based on CPU, memory, and GPU usage with configurable splits (for example, `60:40` for `CPU:memory`) |
-| **Storage** | Usage-based | Allocates costs based on actual storage usage, IOPS, and throughput |
-| **Data Transfer** | Traffic-based | Allocates costs based on network traffic volume and bandwidth usage |
-| **Managed Services** | Attribution-based | Allocates costs based on service usage and API calls |
-
-### Tag enrichment
-
-All allocated costs are enriched with tags from various sources:
-
-- **Kubernetes tags**: Pod labels, node labels, namespace information
-- **Cloud provider tags**: AWS tags, Azure tags, Google Cloud labels
-- **Custom tags**: Business-specific tags for team, project, environment
-- **Out-of-the-box tags**: Automatically applied tags for orchestration platform, cluster name, etc.
-
-## Understanding spend types
-
-CCM categorizes costs into different spend types to help you understand resource utilization:
-
-| Spend Type | Description |
-|------------|-------------|
-| **Usage** | Cost of resources actually used by workloads |
-| **Workload Idle** | Cost of resources reserved but not used by workloads |
-| **Cluster Idle** | Cost of resources not reserved by any workloads |
-| **Not Monitored** | Cost of resources not monitored by Datadog |
-
-## Cost metrics
-
-When cost allocation is enabled, the following metrics become available:
-
-- `aws.cost.amortized.shared.resources.allocated` (AWS)
-- `azure.cost.amortized.shared.resources.allocated` (Azure)  
-- `gcp.cost.amortized.shared.resources.allocated` (Google Cloud)
-
-These metrics include all your cloud costs and allow you to visualize spending across different dimensions and resources.
-
 ## Getting started
 
 To get started with cost allocation:

From e262f819ec87bff6e7432c9db854acdea783d5b1 Mon Sep 17 00:00:00 2001
From: kaylawan2 <kayla.wan@datadoghq.com>
Date: Mon, 28 Jul 2025 12:09:07 -0400
Subject: [PATCH 04/24] Update bigquery.md

---
 content/en/cloud_cost_management/cost_allocation/bigquery.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/content/en/cloud_cost_management/cost_allocation/bigquery.md b/content/en/cloud_cost_management/cost_allocation/bigquery.md
index 625cdf09c908d..c2a19757e52cf 100644
--- a/content/en/cloud_cost_management/cost_allocation/bigquery.md
+++ b/content/en/cloud_cost_management/cost_allocation/bigquery.md
@@ -8,6 +8,7 @@ further_reading:
 ---
 
 ## Overview
+This is the overview for BigQuery Allocation
 
 ## 
 
@@ -15,4 +16,4 @@ further_reading:
 
 {{< partial name="whats-next/whats-next.html" >}}
 
-[1]: 
\ No newline at end of file
+[1]: 

From 2bc33b5a7fff66d53de04375b404683f1e010a66 Mon Sep 17 00:00:00 2001
From: kaylawan2 <kayla.wan@datadoghq.com>
Date: Mon, 28 Jul 2025 12:51:42 -0400
Subject: [PATCH 05/24] Update bigquery.md

---
 .../cost_allocation/bigquery.md               | 91 ++++++++++++++++++-
 1 file changed, 87 insertions(+), 4 deletions(-)

diff --git a/content/en/cloud_cost_management/cost_allocation/bigquery.md b/content/en/cloud_cost_management/cost_allocation/bigquery.md
index c2a19757e52cf..3307eb9554e08 100644
--- a/content/en/cloud_cost_management/cost_allocation/bigquery.md
+++ b/content/en/cloud_cost_management/cost_allocation/bigquery.md
@@ -1,6 +1,6 @@
 ---
 title: BigQuery Cost Allocation
-description: 
+description: Learn how to allocate Cloud Cost Management spending across your organization with BigQuery Cost Allocation.
 further_reading:
   - link: "/cloud_cost_management/"
     tag: "Documentation"
@@ -8,12 +8,95 @@ further_reading:
 ---
 
 ## Overview
-This is the overview for BigQuery Allocation
 
-## 
+Datadog Cloud Cost Management (CCM) automatically allocates the costs of your Google BigQuery resources to individual queries and workloads. Use cost metrics enriched with tags from queries, projects, and reservations to visualize BigQuery workload costs in the context of your entire cloud bill.
+
+Resources
+CCM allocates costs for BigQuery resources for both types of Analysis costs (on-demand and reservation-based).
+
+CCM displays costs for resources including query-level analysis, storage, and data transfer on the [**BigQuery** dashboard][1].
+
+## Prerequisites
+
+The following table presents the list of collected features and the minimal Agent versions required:
+
+| Feature | Requirements |
+|---|---|
+| BigQuery Cost Allocation | Google Cloud Cost Management integration configured |
+| Query-Level Cost Attribution | BigQuery monitoring enabled |
+| Reservation Cost Allocation | BigQuery reservations configured |
+
+1. Configure the Google Cloud Cost Management integration on the [Cloud Cost Setup page][2].
+2. Enable BigQuery monitoring in your Google Cloud project.
+3. For reservation cost allocation, configure BigQuery reservations in your project.
+
+## Allocate costs
+
+Cost allocation divides BigQuery costs from your cloud provider into individual queries and workloads associated with them. These divided costs are enriched with tags from queries, projects, and reservations so you can break down costs by any associated dimensions.
+
+### Record enrichment and tagging for understanding costs
+
+CCM enriches BigQuery cost records with several key pieces of information:
+
+1. **User identification**: Records are enriched with `user_email` to track which user or service account executed the query
+2. **Reservation tracking**: Records include `reservation_id` to identify which reservation pool provided the compute resources
+3. **Scheduled queries**: Records are tagged with `dts_config_id` for identifying scheduled queries and data transfers
+4. **Orchestration platform**: All BigQuery query-related records are tagged with `orchestrator:bigquery`
+
+Additionally, CCM provides two special tags for detailed cost analysis:
+
+1. **`allocated_spend_type`**: Categorizes costs as either:
+   - `usage`: Active query execution costs
+   - `cluster_idle`: Unused reservation capacity costs
+
+2. **`allocated_resource`**: Indicates the resource type being measured:
+   - `slots`: For reservation-based queries
+   - `bytes_processed`: For on-demand queries
+
+### Query-level tag extraction
+
+CCM extracts the following tags from BigQuery query logs, allowing you to aggregate on these fields in the explorer:
+
+| Tag | Description |
+|---|---|
+| `reservation_id` | The reservation pool that provided compute resources |
+| `user_email` | The user or service account that executed the query |
+| `dts_config_id` | Identifier for scheduled queries and data transfers |
+
+### Compute allocation
+
+For BigQuery compute allocation, CCM handles two pricing models:
+
+**On-demand pricing**:
+- Costs are directly attributed to individual queries based on bytes processed
+- Includes query-level tags for detailed cost attribution
+
+**Reservation-based pricing**:
+- Costs of reserved slots are allocated proportionally to queries using those slots
+- Allocation based on slot consumption (total_slot_ms) per query
+- Includes idle cost calculation for unused reservation capacity
+
+### Compute
+
+Costs are allocated into the following spend types:
+
+| Spend type | Description |
+|---|---|
+| Usage | Cost of query execution based on bytes processed (on-demand) or slot consumption (reservation) |
+| Cluster idle | Cost of reserved slots allocated but not utilized by queries |
+
+### Storage
+
+Storage costs are categorized as:
+
+| Spend type | Description |
+|---|---|
+| Active | Cost of actively used storage |
+| Long-term | Cost of infrequently accessed storage |
 
 ## Further reading
 
 {{< partial name="whats-next/whats-next.html" >}}
 
-[1]: 
+[1]: https://app.datadoghq.com/dashboard/ecm-es8-agw/bigquery-allocation
+[2]: https://app.datadoghq.com/cost/setup 

From bf9be64e176f996a6a1746f752b71f4040768083 Mon Sep 17 00:00:00 2001
From: kaylawan2 <kayla.wan@datadoghq.com>
Date: Mon, 28 Jul 2025 13:08:47 -0400
Subject: [PATCH 06/24] Update bigquery.md

---
 .../en/cloud_cost_management/cost_allocation/bigquery.md    | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/content/en/cloud_cost_management/cost_allocation/bigquery.md b/content/en/cloud_cost_management/cost_allocation/bigquery.md
index 3307eb9554e08..bf9dbb88bd933 100644
--- a/content/en/cloud_cost_management/cost_allocation/bigquery.md
+++ b/content/en/cloud_cost_management/cost_allocation/bigquery.md
@@ -11,10 +11,8 @@ further_reading:
 
 Datadog Cloud Cost Management (CCM) automatically allocates the costs of your Google BigQuery resources to individual queries and workloads. Use cost metrics enriched with tags from queries, projects, and reservations to visualize BigQuery workload costs in the context of your entire cloud bill.
 
-Resources
-CCM allocates costs for BigQuery resources for both types of Analysis costs (on-demand and reservation-based).
-
-CCM displays costs for resources including query-level analysis, storage, and data transfer on the [**BigQuery** dashboard][1].
+## Resources
+CCM allocates costs for BigQuery resources for both types of Analysis costs (on-demand and reservation-based). CCM displays costs for resources including query-level analysis, storage, and data transfer on the [**BigQuery** dashboard][1].
 
 ## Prerequisites
 

From 9b33597df566897e2a72ba0a69aa3a36d1313530 Mon Sep 17 00:00:00 2001
From: kaylawan2 <kayla.wan@datadoghq.com>
Date: Mon, 28 Jul 2025 13:11:50 -0400
Subject: [PATCH 07/24] Update bigquery.md

---
 .../cost_allocation/bigquery.md               | 25 +++++++------------
 1 file changed, 9 insertions(+), 16 deletions(-)

diff --git a/content/en/cloud_cost_management/cost_allocation/bigquery.md b/content/en/cloud_cost_management/cost_allocation/bigquery.md
index bf9dbb88bd933..fbeee7356bdcd 100644
--- a/content/en/cloud_cost_management/cost_allocation/bigquery.md
+++ b/content/en/cloud_cost_management/cost_allocation/bigquery.md
@@ -32,14 +32,15 @@ The following table presents the list of collected features and the minimal Agen
 
 Cost allocation divides BigQuery costs from your cloud provider into individual queries and workloads associated with them. These divided costs are enriched with tags from queries, projects, and reservations so you can break down costs by any associated dimensions.
 
-### Record enrichment and tagging for understanding costs
+### Query-level tag extraction
 
-CCM enriches BigQuery cost records with several key pieces of information:
+CCM extracts the following tags from BigQuery query logs, allowing you to aggregate on these fields in the explorer:
 
-1. **User identification**: Records are enriched with `user_email` to track which user or service account executed the query
-2. **Reservation tracking**: Records include `reservation_id` to identify which reservation pool provided the compute resources
-3. **Scheduled queries**: Records are tagged with `dts_config_id` for identifying scheduled queries and data transfers
-4. **Orchestration platform**: All BigQuery query-related records are tagged with `orchestrator:bigquery`
+| Tag | Description |
+|---|---|
+| `reservation_id` | The reservation pool that provided compute resources |
+| `user_email` | The user or service account that executed the query |
+| `dts_config_id` | Identifier for scheduled queries and data transfers |
 
 Additionally, CCM provides two special tags for detailed cost analysis:
 
@@ -50,16 +51,8 @@ Additionally, CCM provides two special tags for detailed cost analysis:
 2. **`allocated_resource`**: Indicates the resource type being measured:
    - `slots`: For reservation-based queries
    - `bytes_processed`: For on-demand queries
-
-### Query-level tag extraction
-
-CCM extracts the following tags from BigQuery query logs, allowing you to aggregate on these fields in the explorer:
-
-| Tag | Description |
-|---|---|
-| `reservation_id` | The reservation pool that provided compute resources |
-| `user_email` | The user or service account that executed the query |
-| `dts_config_id` | Identifier for scheduled queries and data transfers |
+   
+All BigQuery query-related records are tagged with `orchestrator:BigQuery`.
 
 ### Compute allocation
 

From e2630b96e83d8319496e71a4db5596924d2b7439 Mon Sep 17 00:00:00 2001
From: kaylawan2 <kayla.wan@datadoghq.com>
Date: Mon, 28 Jul 2025 13:14:29 -0400
Subject: [PATCH 08/24] Update bigquery.md

---
 .../cost_allocation/bigquery.md                | 18 ++++++++++++++++--
 1 file changed, 16 insertions(+), 2 deletions(-)

diff --git a/content/en/cloud_cost_management/cost_allocation/bigquery.md b/content/en/cloud_cost_management/cost_allocation/bigquery.md
index fbeee7356bdcd..7924b526f7bbc 100644
--- a/content/en/cloud_cost_management/cost_allocation/bigquery.md
+++ b/content/en/cloud_cost_management/cost_allocation/bigquery.md
@@ -28,9 +28,23 @@ The following table presents the list of collected features and the minimal Agen
 2. Enable BigQuery monitoring in your Google Cloud project.
 3. For reservation cost allocation, configure BigQuery reservations in your project.
 
-## Allocate costs
+## Allocating costs
+
+Cost allocation divides BigQuery costs from GCP into individual queries and workloads associated with them. These divided costs are enriched with tags from queries, projects, and reservations so you can break down costs by any associated dimensions. 
+
+For reservation-based BigQuery costs, CCM calculates the cost per-query using the following formula:
+
+```
+cost_per_query = (query_slot_usage / total_reservation_slot_usage) * total_reservation_cost
+```
+
+Where:
+- `query_slot_usage`: The number of slot-seconds consumed by an individual query
+- `total_reservation_slot_usage`: The total slot-seconds used across all queries in the reservation
+- `total_reservation_cost`: The total cost of the reservation for the time period
+
+Any difference between the total billed reservation cost and the sum of allocated query costs is categorized as `cluster_idle` cost, representing unused reservation capacity.
 
-Cost allocation divides BigQuery costs from your cloud provider into individual queries and workloads associated with them. These divided costs are enriched with tags from queries, projects, and reservations so you can break down costs by any associated dimensions.
 
 ### Query-level tag extraction
 

From 8277f7387a034126586b033c4e97e447c43d8b29 Mon Sep 17 00:00:00 2001
From: kaylawan2 <kayla.wan@datadoghq.com>
Date: Mon, 28 Jul 2025 13:19:35 -0400
Subject: [PATCH 09/24] Update bigquery.md

---
 .../cost_allocation/bigquery.md                | 18 +++++++-----------
 1 file changed, 7 insertions(+), 11 deletions(-)

diff --git a/content/en/cloud_cost_management/cost_allocation/bigquery.md b/content/en/cloud_cost_management/cost_allocation/bigquery.md
index 7924b526f7bbc..c12d7a9cd949b 100644
--- a/content/en/cloud_cost_management/cost_allocation/bigquery.md
+++ b/content/en/cloud_cost_management/cost_allocation/bigquery.md
@@ -48,7 +48,7 @@ Any difference between the total billed reservation cost and the sum of allocate
 
 ### Query-level tag extraction
 
-CCM extracts the following tags from BigQuery query logs, allowing you to aggregate on these fields in the explorer:
+CCM extracts the following tags from BigQuery query logs via the Data Observability platform:
 
 | Tag | Description |
 |---|---|
@@ -56,17 +56,13 @@ CCM extracts the following tags from BigQuery query logs, allowing you to aggreg
 | `user_email` | The user or service account that executed the query |
 | `dts_config_id` | Identifier for scheduled queries and data transfers |
 
-Additionally, CCM provides two special tags for detailed cost analysis:
+Additionally, CCM adds the following tags for cost analysis:
 
-1. **`allocated_spend_type`**: Categorizes costs as either:
-   - `usage`: Active query execution costs
-   - `cluster_idle`: Unused reservation capacity costs
-
-2. **`allocated_resource`**: Indicates the resource type being measured:
-   - `slots`: For reservation-based queries
-   - `bytes_processed`: For on-demand queries
-   
-All BigQuery query-related records are tagged with `orchestrator:BigQuery`.
+| Tag | Description |
+|---|---|
+| `allocated_spend_type` | Categorizes costs as either `usage` (active query execution) or `cluster_idle` (unused reservation capacity) |
+| `allocated_resource` | Indicates resource measurement type - `slots` for reservation-based queries or `bytes_processed` for on-demand queries |
+| `orchestrator` | Set to `BigQuery` for all BigQuery query-related records |
 
 ### Compute allocation
 

From 758e02a2903b6e140d89a971b3be0a8a6d394188 Mon Sep 17 00:00:00 2001
From: kaylawan2 <kayla.wan@datadoghq.com>
Date: Mon, 28 Jul 2025 13:36:35 -0400
Subject: [PATCH 10/24] Update bigquery.md

---
 content/en/cloud_cost_management/cost_allocation/bigquery.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/cloud_cost_management/cost_allocation/bigquery.md b/content/en/cloud_cost_management/cost_allocation/bigquery.md
index c12d7a9cd949b..193328127f05c 100644
--- a/content/en/cloud_cost_management/cost_allocation/bigquery.md
+++ b/content/en/cloud_cost_management/cost_allocation/bigquery.md
@@ -32,7 +32,7 @@ The following table presents the list of collected features and the minimal Agen
 
 Cost allocation divides BigQuery costs from GCP into individual queries and workloads associated with them. These divided costs are enriched with tags from queries, projects, and reservations so you can break down costs by any associated dimensions. 
 
-For reservation-based BigQuery costs, CCM calculates the cost per-query using the following formula:
+For reservation-based BigQuery costs, CCM allocates costs proportionally based on slot usage. Each query's cost is determined by its share of the total slot usage within the reservation. For example, if a query uses 25% of the total consumed slots in a reservation during a given period, it will be allocated 25% of that reservation's total cost for that period. The cost per-query is calculated using the following formula:
 
 ```
 cost_per_query = (query_slot_usage / total_reservation_slot_usage) * total_reservation_cost

From 0f8556c395f7b5481b2267794b8a01e246b4931a Mon Sep 17 00:00:00 2001
From: kaylawan2 <kayla.wan@datadoghq.com>
Date: Mon, 28 Jul 2025 14:30:55 -0400
Subject: [PATCH 11/24] Update bigquery.md

---
 .../cloud_cost_management/cost_allocation/bigquery.md  | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/content/en/cloud_cost_management/cost_allocation/bigquery.md b/content/en/cloud_cost_management/cost_allocation/bigquery.md
index 193328127f05c..57317fcd3cba7 100644
--- a/content/en/cloud_cost_management/cost_allocation/bigquery.md
+++ b/content/en/cloud_cost_management/cost_allocation/bigquery.md
@@ -16,7 +16,7 @@ CCM allocates costs for BigQuery resources for both types of Analysis costs (on-
 
 ## Prerequisites
 
-The following table presents the list of collected features and the minimal Agent versions required:
+The following table presents the list of collected features and the minimal requirements:
 
 | Feature | Requirements |
 |---|---|
@@ -32,7 +32,7 @@ The following table presents the list of collected features and the minimal Agen
 
 Cost allocation divides BigQuery costs from GCP into individual queries and workloads associated with them. These divided costs are enriched with tags from queries, projects, and reservations so you can break down costs by any associated dimensions. 
 
-For reservation-based BigQuery costs, CCM allocates costs proportionally based on slot usage. Each query's cost is determined by its share of the total slot usage within the reservation. For example, if a query uses 25% of the total consumed slots in a reservation during a given period, it will be allocated 25% of that reservation's total cost for that period. The cost per-query is calculated using the following formula:
+For reservation-based BigQuery costs, CCM allocates costs proportionally based on slot usage. Each query's cost is determined by its share of the total slot usage within the project's reservations. For example, if a query uses 25% of the total consumed slots in a project's reservation during a given period, it will be allocated 25% of that project's total reservation cost for that period. The cost per-query is calculated using the following formula:
 
 ```
 cost_per_query = (query_slot_usage / total_reservation_slot_usage) * total_reservation_cost
@@ -40,10 +40,10 @@ cost_per_query = (query_slot_usage / total_reservation_slot_usage) * total_reser
 
 Where:
 - `query_slot_usage`: The number of slot-seconds consumed by an individual query
-- `total_reservation_slot_usage`: The total slot-seconds used across all queries in the reservation
-- `total_reservation_cost`: The total cost of the reservation for the time period
+- `total_reservation_slot_usage`: The total slot-seconds used across all queries in the project's reservations
+- `total_reservation_cost`: The total cost of the reservations for the time period
 
-Any difference between the total billed reservation cost and the sum of allocated query costs is categorized as `cluster_idle` cost, representing unused reservation capacity.
+Any difference between the total billed reservation cost and the sum of allocated query costs is categorized as a project's `cluster_idle` cost, representing unused reservation capacity.
 
 
 ### Query-level tag extraction

From c99f1b9a62454f2845f3cd07e18e3abc24b9f541 Mon Sep 17 00:00:00 2001
From: kaylawan2 <kayla.wan@datadoghq.com>
Date: Mon, 28 Jul 2025 14:34:29 -0400
Subject: [PATCH 12/24] Update bigquery.md

---
 .../en/cloud_cost_management/cost_allocation/bigquery.md    | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/content/en/cloud_cost_management/cost_allocation/bigquery.md b/content/en/cloud_cost_management/cost_allocation/bigquery.md
index 57317fcd3cba7..8e572a4a944ba 100644
--- a/content/en/cloud_cost_management/cost_allocation/bigquery.md
+++ b/content/en/cloud_cost_management/cost_allocation/bigquery.md
@@ -35,13 +35,13 @@ Cost allocation divides BigQuery costs from GCP into individual queries and work
 For reservation-based BigQuery costs, CCM allocates costs proportionally based on slot usage. Each query's cost is determined by its share of the total slot usage within the project's reservations. For example, if a query uses 25% of the total consumed slots in a project's reservation during a given period, it will be allocated 25% of that project's total reservation cost for that period. The cost per-query is calculated using the following formula:
 
 ```
-cost_per_query = (query_slot_usage / total_reservation_slot_usage) * total_reservation_cost
+cost_per_query = (query_slot_usage / total_slot_usage) * total_project_reservation_cost
 ```
 
 Where:
 - `query_slot_usage`: The number of slot-seconds consumed by an individual query
-- `total_reservation_slot_usage`: The total slot-seconds used across all queries in the project's reservations
-- `total_reservation_cost`: The total cost of the reservations for the time period
+- `total_slot_usage`: The total slot-seconds used across all queries in the project's reservations
+- `total_project_reservation_cost`: The total cost of the reservations in a given project for the time period
 
 Any difference between the total billed reservation cost and the sum of allocated query costs is categorized as a project's `cluster_idle` cost, representing unused reservation capacity.
 

From 0237fca97c6fe5d7e775119a6372b3706ceef87c Mon Sep 17 00:00:00 2001
From: kaylawan2 <kayla.wan@datadoghq.com>
Date: Wed, 30 Jul 2025 09:42:59 -0400
Subject: [PATCH 13/24] Update bigquery.md

---
 content/en/cloud_cost_management/cost_allocation/bigquery.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/cloud_cost_management/cost_allocation/bigquery.md b/content/en/cloud_cost_management/cost_allocation/bigquery.md
index 8e572a4a944ba..8b5677072b6ae 100644
--- a/content/en/cloud_cost_management/cost_allocation/bigquery.md
+++ b/content/en/cloud_cost_management/cost_allocation/bigquery.md
@@ -20,7 +20,7 @@ The following table presents the list of collected features and the minimal requ
 
 | Feature | Requirements |
 |---|---|
-| BigQuery Cost Allocation | Google Cloud Cost Management integration configured |
+| Retrieve tags from labels of a query | Supported without monitoring or reservations |
 | Query-Level Cost Attribution | BigQuery monitoring enabled |
 | Reservation Cost Allocation | BigQuery reservations configured |
 

From a54a9ab3c238f0616d403dda8403cd982aba8998 Mon Sep 17 00:00:00 2001
From: kaylawan2 <kayla.wan@datadoghq.com>
Date: Thu, 31 Jul 2025 13:34:38 -0400
Subject: [PATCH 14/24] Update bigquery.md

---
 .../cloud_cost_management/cost_allocation/bigquery.md  | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/content/en/cloud_cost_management/cost_allocation/bigquery.md b/content/en/cloud_cost_management/cost_allocation/bigquery.md
index 8b5677072b6ae..c32a6a913c898 100644
--- a/content/en/cloud_cost_management/cost_allocation/bigquery.md
+++ b/content/en/cloud_cost_management/cost_allocation/bigquery.md
@@ -74,7 +74,7 @@ For BigQuery compute allocation, CCM handles two pricing models:
 
 **Reservation-based pricing**:
 - Costs of reserved slots are allocated proportionally to queries using those slots
-- Allocation based on slot consumption (total_slot_ms) per query
+- Allocation based on slot consumption (`total_slot_ms`) per query
 - Includes idle cost calculation for unused reservation capacity
 
 ### Compute
@@ -83,8 +83,8 @@ Costs are allocated into the following spend types:
 
 | Spend type | Description |
 |---|---|
-| Usage | Cost of query execution based on bytes processed (on-demand) or slot consumption (reservation) |
-| Cluster idle | Cost of reserved slots allocated but not utilized by queries |
+| `Usage` | Cost of query execution based on bytes processed (on-demand) or slot consumption (reservation) |
+| `Cluster_idle` | Cost of reserved slots allocated but not utilized by queries |
 
 ### Storage
 
@@ -92,8 +92,8 @@ Storage costs are categorized as:
 
 | Spend type | Description |
 |---|---|
-| Active | Cost of actively used storage |
-| Long-term | Cost of infrequently accessed storage |
+| `Active` | Includes any table or table partition that has been modified in the last 90 days |
+| `Long-term` | Includes any table or table partition that has not been modified for 90 consecutive days. The price of storage for that table automatically drops by approximately 50%. There is no difference in performance, durability, or availability between active and long-term storage |
 
 ## Further reading
 

From e48fcd2c9a2028f8211608272459109d3046b658 Mon Sep 17 00:00:00 2001
From: Rosa Trieu <rosa.trieu@datadoghq.com>
Date: Thu, 31 Jul 2025 10:44:54 -0700
Subject: [PATCH 15/24] correct url

---
 config/_default/menus/main.en.yaml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/config/_default/menus/main.en.yaml b/config/_default/menus/main.en.yaml
index 0f34bbdf8c693..9638df1e1d56d 100644
--- a/config/_default/menus/main.en.yaml
+++ b/config/_default/menus/main.en.yaml
@@ -3643,9 +3643,9 @@ menu:
       identifier: cloud_cost_container_cost_allocation_google
       weight: 103
     - name: BigQuery Costs
-      url: cloud_cost_management/cost_allocation/bigquery_cost_allocation/
+      url: cloud_cost_management/cost_allocation/bigquery/
       parent: cloud_cost_cost_allocation
-      identifier: cloud_cost_bigquery_cost_allocation
+      identifier: cloud_cost_cost_allocationbigquery
       weight: 302
     - name: Custom Allocation Rules
       url: cloud_cost_management/custom_allocation_rules

From 8ad33fe77b3aa1174bf18236e4a1e1dff83f7556 Mon Sep 17 00:00:00 2001
From: kaylawan2 <kayla.wan@datadoghq.com>
Date: Thu, 31 Jul 2025 16:10:59 -0400
Subject: [PATCH 16/24] Update bigquery.md

---
 .../cost_allocation/bigquery.md                   | 15 ++++++++++++---
 1 file changed, 12 insertions(+), 3 deletions(-)

diff --git a/content/en/cloud_cost_management/cost_allocation/bigquery.md b/content/en/cloud_cost_management/cost_allocation/bigquery.md
index c32a6a913c898..4275c84543797 100644
--- a/content/en/cloud_cost_management/cost_allocation/bigquery.md
+++ b/content/en/cloud_cost_management/cost_allocation/bigquery.md
@@ -43,8 +43,17 @@ Where:
 - `total_slot_usage`: The total slot-seconds used across all queries in the project's reservations
 - `total_project_reservation_cost`: The total cost of the reservations in a given project for the time period
 
-Any difference between the total billed reservation cost and the sum of allocated query costs is categorized as a project's `cluster_idle` cost, representing unused reservation capacity.
+Any difference between the total billed reservation cost and the sum of allocated query costs is categorized as a project's `cluster_idle` cost, representing unused reservation capacity. 
 
+### Understanding idle costs
+
+Idle costs represent the portion of reservation capacity that was paid for but not utilized by queries. These costs arise when the reserved slot capacity exceeds actual usage during a billing period.
+
+**Idle slot sharing considerations**: If your organization has enabled idle slot sharing between reservations, the idle cost calculation may appear different than expected. When queries from one project use idle slots from another project's reservation, those slot costs are attributed as "free" rather than to the consuming project. This means:
+
+- A project's reservation may show higher idle costs if other projects are using its unused capacity
+- The original project pays full reservation costs regardless of cross-project usage
+- No automatic cost-transfer: Sharing projects don't pay the reservation owner for consumed idle slots
 
 ### Query-level tag extraction
 
@@ -84,7 +93,7 @@ Costs are allocated into the following spend types:
 | Spend type | Description |
 |---|---|
 | `Usage` | Cost of query execution based on bytes processed (on-demand) or slot consumption (reservation) |
-| `Cluster_idle` | Cost of reserved slots allocated but not utilized by queries |
+| `Cluster_idle` | Cost of reserved slots allocated within a project but not utilized by queries|
 
 ### Storage
 
@@ -96,7 +105,7 @@ Storage costs are categorized as:
 | `Long-term` | Includes any table or table partition that has not been modified for 90 consecutive days. The price of storage for that table automatically drops by approximately 50%. There is no difference in performance, durability, or availability between active and long-term storage |
 
 ## Further reading
-
+ 
 {{< partial name="whats-next/whats-next.html" >}}
 
 [1]: https://app.datadoghq.com/dashboard/ecm-es8-agw/bigquery-allocation

From 7702178d68c67a8ca859ba6ed90999cceda9a8a1 Mon Sep 17 00:00:00 2001
From: kaylawan2 <kayla.wan@datadoghq.com>
Date: Thu, 31 Jul 2025 16:49:12 -0400
Subject: [PATCH 17/24] Update bigquery.md

---
 .../en/cloud_cost_management/cost_allocation/bigquery.md  | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/content/en/cloud_cost_management/cost_allocation/bigquery.md b/content/en/cloud_cost_management/cost_allocation/bigquery.md
index 4275c84543797..c1e1d45074944 100644
--- a/content/en/cloud_cost_management/cost_allocation/bigquery.md
+++ b/content/en/cloud_cost_management/cost_allocation/bigquery.md
@@ -92,8 +92,8 @@ Costs are allocated into the following spend types:
 
 | Spend type | Description |
 |---|---|
-| `Usage` | Cost of query execution based on bytes processed (on-demand) or slot consumption (reservation) |
-| `Cluster_idle` | Cost of reserved slots allocated within a project but not utilized by queries|
+| Usage | Cost of query execution based on bytes processed (on-demand) or slot consumption (reservation) |
+| Cluster_idle | Cost of reserved slots allocated within a project but not utilized by queries|
 
 ### Storage
 
@@ -101,8 +101,8 @@ Storage costs are categorized as:
 
 | Spend type | Description |
 |---|---|
-| `Active` | Includes any table or table partition that has been modified in the last 90 days |
-| `Long-term` | Includes any table or table partition that has not been modified for 90 consecutive days. The price of storage for that table automatically drops by approximately 50%. There is no difference in performance, durability, or availability between active and long-term storage |
+| Active | Includes any table or table partition that has been modified in the last 90 days |
+| Long-term | Includes any table or table partition that has not been modified for 90 consecutive days. The price of storage for that table automatically drops by approximately 50%. There is no difference in performance, durability, or availability between active and long-term storage |
 
 ## Further reading
  

From 28665e423d9a8ad6b90a79eef1ca74cd78055ccd Mon Sep 17 00:00:00 2001
From: Kayla Wan <kayla.wan@datadoghq.com>
Date: Thu, 31 Jul 2025 18:24:08 -0400
Subject: [PATCH 18/24] some pr fixed

---
 .../cost_allocation/bigquery.md               | 24 ++++++++++++++-----
 1 file changed, 18 insertions(+), 6 deletions(-)

diff --git a/content/en/cloud_cost_management/cost_allocation/bigquery.md b/content/en/cloud_cost_management/cost_allocation/bigquery.md
index c1e1d45074944..5063ed91c4e1b 100644
--- a/content/en/cloud_cost_management/cost_allocation/bigquery.md
+++ b/content/en/cloud_cost_management/cost_allocation/bigquery.md
@@ -9,10 +9,19 @@ further_reading:
 
 ## Overview
 
-Datadog Cloud Cost Management (CCM) automatically allocates the costs of your Google BigQuery resources to individual queries and workloads. Use cost metrics enriched with tags from queries, projects, and reservations to visualize BigQuery workload costs in the context of your entire cloud bill.
+Datadog Cloud Cost Management (CCM) automatically allocates the costs of your Google BigQuery resources to individual queries and workloads. Use cost metrics enriched with tags from queries, projects, and reservations to visualize BigQuery workload costs in the context of your entire cloud bill. CCM displays costs for resources including query-level analysis, storage, and data transfer on the [**BigQuery** dashboard][1].
 
-## Resources
-CCM allocates costs for BigQuery resources for both types of Analysis costs (on-demand and reservation-based). CCM displays costs for resources including query-level analysis, storage, and data transfer on the [**BigQuery** dashboard][1].
+## BigQuery pricing models
+
+BigQuery offers two primary pricing models for query processing:
+
+**On-demand queries**: You pay per query based on the amount of data processed. Costs are directly attributed to individual queries with no upfront commitment.
+
+**Reservation-based queries**: You purchase dedicated processing capacity (slots) in advance at a fixed cost. Multiple queries can share this reserved capacity, making cost attribution more complex but potentially more cost-effective for consistent workloads.
+
+CCM allocates and enriches costs for both pricing models, providing detailed cost attribution and tagging regardless of which model you use.
+
+Learn more about BigQuery services and pricing models [**here**][3].
 
 ## Prerequisites
 
@@ -20,12 +29,13 @@ The following table presents the list of collected features and the minimal requ
 
 | Feature | Requirements |
 |---|---|
-| Retrieve tags from labels of a query | Supported without monitoring or reservations |
+| Retrieve tags from labels of a query | GCP CCM costs must be setup. Supported without monitoring or reservations. |
 | Query-Level Cost Attribution | BigQuery monitoring enabled |
 | Reservation Cost Allocation | BigQuery reservations configured |
 
 1. Configure the Google Cloud Cost Management integration on the [Cloud Cost Setup page][2].
-2. Enable BigQuery monitoring in your Google Cloud project.
+2. Enable BigQuery monitoring in your Google Cloud project. 
+[**Enable BigQuery monitoring here**][4]
 3. For reservation cost allocation, configure BigQuery reservations in your project.
 
 ## Allocating costs
@@ -43,7 +53,7 @@ Where:
 - `total_slot_usage`: The total slot-seconds used across all queries in the project's reservations
 - `total_project_reservation_cost`: The total cost of the reservations in a given project for the time period
 
-Any difference between the total billed reservation cost and the sum of allocated query costs is categorized as a project's `cluster_idle` cost, representing unused reservation capacity. 
+Any difference between the total billed reservation cost and the sum of allocated query costs is categorized as a project's idle cost, representing unused reservation capacity. These costs are tagged with `allocated_spend_type:cluster_idle`, while actual query execution costs (both reservation and on-demand) are tagged with `allocated_spend_type:usage`. 
 
 ### Understanding idle costs
 
@@ -110,3 +120,5 @@ Storage costs are categorized as:
 
 [1]: https://app.datadoghq.com/dashboard/ecm-es8-agw/bigquery-allocation
 [2]: https://app.datadoghq.com/cost/setup 
+[3]: https://cloud.google.com/bigquery/pricing?hl=en
+[4]: https://docs.datadoghq.com/integrations/google-cloud-bigquery/
\ No newline at end of file

From 9f14e0be02ce9515b24bf3f5f42025ceacc448a6 Mon Sep 17 00:00:00 2001
From: kaylawan2 <kayla.wan@datadoghq.com>
Date: Fri, 1 Aug 2025 10:10:54 -0400
Subject: [PATCH 19/24] Update bigquery.md

---
 .../cost_allocation/bigquery.md               | 32 +++++++++++++------
 1 file changed, 23 insertions(+), 9 deletions(-)

diff --git a/content/en/cloud_cost_management/cost_allocation/bigquery.md b/content/en/cloud_cost_management/cost_allocation/bigquery.md
index 5063ed91c4e1b..a2afedcb886b5 100644
--- a/content/en/cloud_cost_management/cost_allocation/bigquery.md
+++ b/content/en/cloud_cost_management/cost_allocation/bigquery.md
@@ -65,9 +65,11 @@ Idle costs represent the portion of reservation capacity that was paid for but n
 - The original project pays full reservation costs regardless of cross-project usage
 - No automatic cost-transfer: Sharing projects don't pay the reservation owner for consumed idle slots
 
+[**Learn how to enable idle slot sharing for your reservations**][5]
+
 ### Query-level tag extraction
 
-CCM extracts the following tags from BigQuery query logs via the Data Observability platform:
+When the [Datadog Google BigQuery integration][4] is enabled, CCM extracts the following tags to add to your query costs:
 
 | Tag | Description |
 |---|---|
@@ -75,6 +77,13 @@ CCM extracts the following tags from BigQuery query logs via the Data Observabil
 | `user_email` | The user or service account that executed the query |
 | `dts_config_id` | Identifier for scheduled queries and data transfers |
 
+To identify which BigQuery schedule a `DTS_CONFIG_ID` refers to:
+
+1.  Go to **BigQuery** in the [**GCP Console**][6].
+2.  Navigate to **Transfers > Schedules**.
+3.  Use the **search bar** or **Ctrl+F** to locate the `DTS_CONFIG_ID`.
+4.  Click the matched entry to view details about the query schedule, including source, frequency, and target dataset.
+
 Additionally, CCM adds the following tags for cost analysis:
 
 | Tag | Description |
@@ -82,10 +91,13 @@ Additionally, CCM adds the following tags for cost analysis:
 | `allocated_spend_type` | Categorizes costs as either `usage` (active query execution) or `cluster_idle` (unused reservation capacity) |
 | `allocated_resource` | Indicates resource measurement type - `slots` for reservation-based queries or `bytes_processed` for on-demand queries |
 | `orchestrator` | Set to `BigQuery` for all BigQuery query-related records |
+| `project_id` | GCP project ID where the BigQuery resource or job is located |
+| `google_location` | The specific Google Cloud region or zone where BigQuery resources are deployed (e.g., us-central1, europe-west1, asia-southeast1) |
+| `resource_name` | Full Google Cloud resource identifier |
 
 ### Compute allocation
 
-For BigQuery compute allocation, CCM handles two pricing models:
+For BigQuery compute allocation, CCM handles two [**pricing models**][3]:
 
 **On-demand pricing**:
 - Costs are directly attributed to individual queries based on bytes processed
@@ -102,8 +114,8 @@ Costs are allocated into the following spend types:
 
 | Spend type | Description |
 |---|---|
-| Usage | Cost of query execution based on bytes processed (on-demand) or slot consumption (reservation) |
-| Cluster_idle | Cost of reserved slots allocated within a project but not utilized by queries|
+| `allocated_spend_type`: Usage | Cost of query execution based on bytes processed (on-demand) or slot consumption (reservation) |
+| `allocated_spend_type`: Cluster_idle | Cost of reserved slots allocated within a project but not utilized by queries|
 
 ### Storage
 
@@ -111,14 +123,16 @@ Storage costs are categorized as:
 
 | Spend type | Description |
 |---|---|
-| Active | Includes any table or table partition that has been modified in the last 90 days |
-| Long-term | Includes any table or table partition that has not been modified for 90 consecutive days. The price of storage for that table automatically drops by approximately 50%. There is no difference in performance, durability, or availability between active and long-term storage |
+| `google_usage_type`: Active Logical Storage | Includes any table or table partition that has been modified in the last 90 days |
+| `google_usage_type`: Long Term Logical Storage | Includes any table or table partition that has not been modified for 90 consecutive days. The price of storage for that table automatically drops by approximately 50%. There is no difference in performance, durability, or availability between active and long-term storage |
 
 ## Further reading
  
 {{< partial name="whats-next/whats-next.html" >}}
 
-[1]: https://app.datadoghq.com/dashboard/ecm-es8-agw/bigquery-allocation
-[2]: https://app.datadoghq.com/cost/setup 
+[1]: /dashboard/ecm-es8-agw/bigquery-allocation
+[2]: /cost/setup 
 [3]: https://cloud.google.com/bigquery/pricing?hl=en
-[4]: https://docs.datadoghq.com/integrations/google-cloud-bigquery/
\ No newline at end of file
+[4]: https://docs.datadoghq.com/integrations/google-cloud-bigquery/
+[5]: https://cloud.google.com/bigquery/docs/reservations-tasks
+[6]: https://console.cloud.google.com

From a179e665ad765dbf19b93702ccccc94a7ff35579 Mon Sep 17 00:00:00 2001
From: kaylawan2 <kayla.wan@datadoghq.com>
Date: Fri, 1 Aug 2025 10:22:40 -0400
Subject: [PATCH 20/24] Update bigquery.md

---
 .../cost_allocation/bigquery.md               | 81 ++++++++++---------
 1 file changed, 45 insertions(+), 36 deletions(-)

diff --git a/content/en/cloud_cost_management/cost_allocation/bigquery.md b/content/en/cloud_cost_management/cost_allocation/bigquery.md
index a2afedcb886b5..043d5f125ae9b 100644
--- a/content/en/cloud_cost_management/cost_allocation/bigquery.md
+++ b/content/en/cloud_cost_management/cost_allocation/bigquery.md
@@ -36,36 +36,33 @@ The following table presents the list of collected features and the minimal requ
 1. Configure the Google Cloud Cost Management integration on the [Cloud Cost Setup page][2].
 2. Enable BigQuery monitoring in your Google Cloud project. 
 [**Enable BigQuery monitoring here**][4]
-3. For reservation cost allocation, configure BigQuery reservations in your project.
+3. For reservation cost allocation, configure BigQuery reservations in your project. [**Learn about BigQuery reservations**][7]
 
 ## Allocating costs
 
-Cost allocation divides BigQuery costs from GCP into individual queries and workloads associated with them. These divided costs are enriched with tags from queries, projects, and reservations so you can break down costs by any associated dimensions. 
-
-For reservation-based BigQuery costs, CCM allocates costs proportionally based on slot usage. Each query's cost is determined by its share of the total slot usage within the project's reservations. For example, if a query uses 25% of the total consumed slots in a project's reservation during a given period, it will be allocated 25% of that project's total reservation cost for that period. The cost per-query is calculated using the following formula:
-
-```
-cost_per_query = (query_slot_usage / total_slot_usage) * total_project_reservation_cost
-```
+### Compute allocation
 
-Where:
-- `query_slot_usage`: The number of slot-seconds consumed by an individual query
-- `total_slot_usage`: The total slot-seconds used across all queries in the project's reservations
-- `total_project_reservation_cost`: The total cost of the reservations in a given project for the time period
+For BigQuery compute allocation, CCM handles two [**pricing models**][3]:
 
-Any difference between the total billed reservation cost and the sum of allocated query costs is categorized as a project's idle cost, representing unused reservation capacity. These costs are tagged with `allocated_spend_type:cluster_idle`, while actual query execution costs (both reservation and on-demand) are tagged with `allocated_spend_type:usage`. 
+**On-demand pricing**:
+- Costs are directly attributed to individual queries based on bytes processed
+- Includes query-level tags for detailed cost attribution
 
-### Understanding idle costs
+**Reservation-based pricing**:
+- Costs of reserved slots are allocated proportionally to queries using those slots
+- Allocation based on slot consumption (`total_slot_ms`) per query
+- Includes idle cost calculation for unused reservation capacity
 
-Idle costs represent the portion of reservation capacity that was paid for but not utilized by queries. These costs arise when the reserved slot capacity exceeds actual usage during a billing period.
+[**Learn more about optimizing BigQuery performance and costs**][8]
 
-**Idle slot sharing considerations**: If your organization has enabled idle slot sharing between reservations, the idle cost calculation may appear different than expected. When queries from one project use idle slots from another project's reservation, those slot costs are attributed as "free" rather than to the consuming project. This means:
+### Compute
 
-- A project's reservation may show higher idle costs if other projects are using its unused capacity
-- The original project pays full reservation costs regardless of cross-project usage
-- No automatic cost-transfer: Sharing projects don't pay the reservation owner for consumed idle slots
+Costs are allocated into the following spend types:
 
-[**Learn how to enable idle slot sharing for your reservations**][5]
+| Spend type | Description |
+|---|---|
+| `allocated_spend_type`: Usage | Cost of query execution based on bytes processed (on-demand) or slot consumption (reservation) |
+| `allocated_spend_type`: Cluster_idle | Cost of reserved slots allocated within a project but not utilized by queries|
 
 ### Query-level tag extraction
 
@@ -95,27 +92,34 @@ Additionally, CCM adds the following tags for cost analysis:
 | `google_location` | The specific Google Cloud region or zone where BigQuery resources are deployed (e.g., us-central1, europe-west1, asia-southeast1) |
 | `resource_name` | Full Google Cloud resource identifier |
 
-### Compute allocation
+### Query-level allocation
 
-For BigQuery compute allocation, CCM handles two [**pricing models**][3]:
+Cost allocation divides BigQuery costs from GCP into individual queries and workloads associated with them. These divided costs are enriched with tags from queries, projects, and reservations so you can break down costs by any associated dimensions. 
 
-**On-demand pricing**:
-- Costs are directly attributed to individual queries based on bytes processed
-- Includes query-level tags for detailed cost attribution
+For reservation-based BigQuery costs, CCM allocates costs proportionally based on slot usage. Each query's cost is determined by its share of the total slot usage within the project's reservations. For example, if a query uses 25% of the total consumed slots in a project's reservation during a given period, it will be allocated 25% of that project's total reservation cost for that period. The cost per-query is calculated using the following formula:
 
-**Reservation-based pricing**:
-- Costs of reserved slots are allocated proportionally to queries using those slots
-- Allocation based on slot consumption (`total_slot_ms`) per query
-- Includes idle cost calculation for unused reservation capacity
+```
+cost_per_query = (query_slot_usage / total_slot_usage) * total_project_reservation_cost
+```
 
-### Compute
+Where:
+- `query_slot_usage`: The number of slot-seconds consumed by an individual query
+- `total_slot_usage`: The total slot-seconds used across all queries in the project's reservations
+- `total_project_reservation_cost`: The total cost of the reservations in a given project for the time period
 
-Costs are allocated into the following spend types:
+Any difference between the total billed reservation cost and the sum of allocated query costs is categorized as a project's idle cost, representing unused reservation capacity. These costs are tagged with `allocated_spend_type:cluster_idle`, while actual query execution costs (both reservation and on-demand) are tagged with `allocated_spend_type:usage`. 
 
-| Spend type | Description |
-|---|---|
-| `allocated_spend_type`: Usage | Cost of query execution based on bytes processed (on-demand) or slot consumption (reservation) |
-| `allocated_spend_type`: Cluster_idle | Cost of reserved slots allocated within a project but not utilized by queries|
+### Understanding idle costs
+
+Idle costs represent the portion of reservation capacity that was paid for but not utilized by queries. These costs arise when the reserved slot capacity exceeds actual usage during a billing period.
+
+**Idle slot sharing considerations**: If your organization has enabled idle slot sharing between reservations, the idle cost calculation may appear different than expected. When queries from one project use idle slots from another project's reservation, those slot costs are attributed as "free" rather than to the consuming project. This means:
+
+- A project's reservation may show higher idle costs if other projects are using its unused capacity
+- The original project pays full reservation costs regardless of cross-project usage
+- No automatic cost-transfer: Sharing projects don't pay the reservation owner for consumed idle slots
+
+[**Learn how to enable idle slot sharing for your reservations**][5]
 
 ### Storage
 
@@ -126,8 +130,10 @@ Storage costs are categorized as:
 | `google_usage_type`: Active Logical Storage | Includes any table or table partition that has been modified in the last 90 days |
 | `google_usage_type`: Long Term Logical Storage | Includes any table or table partition that has not been modified for 90 consecutive days. The price of storage for that table automatically drops by approximately 50%. There is no difference in performance, durability, or availability between active and long-term storage |
 
+[**Learn about BigQuery storage best practices**][9]
+
 ## Further reading
- 
+
 {{< partial name="whats-next/whats-next.html" >}}
 
 [1]: /dashboard/ecm-es8-agw/bigquery-allocation
@@ -136,3 +142,6 @@ Storage costs are categorized as:
 [4]: https://docs.datadoghq.com/integrations/google-cloud-bigquery/
 [5]: https://cloud.google.com/bigquery/docs/reservations-tasks
 [6]: https://console.cloud.google.com
+[7]: https://cloud.google.com/bigquery/docs/reservations-intro
+[8]: https://cloud.google.com/bigquery/docs/best-practices-performance-overview
+[9]: https://cloud.google.com/bigquery/docs/best-practices-storage

From 3818a0f732213dec0d62b75617e61ac4a4206e5e Mon Sep 17 00:00:00 2001
From: kaylawan2 <kayla.wan@datadoghq.com>
Date: Fri, 1 Aug 2025 13:58:29 -0400
Subject: [PATCH 21/24] Update bigquery.md

---
 .../cost_allocation/bigquery.md               | 36 ++++++++++++++++++-
 1 file changed, 35 insertions(+), 1 deletion(-)

diff --git a/content/en/cloud_cost_management/cost_allocation/bigquery.md b/content/en/cloud_cost_management/cost_allocation/bigquery.md
index 043d5f125ae9b..f3d089f15693e 100644
--- a/content/en/cloud_cost_management/cost_allocation/bigquery.md
+++ b/content/en/cloud_cost_management/cost_allocation/bigquery.md
@@ -9,7 +9,9 @@ further_reading:
 
 ## Overview
 
-Datadog Cloud Cost Management (CCM) automatically allocates the costs of your Google BigQuery resources to individual queries and workloads. Use cost metrics enriched with tags from queries, projects, and reservations to visualize BigQuery workload costs in the context of your entire cloud bill. CCM displays costs for resources including query-level analysis, storage, and data transfer on the [**BigQuery** dashboard][1].
+Datadog Cloud Cost Management (CCM) automatically allocates the costs of your Google BigQuery resources to individual queries and workloads. Use cost metrics enriched with tags from queries, projects, and reservations to visualize BigQuery workload costs in the context of your entire cloud bill. 
+
+CCM displays costs for resources including query-level analysis, storage, and data transfer on the [**BigQuery dashboard**][1].
 
 ## BigQuery pricing models
 
@@ -88,10 +90,41 @@ Additionally, CCM adds the following tags for cost analysis:
 | `allocated_spend_type` | Categorizes costs as either `usage` (active query execution) or `cluster_idle` (unused reservation capacity) |
 | `allocated_resource` | Indicates resource measurement type - `slots` for reservation-based queries or `bytes_processed` for on-demand queries |
 | `orchestrator` | Set to `BigQuery` for all BigQuery query-related records |
+
+The tags below are automatically tagged from the billing data CCM processes and can be especially useful in BigQuery cost analysis: 
 | `project_id` | GCP project ID where the BigQuery resource or job is located |
 | `google_location` | The specific Google Cloud region or zone where BigQuery resources are deployed (e.g., us-central1, europe-west1, asia-southeast1) |
 | `resource_name` | Full Google Cloud resource identifier |
 
+#### Using BigQuery labels for cost attribution
+
+BigQuery labels provide a powerful way to add custom metadata to your queries, jobs, datasets, and tables that automatically appear as tags in CCM. This enables highly granular cost attribution across teams, projects, applications, or any custom dimension you define.
+
+**What are BigQuery labels?**
+Labels are key-value pairs that you can attach to BigQuery resources. When you add labels to queries or jobs, they automatically become available as tags in CCM, allowing you to filter and group costs by these custom dimensions.
+
+**Adding labels to queries:**
+You can add labels to BigQuery queries using the `--label` flag with the `bq` command-line tool:
+
+```bash
+bq query --label department:engineering --label environment:production 'SELECT * FROM dataset.table'
+```
+
+**Adding labels in SQL sessions:**
+For queries within a session, you can set labels that apply to all subsequent queries:
+
+```sql
+SET @@query_label = "team:data_science,cost_center:analytics";
+```
+
+**Benefits for cost management:**
+- **Team attribution**: Tag queries with team names to track departmental BigQuery spending
+- **Environment tracking**: Separate development, staging, and production costs
+- **Application mapping**: Associate costs with specific applications or services
+- **Project categorization**: Group costs by business initiatives or customer projects
+
+Labels added to BigQuery resources automatically appear as tags in CCM, enabling powerful cost analysis and chargeback capabilities. [**Learn more about adding BigQuery labels**][10].
+
 ### Query-level allocation
 
 Cost allocation divides BigQuery costs from GCP into individual queries and workloads associated with them. These divided costs are enriched with tags from queries, projects, and reservations so you can break down costs by any associated dimensions. 
@@ -145,3 +178,4 @@ Storage costs are categorized as:
 [7]: https://cloud.google.com/bigquery/docs/reservations-intro
 [8]: https://cloud.google.com/bigquery/docs/best-practices-performance-overview
 [9]: https://cloud.google.com/bigquery/docs/best-practices-storage
+[10]: https://cloud.google.com/bigquery/docs/adding-labels

From 7614992a57e75a459de5ca7d5f3aea1606785642 Mon Sep 17 00:00:00 2001
From: kaylawan2 <kayla.wan@datadoghq.com>
Date: Fri, 1 Aug 2025 14:06:50 -0400
Subject: [PATCH 22/24] Update bigquery.md

---
 .../cost_allocation/bigquery.md               | 26 ++++++-------------
 1 file changed, 8 insertions(+), 18 deletions(-)

diff --git a/content/en/cloud_cost_management/cost_allocation/bigquery.md b/content/en/cloud_cost_management/cost_allocation/bigquery.md
index f3d089f15693e..e1da04c7d2663 100644
--- a/content/en/cloud_cost_management/cost_allocation/bigquery.md
+++ b/content/en/cloud_cost_management/cost_allocation/bigquery.md
@@ -17,13 +17,18 @@ CCM displays costs for resources including query-level analysis, storage, and da
 
 BigQuery offers two primary pricing models for query processing:
 
-**On-demand queries**: You pay per query based on the amount of data processed. Costs are directly attributed to individual queries with no upfront commitment.
+**On-demand queries**: You pay per query based on the amount of data processed.
+- Costs are directly attributed to individual queries based on bytes processed
+- Includes query-level tags for detailed cost attribution
 
 **Reservation-based queries**: You purchase dedicated processing capacity (slots) in advance at a fixed cost. Multiple queries can share this reserved capacity, making cost attribution more complex but potentially more cost-effective for consistent workloads.
+- Costs of reserved slots are allocated proportionally to queries using those slots
+- Allocation based on slot consumption (`total_slot_ms`) per query
+- Includes idle cost calculation for unused reservation capacity
 
-CCM allocates and enriches costs for both pricing models, providing detailed cost attribution and tagging regardless of which model you use.
+CCM allocates and enriches costs for both pricing models, providing detailed cost attribution and tagging regardless of which model you use. Learn more about BigQuery services and pricing models [**here**][3].
 
-Learn more about BigQuery services and pricing models [**here**][3].
+[**Learn more about optimizing BigQuery performance and costs**][8]
 
 ## Prerequisites
 
@@ -42,21 +47,6 @@ The following table presents the list of collected features and the minimal requ
 
 ## Allocating costs
 
-### Compute allocation
-
-For BigQuery compute allocation, CCM handles two [**pricing models**][3]:
-
-**On-demand pricing**:
-- Costs are directly attributed to individual queries based on bytes processed
-- Includes query-level tags for detailed cost attribution
-
-**Reservation-based pricing**:
-- Costs of reserved slots are allocated proportionally to queries using those slots
-- Allocation based on slot consumption (`total_slot_ms`) per query
-- Includes idle cost calculation for unused reservation capacity
-
-[**Learn more about optimizing BigQuery performance and costs**][8]
-
 ### Compute
 
 Costs are allocated into the following spend types:

From 187f9e81af7d467209887214ba13476f2e6bda1e Mon Sep 17 00:00:00 2001
From: kaylawan2 <kayla.wan@datadoghq.com>
Date: Fri, 1 Aug 2025 14:08:39 -0400
Subject: [PATCH 23/24] Update bigquery.md

---
 .../cost_allocation/bigquery.md                     | 13 +++++++++++--
 1 file changed, 11 insertions(+), 2 deletions(-)

diff --git a/content/en/cloud_cost_management/cost_allocation/bigquery.md b/content/en/cloud_cost_management/cost_allocation/bigquery.md
index e1da04c7d2663..562762fc37a6e 100644
--- a/content/en/cloud_cost_management/cost_allocation/bigquery.md
+++ b/content/en/cloud_cost_management/cost_allocation/bigquery.md
@@ -15,7 +15,9 @@ CCM displays costs for resources including query-level analysis, storage, and da
 
 ## BigQuery pricing models
 
-BigQuery offers two primary pricing models for query processing:
+BigQuery offers multiple pricing components, with CCM focusing on query-related processing costs:
+
+**Query Processing:**
 
 **On-demand queries**: You pay per query based on the amount of data processed.
 - Costs are directly attributed to individual queries based on bytes processed
@@ -26,7 +28,14 @@ BigQuery offers two primary pricing models for query processing:
 - Allocation based on slot consumption (`total_slot_ms`) per query
 - Includes idle cost calculation for unused reservation capacity
 
-CCM allocates and enriches costs for both pricing models, providing detailed cost attribution and tagging regardless of which model you use. Learn more about BigQuery services and pricing models [**here**][3].
+**Other BigQuery Costs (Not Currently Allocated):**
+- **Storage**: Charges for data stored in BigQuery tables (active and long-term storage)
+- **Streaming**: Costs for real-time data ingestion via streaming inserts
+- **Data Transfer**: Charges for moving data between regions or exporting data
+- **BI Engine**: Costs for in-memory analytics acceleration
+- **Other services**: ML training, routine executions, and additional BigQuery features
+
+CCM allocates and enriches costs for both query-processing pricing models, providing detailed cost attribution and tagging for your BigQuery analysis workloads. Learn more about BigQuery services and pricing models [**here**][3].
 
 [**Learn more about optimizing BigQuery performance and costs**][8]
 

From 1dbb799f81a957020300d78e233e8fee0e301977 Mon Sep 17 00:00:00 2001
From: kaylawan2 <kayla.wan@datadoghq.com>
Date: Fri, 1 Aug 2025 15:54:11 -0400
Subject: [PATCH 24/24] Update bigquery.md

---
 .../cost_allocation/bigquery.md               | 19 +++++++++++--------
 1 file changed, 11 insertions(+), 8 deletions(-)

diff --git a/content/en/cloud_cost_management/cost_allocation/bigquery.md b/content/en/cloud_cost_management/cost_allocation/bigquery.md
index 562762fc37a6e..bc84f08a5833b 100644
--- a/content/en/cloud_cost_management/cost_allocation/bigquery.md
+++ b/content/en/cloud_cost_management/cost_allocation/bigquery.md
@@ -15,9 +15,9 @@ CCM displays costs for resources including query-level analysis, storage, and da
 
 ## BigQuery pricing models
 
-BigQuery offers multiple pricing components, with CCM focusing on query-related processing costs:
+BigQuery offers multiple pricing components, with CCM focusing on query-related processing costs.
 
-**Query Processing:**
+### Query Processing
 
 **On-demand queries**: You pay per query based on the amount of data processed.
 - Costs are directly attributed to individual queries based on bytes processed
@@ -28,7 +28,7 @@ BigQuery offers multiple pricing components, with CCM focusing on query-related
 - Allocation based on slot consumption (`total_slot_ms`) per query
 - Includes idle cost calculation for unused reservation capacity
 
-**Other BigQuery Costs (Not Currently Allocated):**
+**Other BigQuery Costs:**
 - **Storage**: Charges for data stored in BigQuery tables (active and long-term storage)
 - **Streaming**: Costs for real-time data ingestion via streaming inserts
 - **Data Transfer**: Charges for moving data between regions or exporting data
@@ -37,7 +37,7 @@ BigQuery offers multiple pricing components, with CCM focusing on query-related
 
 CCM allocates and enriches costs for both query-processing pricing models, providing detailed cost attribution and tagging for your BigQuery analysis workloads. Learn more about BigQuery services and pricing models [**here**][3].
 
-[**Learn more about optimizing BigQuery performance and costs**][8]
+[**Learn more about optimizing BigQuery performance and costs.**][8]
 
 ## Prerequisites
 
@@ -52,7 +52,7 @@ The following table presents the list of collected features and the minimal requ
 1. Configure the Google Cloud Cost Management integration on the [Cloud Cost Setup page][2].
 2. Enable BigQuery monitoring in your Google Cloud project. 
 [**Enable BigQuery monitoring here**][4]
-3. For reservation cost allocation, configure BigQuery reservations in your project. [**Learn about BigQuery reservations**][7]
+3. For reservation cost allocation, configure BigQuery reservations in your project. [**Learn about BigQuery reservations.**][7]
 
 ## Allocating costs
 
@@ -91,11 +91,14 @@ Additionally, CCM adds the following tags for cost analysis:
 | `orchestrator` | Set to `BigQuery` for all BigQuery query-related records |
 
 The tags below are automatically tagged from the billing data CCM processes and can be especially useful in BigQuery cost analysis: 
+
+| Tag | Description |
+|---|---|
 | `project_id` | GCP project ID where the BigQuery resource or job is located |
 | `google_location` | The specific Google Cloud region or zone where BigQuery resources are deployed (e.g., us-central1, europe-west1, asia-southeast1) |
 | `resource_name` | Full Google Cloud resource identifier |
 
-#### Using BigQuery labels for cost attribution
+### Using BigQuery labels for cost attribution
 
 BigQuery labels provide a powerful way to add custom metadata to your queries, jobs, datasets, and tables that automatically appear as tags in CCM. This enables highly granular cost attribution across teams, projects, applications, or any custom dimension you define.
 
@@ -151,7 +154,7 @@ Idle costs represent the portion of reservation capacity that was paid for but n
 - The original project pays full reservation costs regardless of cross-project usage
 - No automatic cost-transfer: Sharing projects don't pay the reservation owner for consumed idle slots
 
-[**Learn how to enable idle slot sharing for your reservations**][5]
+[**Learn how to enable idle slot sharing for your reservations.**][5]
 
 ### Storage
 
@@ -162,7 +165,7 @@ Storage costs are categorized as:
 | `google_usage_type`: Active Logical Storage | Includes any table or table partition that has been modified in the last 90 days |
 | `google_usage_type`: Long Term Logical Storage | Includes any table or table partition that has not been modified for 90 consecutive days. The price of storage for that table automatically drops by approximately 50%. There is no difference in performance, durability, or availability between active and long-term storage |
 
-[**Learn about BigQuery storage best practices**][9]
+[**Learn more about BigQuery storage and best practices.**][9]
 
 ## Further reading