Salesforce Data 360 (formerly Data Cloud) empowers organizations to unify and harmonize vast amounts of data. Managing and deploying the configurations that define your Data Cloud instance is crucial for maintaining consistency across your Salesforce landscape.
Gearset simplifies this process by providing comprehensive support for Data 360 deployments through Salesforce's robust Metadata API.
Data 360 components can be selected and deployed using Gearset, directly to an org selected as the target, or to source control as part of a CI/CD Pipeline.
You can find the components in your metadata filter (see below).
Supported metadata types
The below table details all the Data 360 specific metadata currently supported, which is an expanding list and subject to regular update. If you would like us to prioritise supporting a specific metadata type please reach out over the in-app chat.
Component name | API name | Deployable via Data Kit | Individually deployable |
Activation platform Activation Attributes | Yes | No | |
Activation platform Field Value | Yes | No | |
Activation platform Identifier | Yes | No | |
Activation platform Data Connector | Yes | No | |
Activation platform | Yes | No | |
Activation platform Field | Yes | No | |
Data Stream Template | Yes | No | |
Data Source Bundle Definition | Yes | No | |
Data Package Kit Definition | Yes | No | |
Data Package Kit Object | Yes | No | |
Streaming App Data Connector | Yes | No | |
Market Data Transport Object | Yes | No | |
External Data Source | Yes | No | |
External Data Connector | Yes | No | |
Data Stream Definition | No | No | |
Data Source Tenant | Yes | No | |
Data Source Object | Yes | No | |
Data Source | Yes | No | |
Object Source Target Map | Yes | No | |
Field Source Target Relationship | Yes | No | |
Data Source Data Model Field Map | Yes | No | |
Data Connector Ingest API | Yes | No | |
Market Calculated Insight Object Definition | Yes | Yes | |
Market Segment Definition | Yes | No | |
Data Connector | Yes | No | |
Internal Data Connector | Yes | No | |
Data Kit Object Template | DataKitObjectTemplate | Yes | No |
Data Kit Object Dependency | DataKitObjectDependency | Yes | No |
Customer Data Platform Settings | Yes | No | |
Identity Resolution |
| Yes | Yes |
Machine learning retriever |
| Yes | Yes |
Search Index |
| Yes | Yes |
Data Cloud Salesforce Connector Permission Set | No - not supported by Metadata API. This permission set must be manually created in the target org. | No |
Deploying Data 360 components through Data Kits
Some Data 360 metadata types must be deployed through a DevOps Data Kit. For example: Data Libraries, Data Source Objects, and Data Lake Objects should be added into a Data Kit before deploying. Check out this document on how to deploy Data Kits with Gearset.
Deploying Data 360 components using Direct Deploy
If you want to deploy Data 360 components individually, you can use the Direct Deploy option in the metadata filter. Check out this document on how to deploy individual Data 360 components using Direct Deploy.
Deploying Data 360 metadata through pipeline
Deploying Data 360 metadata requires careful planning due to the scope, dependencies, and impact these components can have across your org. To help teams avoid unintended disruptions on any ongoing work, we strongly recommend using a Long Term Project to implement Data 360 metadata until your team is ready to release.
Check out this document for more details on Long Term Projects in Gearset Pipelines.