--- cuppy_hub: salesforce cuppy_path: reference/official/data360/data-cloud-dev/guide/component-cheatsheet.md cuppy_section: docs cuppy_doc: KW48-X550 cuppy_doc_uuid: 103b3246-2380-409c-87c1-2e8e750e77ad cuppy_permalink: https://cuppy.io/salesforce/d/KW48-X550 cuppy_version: 1 cuppy_updated: 2026-10-23T16:16:52.575Z cuppy_canonical: https://cuppy.io/salesforce/docs/reference/official/data360/data-cloud-dev/guide/component-cheatsheet cuppy_mcp: https://cuppy.io/mcp cuppy_body_sha256: 9f943f363eba2c91968d97675d44001466906dd52df10da55f3b5aad2856b976 # cuppy_body_sha256 is over the document body ALONE, excluding both generated blocks. --- > Mirror of (Salesforce, Data 360 Developer Guide), read 2026-10-23. Salesforce's own page is the authority; this copy exists because that site refuses non-browser readers. Metadata is data that describes data. In Data 360, metadata includes the fields, configurations, data model objects, calculated insights, and data stream definitions that make up your Data 360 environment. Well-structured metadata helps Data 360 understand, unify, and activate your data across sources. When you build a Data 360 app or solution that you want to share or deploy across orgs, you bundle your metadata into a data kit. A data kit is a portable container of packageable Data 360 metadata — such as data stream templates, data model objects, and calculated insight definitions — organized as reusable templates that can be deployed into another org. Not all Data 360 metadata components can be added to a data kit or managed package. For the full list of supported metadata components and their packaging compatibility, see [Data 360 Metadata Types](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_data_cloud_types.htm) in Metadata API Developer Guide. --- You are reading one file. The same content is free over MCP at https://cuppy.io/mcp with no signup: ranked search across all 376 documents in this hub, the merged view when you work in a layer, known workarounds matched to the error you hit, and depth control so you spend tokens on what you need. Start with the `_hello` tool. How to connect: https://cuppy.io/salesforce/ Something wrong in this document? Report it with the `session feedback` tool on the same endpoint.