Loading
Marketing Cloud Next
Deploy Sandbox Changes in Marketing Cloud Next

Deploy Sandbox Changes in Marketing Cloud Next

After you make changes in a sandbox, deploy those changes back to the production org or to another sandbox by using Salesforce Platform DevOps features.

Required Editions

View supported editions.

User Permissions Needed
To create a sandbox:

Manage Dev Sandboxes (Developer or Developer Pro only)

OR

Manage Sandboxes (all sandbox types)

To deploy Data 360 objects: Data Cloud Architect

Some things in the sandbox aren't promoted. The schema, logic, and rules that you create in a sandbox are promoted, but the underlying data isn't. For example, you can promote and reuse the identity resolution rulesets you created, but not the unified individuals themselves. You need to re-create those related records.

Sandboxes don't promote these items:

  • Sending and engagement history
  • Segment populations or lists
  • Ingested data
  • Calculated insights, logs, and reporting data
  • Campaign records
  • Brief records
  • Subscription and consent records
  • Contact and lead records

Make sure that you deploy components in the right order. Features and assets have internal dependencies that are validated at deployment time. If the dependencies aren't met, the deployment fails. For example, if a flow references a Data 360 object or a content template, that object or template must be deployed before the flow can be deployed.

Always deploy components in this order:

  1. Deploy Data 360 objects by using one of the provided deployment methods.
    1. Select these objects for deployment: segments, DMOs, DLOs, identity resolution rulesets, data graphs, data streams, calculated insights, data actions, Personalization Points, recommenders, and engagement signals. See Deploy Data 360 Changes from a Sandbox.
    2. After deploying to the target org, activate or publish the objects.
  2. Deploy marketing content by using one of the provided deployment methods.
    1. In the Digital Experience component, select content records, email templates, brand, and images.
    2. In the Digital Experience Bundle component, select the CMS workspace.
      Deploy content records to the same CMS workspace in the target org. If the CMS workspace is already available in the target org, skip this step.
    3. After deploying to the target org, publish your content.
  3. Deploy marketing flows by selecting Flows in the Flow Definition component.

You can use any of these methods to move changes from a sandbox to production or another sandbox.

Method resources
Change Sets
DevOps Center Improve Release Quality with DevOps Testing
Metadata Retrieve and Deploy
CLI Retrieve and Deploy Salesforce CLI Setup Guide
Note
Note After content is deployed to the target org, its status is Draft, even if the status was Active or Published in the source org.
 
Chargement
Salesforce Help | Article