diff --git a/config/_default/menus/main.en.yaml b/config/_default/menus/main.en.yaml
index 1171f86370052..0df7914737fc9 100644
--- a/config/_default/menus/main.en.yaml
+++ b/config/_default/menus/main.en.yaml
@@ -3656,46 +3656,51 @@ menu:
       parent: cloud_cost_planning
       identifier: cloud_cost_planning_commitment_programs
       weight: 502
-    - name: Tag Pipelines
-      url: cloud_cost_management/tag_pipelines
+    - name: Tags
+      url: cloud_cost_management/tags
       parent: cloud_cost
-      identifier: cloud_cost_tag_pipelines
+      identifier: cloud_cost_tags
       weight: 6
     - name: Tag Explorer
-      url: cloud_cost_management/tag_explorer
-      parent: cloud_cost
+      url: cloud_cost_management/tags/tag_explorer
+      parent: cloud_cost_tags
       identifier: cloud_cost_tag_explorer
-      weight: 7
+      weight: 601
+    - name: Tag Pipelines
+      url: cloud_cost_management/tags/tag_pipelines
+      parent: cloud_cost_tags
+      identifier: cloud_cost_tag_pipelines
+      weight: 602
     - name: Multisource Querying
       url: cloud_cost_management/multisource_querying
       parent: cloud_cost
       identifier: cloud_cost_multisource_querying
-      weight: 8
+      weight: 7
     - name: Reports
       url: /cloud_cost_management/reports
       parent: cloud_cost
       identifier: cloud_cost_reports
-      weight: 9
+      weight: 8
     - name: Recommendations
       url: cloud_cost_management/recommendations
       parent: cloud_cost
       identifier: cloud_cost_recommendations
-      weight: 10
+      weight: 9
     - name: Custom Recommendations
       url: cloud_cost_management/recommendations/custom_recommendations
       parent: cloud_cost_recommendations
       identifier: cloud_cost_custom_recommendations
-      weight: 1001
+      weight: 901
     - name: Monitors
       url: /cloud_cost_management/monitors
       parent: cloud_cost
       identifier: cloud_cost_monitors
-      weight: 11
+      weight: 10
     - name: Anomalies
       url: /cloud_cost_management/anomalies
       parent: cloud_cost
       identifier: cloud_cost_anomalies
-      weight: 12
+      weight: 11
     - name: APM
       url: tracing/
       pre: apm
diff --git a/content/en/cloud_cost_management/_index.md b/content/en/cloud_cost_management/_index.md
index 4279d24dad3e3..265fb0f868ee6 100644
--- a/content/en/cloud_cost_management/_index.md
+++ b/content/en/cloud_cost_management/_index.md
@@ -19,12 +19,9 @@ further_reading:
   - link: "/monitors/types/cloud_cost/"
     tag: "Documentation"
     text: "Create a Cloud Cost monitor"
-  - link: "/cloud_cost_management/tag_pipelines/"
+  - link: "/cloud_cost_management/tags/"
     tag: "Documentation"
-    text: "Learn about Tag Pipelines"
-  - link: "/cloud_cost_management/tag_pipelines"
-    tag: "Documentation"
-    text: "Standardize tags across Cloud Cost Management with Tag Pipelines"
+    text: "Learn about Tags in Cloud Cost Management"
   - link: "https://www.datadoghq.com/blog/cloud-costs-study-learnings/"
     tag: "Blog"
     text: "Key learnings from the State of Cloud Costs study"
@@ -84,11 +81,9 @@ When creating a dashboard, select **Cloud Cost** as the data source for your sea
 
 Optionally, you can programmatically export a timeseries graph of your Datadog cost data by using the [Metrics API][2].
 
-## Create tag rules
-
-Use [Tag Pipelines][5] to ensure comprehensive cost tracking by standardizing the tags across all cloud resources. This prevents any cost data from being overlooked.
+## Tagging and cost allocation
 
-{{< img src="cloud_cost/tags_addnew.png" alt="Create a tag rule in Tag Pipelines to ensure your cloud resources use standard tags" style="width:60%;" >}}
+Use the [Tags documentation][5] to understand how tags are sourced, enriched, and managed in Cloud Cost Management.
 
 You can create tag rules to correct missing or incorrect tags and add inferred tags that align with your organization's business logic.
 
@@ -139,6 +134,6 @@ please fill out [this form][7].
 [2]: /api/latest/metrics/#query-timeseries-data-across-multiple-products
 [3]: /monitors/types/cloud_cost/
 [4]: /cloud_cost_management/container_cost_allocation
-[5]: /cloud_cost_management/tag_pipelines
+[5]: /cloud_cost_management/tags/
 [6]: /account_management/rbac/data_access/
 [7]: https://www.datadoghq.com/product-preview/data-access-control/
diff --git a/content/en/cloud_cost_management/custom_allocation_rules.md b/content/en/cloud_cost_management/custom_allocation_rules.md
index 5bf40288f4665..8f2964b5f5251 100644
--- a/content/en/cloud_cost_management/custom_allocation_rules.md
+++ b/content/en/cloud_cost_management/custom_allocation_rules.md
@@ -173,6 +173,6 @@ Changes to custom allocation rules may take up to 24 hours to be applied. After
 ## Further reading
 {{< partial name="whats-next/whats-next.html" >}}
 
-[1]: /cloud_cost_management/tag_pipelines
+[1]: /cloud_cost_management/tags/tag_pipelines
 [2]: https://app.datadoghq.com/cost/settings/custom-allocation-rules
 [3]: https://www.datadoghq.com/support/
diff --git a/content/en/cloud_cost_management/setup/aws.md b/content/en/cloud_cost_management/setup/aws.md
index 2fa962d6ce489..0ed0f1249ff18 100644
--- a/content/en/cloud_cost_management/setup/aws.md
+++ b/content/en/cloud_cost_management/setup/aws.md
@@ -262,7 +262,9 @@ In general:
 
 ## Tag enrichment
 
-Datadog adds tags to the ingested cost data using many sources, described in detail below.
+Datadog automatically enriches your AWS cost data with tags from multiple sources. For a comprehensive overview of how tags are applied to cost data, see [Tags][19].
+
+The following tag sources are available for AWS:
 
 - Cost and Usage Report columns
 - AWS Resource tags
@@ -406,7 +408,7 @@ _Requires [container cost allocation][11], and applies only to `shared.resources
 
 ### Tag pipelines
 
-Finally, all of your [tag pipeline][15] rulesets are applied, providing complete cost allocation when infrastructure tagging is not possible.
+Finally, all of your [tag pipeline][15] rulesets are applied, providing complete cost allocation when infrastructure tagging is not possible. Tag pipelines are the final enrichment layer and can override tags from other sources.
 
 ## Billing conductor
 [AWS Billing Conductor][16] is a custom billing service for AWS Marketplace Channel Partners (Partners) and organizations that have chargeback requirements.
@@ -436,7 +438,8 @@ After the billing conductor CUR is created, follow the Cloud Cost Management ins
 [12]: https://docs.aws.amazon.com/tag-editor/latest/userguide/tagging.html
 [13]: https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/activating-tags.html
 [14]: https://docs.aws.amazon.com/organizations/latest/userguide/orgs_tagging.html
-[15]: /cloud_cost_management/tag_pipelines
+[15]: /cloud_cost_management/tags/tag_pipelines
 [16]: https://docs.aws.amazon.com/billingconductor/latest/userguide/what-is-billingconductor.html
 [17]: https://app.datadoghq.com/cost/settings/accounts
-[18]: /help/
\ No newline at end of file
+[18]: /help/
+[19]: /cloud_cost_management/tags
diff --git a/content/en/cloud_cost_management/setup/azure.md b/content/en/cloud_cost_management/setup/azure.md
index e3c4a56024f2d..90895acb29bd7 100644
--- a/content/en/cloud_cost_management/setup/azure.md
+++ b/content/en/cloud_cost_management/setup/azure.md
@@ -165,7 +165,9 @@ You can visualize your ingested data using the following cost types:
 
 ### Out-of-the-box tags
 
-Datadog adds out-of-the-box tags to ingested cost data to help you further break down and allocate your costs. These tags are derived from your [usage cost report][9] and make it easier to discover and understand cost data.
+Datadog automatically enriches your Azure cost data with tags from multiple sources. For a comprehensive overview of how tags are applied to cost data, see [Tags][12].
+
+The following out-of-the-box tags are derived from your [usage cost report][9] and make it easier to discover and understand cost data:
 
 | Tag Name                         | Tag Description       |
 | ---------------------------- | ----------------- |
@@ -248,3 +250,4 @@ For example, to view cost and utilization for each Azure VM, you can make a tabl
 [9]:  https://learn.microsoft.com/en-us/azure/cost-management-billing/understand/download-azure-daily-usage
 [10]: https://docs.azure.cn/en-us/cost-management-billing/manage/resolve-past-due-balance#check-the-type-of-your-account
 [11]: /help/
+[12]: /cloud_cost_management/tags
diff --git a/content/en/cloud_cost_management/setup/google_cloud.md b/content/en/cloud_cost_management/setup/google_cloud.md
index 81c6c49af4e47..cd4debd709d0d 100644
--- a/content/en/cloud_cost_management/setup/google_cloud.md
+++ b/content/en/cloud_cost_management/setup/google_cloud.md
@@ -142,9 +142,10 @@ You can visualize your ingested data using the following cost types:
 | `gcp.cost.ondemand`                             | Total public, on-demand cost of resources before public and private discounts are applied over an interval. |
 
 ### Out-of-the-box tags
-Datadog adds out-of-the-box tags to ingested cost data to help you further break down and allocate your costs. These tags are derived from your [detailed usage cost report][16] and make it easier to discover and understand cost data.
 
-The following out-of-the-box tags are available for filtering and grouping data:
+Datadog automatically enriches your Google Cloud cost data with tags from multiple sources. For a comprehensive overview of how tags are applied to cost data, see [Tags][17].
+
+The following out-of-the-box tags are derived from your [detailed usage cost report][16] and make it easier to discover and understand cost data:
 
 | Tag Name                         | Tag Description       |
 | ---------------------------- | ----------------- |
@@ -204,3 +205,4 @@ The following out-of-the-box tags are available:
 [14]: /cloud_cost_management/container_cost_allocation/
 [15]: /cloud_cost_management/setup/google_cloud/#create-or-select-a-google-cloud-storage-bucket
 [16]: https://cloud.google.com/billing/docs/how-to/export-data-bigquery-tables/detailed-usage
+[17]: /cloud_cost_management/tags
diff --git a/content/en/cloud_cost_management/tags/_index.md b/content/en/cloud_cost_management/tags/_index.md
new file mode 100644
index 0000000000000..c7cfce3df91da
--- /dev/null
+++ b/content/en/cloud_cost_management/tags/_index.md
@@ -0,0 +1,102 @@
+---
+title: Tags
+description: Learn how tags are sourced, enriched, and managed in Cloud Cost Management.
+further_reading:
+- link: "/cloud_cost_management/"
+  tag: "Documentation"
+  text: "Learn about Cloud Cost Management"
+- link: "/cloud_cost_management/tags/tag_pipelines"
+  tag: "Documentation"
+  text: "Tag Pipelines"
+- link: "/cloud_cost_management/tags/tag_explorer"
+  tag: "Documentation"
+  text: "Tag Explorer"
+- link: "/getting_started/tagging/"
+  tag: "Documentation"
+  text: "Getting Started with Tags"
+---
+
+## Overview
+
+Tags help you organize, filter, and allocate your cloud costs effectively. Cloud Cost Management automatically enriches your cost data with tags from multiple sources, so you can focus on using tags to drive insights rather than managing the technical details. Using tags, you can allocate shared costs fairly, create accurate reports, and track costs by team, service, or environment.
+
+## Getting started
+
+Get started with tags in three steps:
+
+1. **See what you have** - Use [Tag Explorer][5] to discover which tags are already available in your cost data.
+2. **Identify gaps** - Look for missing tags that would help you track costs by team, project, or environment.
+3. **Add missing tags** - Use [Tag Pipelines][4] to automatically add tags based on your business logic.
+
+{{< img src="cloud_cost/tag_explorer/aws_1.png" alt="Tag Explorer interface showing available AWS tags and their usage" style="width:80%;" >}}
+
+## Where your tags come from
+
+Datadog applies tags to cost data using the following sources:
+
+- **[Out-of-the-box tags][1]** - Standardized tags that Datadog automatically generates from some billing data columns (like `aws_product` and `aws_region`) in your cost and usage report
+- **[Container allocation tags][2]** - Tags from your container workloads
+- **[Resource and account tags][3]** - Tags you've applied to your cloud resources
+- **[Tag pipelines][4]** - Custom rules you create to add missing tags
+
+## How tags are attached to cost data
+
+Datadog automatically associates tags with your cost data through a multi-step process as new cost data is ingested. Your cost analysis always reflects the most current tag information.
+
+1. **Data ingestion** - When cost data arrives from your cloud provider (through billing reports, APIs, and so on), Datadog identifies the specific resources and services being billed.
+2. **Tag lookup** - For each cost datapoint, Datadog looks up available tags from all configured sources (billing data, resource tags, container metadata, and so on).
+3. **Tag application** - Tags are attached to the cost data based on a precedence order:
+   - Tag Pipelines (highest priority)
+   - Container tags
+   - Resource/account tags
+   - Out-of-the-box tags
+   - Billing data (lowest priority)
+
+4. **Data storage** - The enriched cost data with all associated tags is stored and made available for analysis.
+
+## Essential tags and examples
+
+In addition to out-of-the-box tags, you can add these key tags to get the most value from your cost data:
+
+### Team and ownership tags
+- `team` - Which team owns the resource
+- `owner` - Individual responsible for the resource
+- `project` - Project or initiative the resource supports
+
+**Example: Track costs by team**
+Tag your resources with `team:engineering` or `team:marketing`, then:
+- Create dashboards showing spend by team
+- Set up alerts for unusual team spending
+- Generate monthly cost reports per team
+
+### Environment and lifecycle tags
+- `env` - Environment (prod, staging, dev)
+- `service` - Application or service name
+- `version` - Application version or release
+
+**Example: Identify unused resources**
+Use tags like `env:dev` and `purpose:testing` to:
+- Find development resources that can be stopped
+- Track costs for temporary projects
+- Clean up abandoned test environments
+
+### Business context tags
+- `cost-center` - Budget or cost center
+- `business-unit` - Business unit or department
+- `purpose` - What the resource is used for
+
+**Example: Optimize container costs**
+With container cost allocation, you can:
+- See costs broken down by pod, namespace, or deployment
+- Identify which applications are most expensive
+- Optimize resource requests and limits
+
+## Further reading
+
+{{< partial name="whats-next/whats-next.html" >}}
+
+[1]: /cloud_cost_management/multisource_querying/
+[2]: /cloud_cost_management/container_cost_allocation
+[3]: /cloud_cost_management/setup/aws/#aws-resource-tags
+[4]: /cloud_cost_management/tags/tag_pipelines
+[5]: /cloud_cost_management/tags/tag_explorer
\ No newline at end of file
diff --git a/content/en/cloud_cost_management/tag_explorer/_index.md b/content/en/cloud_cost_management/tags/tag_explorer.md
similarity index 97%
rename from content/en/cloud_cost_management/tag_explorer/_index.md
rename to content/en/cloud_cost_management/tags/tag_explorer.md
index ae94e767838d5..abe681600ca37 100644
--- a/content/en/cloud_cost_management/tag_explorer/_index.md
+++ b/content/en/cloud_cost_management/tags/tag_explorer.md
@@ -1,5 +1,7 @@
 ---
 title: Tag Explorer
+aliases:
+  - /cloud_cost_management/tag_explorer
 description: Search and manage all cost-related tags, including those from your bills, with insights into their sources.
 further_reading:
 - link: "/cloud_cost_management/"
@@ -14,7 +16,7 @@ further_reading:
 - link: "/cloud_cost_management/setup/saas_costs"
   tag: "Documentation"
   text: "Learn about SaaS Cost Integrations"
-- link: "/cloud_cost_management/tag_pipelines"
+- link: "/cloud_cost_management/tags/tag_pipelines"
   tag: "Documentation"
   text: "Learn about Tag Pipelines"
 ---
@@ -152,7 +154,7 @@ For Twilio tags, select **Twilio** from the dropdown menu on the top right corne
 
 [1]: /cloud_cost_management/
 [2]: https://app.datadoghq.com/cost/tags
-[3]: /cloud_cost_management/tag_pipelines
+[3]: /cloud_cost_management/tags/tag_pipelines
 [4]: /cloud_cost_management/setup/custom
 [5]: /cloud_cost_management/datadog_costs
 [6]: /cloud_cost_management/setup/saas_costs
diff --git a/content/en/cloud_cost_management/tag_pipelines.md b/content/en/cloud_cost_management/tags/tag_pipelines.md
similarity index 96%
rename from content/en/cloud_cost_management/tag_pipelines.md
rename to content/en/cloud_cost_management/tags/tag_pipelines.md
index 0695eba57064f..e607232599ace 100644
--- a/content/en/cloud_cost_management/tag_pipelines.md
+++ b/content/en/cloud_cost_management/tags/tag_pipelines.md
@@ -1,5 +1,7 @@
 ---
 title: Tag Pipelines
+aliases:
+  - /cloud_cost_management/tag_pipelines/
 further_reading:
 - link: "/cloud_cost_management/"
   tag: "Documentation"
@@ -81,7 +83,7 @@ Certain tags such as `env` and `host` are [reserved tags][4], and are part of [U
 Using tags helps correlate your metrics, traces, processes, and logs. Reserved tags like `host` provide visibility and effective monitoring across your infrastructure. For optimal correlation and actionable insights, use these reserved tags as part of your tagging strategy in Datadog.
 
 ## Delete tags
-To delete a tag created using Tag Pipelines, delete the rule that created it. Within 24 hours, the tag will be automatically removed from the most recent three months of data. To remove the tag from older data, request a backfill through [Datadog support][5].
+To delete a tag created using Tag Pipelines, delete the rule that created it. Within 24 hours, the tag is automatically removed from the most recent three months of data. To remove the tag from older data, request a backfill through [Datadog support][5].
 
 ## Further reading