How to deploy Marketing Cloud Next with Gearset
Marketing Cloud Next segments, calculated insights, and their data model are Data 360 metadata, so you deploy them with Gearset as a DevOps Data Kit. This article walks through the deployment.
Gearset has a dedicated Data Kit deployment method in both Pipelines and Compare and Deploy. Pick your kit and Gearset reads its manifest, builds the package including dependencies, and activates the kit in the target org after deployment.
Before you make your first deployment
There are a handful of setup steps that you will need to go through before the first time you make a Marketing Cloud Next deployment.
Enable Data 360 in both orgs. Data 360 must be provisioned in source and target.
Give the deployment user the
Data Cloud Architectpermission set in both orgs. See Permissions required to deploy Data 360 metadata.Create a matching data space in the target org. The org will have a default data space, if you've created another data space, make sure that there is a data space of the same name in the target.
Create your kit as a DevOps Data Kit. Create your data kit as a
DevOpsdata kit, not aStandardone. Standard Data Kits can't be deployed through the Metadata API.
See How to create a DevOps Data Kit? for the steps, and add every component you need, such as the segment, its calculated insights, the data model objects, and the mappings. Gearset traces the dependencies of what's in the kit, so something never added to the kit has nothing linking it there.
Deploying Marketing Cloud Next with Gearset
After creating your data kit, follow this guide to deploy your Marketing Cloud Next configuration: How to deploy data kits with Gearset
The component type name in the Salesforce UI might not match the file’s API name. This is because Salesforce auto-generates data kit component names. If you added the component to the data kit, Gearset picks it up automatically.
What this doesn't cover
Campaign flows. These are ordinary
Flowmetadata and deploy through a normal comparison. Note Salesforce's known issue: flows with consent actions or form submission triggers hold source-org record IDs and fail on deployment until those IDs are stripped from the XML, use a Gearset environment variable to make sure this doesn't happen.Setup configuration. If you need to enable Data 360 then this needs to be done in the Setup of the org, not via a deployment.
Marketing content. Emails, landing pages and forms live in a Salesforce CMS workspace and follow a different path.
If this is a new implementation you may want to consider building your changes in a Long term project in your pipeline until the team is ready to release. Long term projects require the Automation Enterprise tier.