| Billing |
|
| Business Units |
When copying business units from production to a sandbox, the behavior of CMS
workspaces depends on the sandbox type.
- Full Sandbox: CMS workspaces are replicated. Therefore, the relationships
between business units and CMS workspaces are preserved and copied
automatically.
- Other Sandbox Types (Developer or Partial): CMS workspaces aren’t copied. In
these environments, workspaces must be manually re-created, and their
relationships with business units must be re-established.
|
| Unified Messaging |
- When testing an SMS campaign in a sandbox, don't use the same sender code that
you use in production. Instead, in your production org, acquire a dedicated
sender code for sandbox testing. Then, to use the new sender code in your
sandbox, refresh the sandbox. See Set Up an SMS Unified Messaging Channel.
- A sender code can be active in only one org at a time. You can activate or
deactivate a sender code from within each sandbox.
- Email, mobile app messaging, and WhatsApp require unique configurations in
each sandbox. For example, a sandbox requires its own authenticated domain and
From addresses for email, as well as its own tracking domains, WhatsApp number,
and blockout windows. These settings can't be deployed from one org to
another.
|
| Marketing content |
- Due to storage limits in Developer, Developer Pro, and Partial Copy sandboxes,
content and digital assets in the CMS Marketing workspace aren’t copied over
when a sandbox is created or refreshed. To move content, use change sets or create an import.
- Workspaces are deployed in the Digital Experience Bundle component. Content
and digital assets related to content (such as images) are deployed in the
Digital Experience component.
- To make the content records easier to find in the Digital Experience
component, enter a descriptive API name when creating content on the Content tab or through Connect API. Otherwise, the system
automatically populates the field with a system-generated content key, which
can't be changed.
- To deploy content, the target org must have a workspace. You can deploy the
workspace with its content, or deploy the workspace first and then its
content.
- You can’t deploy a folder by itself. However, when you deploy a folder’s
content (such as an email template), the entire folder path deploys with it.
- To deploy an image, make sure it's related to an email, MMS message, RCS
message, WhatsApp message, or landing page. If an image isn't related to
content, it isn’t available to add in the Digital Experience component.
|
| Marketing flows |
- Deploy marketing flows in draft status. After you test a flow, save it as a
new version. The new version starts in draft status.
|
| Tests with customer engagement data |
To test custom reports or event-based flows, add behavior and
messaging events to your sandbox. Create a CSV file with the necessary fields mapped
to Data 360 DMOs, and import it by using the File Upload data
stream. See Ingest Data by Uploading a File. |