When a Sandbox refresh is performed by copying the configuration from an Agentforce Sales (formerly Sales Cloud) or Agentforce Service (formerly Service Cloud) Production Org, the refresh process will copy the Marketing Cloud Connect configuration of the Production org to the sandbox org. After the refresh is completed the Sandbox will have the same Marketing Cloud Connect connection information than the Production org and this could cause the Sandbox to inject records into the Marketing Cloud account’s Journeys when contacts are added in the sandbox.
Follow the steps outline below before you start a sandbox refresh to avoid this type of issue.
Note: Once the Marketing Cloud connection is complete, all previously configured items will no longer function unless they are reconfigured (including both triggered sends and synchronized data extensions). Complete the steps below to prepare for a refresh, then proceed to reconfigure any necessary items.
1. Log in to Marketing Cloud, mouse over your name and select Setup.
2. Under the Platform Tools section, select Apps | Salesforce Integration
3. Click Edit.
4. Click Disconnect Account, then click OK to disable the connector in the current sandbox org.
5. Click OK in the "this action cannot be undone" dialog box.
Now, you are ready to perform the refresh in your sandbox org.
The standard Salesforce functionality for sandbox refresh is that when customers perform a Developer Sandbox, Developer Pro Sandbox, Partial Copy or a Full Sandbox refresh all managed packages (including Marketing Cloud Connect) have their metadata copied from the production environment to the sandbox environment. For Marketing Cloud Connect, the sandbox refresh process copies all the authentication tokens and all the configuration from Salesforce Production to Salesforce sandbox. This means that the sandbox is connected to the same Marketing Cloud account than the Salesforce production org.
Once the sandbox refresh is complete and as soon as the sandbox is ready, disconnect it from Marketing cloud account connected to the Salesforce Production org by running this command et4ae5.SupportUtilities.resetConfiguration();. This command only removes the Marketing Cloud Connect configuration; this includes configuration and tokens. None of the object data is affected.
IMPORTANT: This step is necessary to avoid the sandbox org to inject contacts into the Marketing Cloud account connected to the Salesforce Production org. Please make sure it happens every time a copy/refresh occurs as soon as the sandbox is ready.
Note: Log out all Salesforce orgs before completing these steps.
Actions to perform in Marketing Cloud
Note: Log out all Salesforce orgs before completing these steps.
1. Log in to Marketing Cloud account you want to connect to the “refreshed” sandbox
2. Go to Setup section, select Apps | Salesforce Integration
3. Click Edit.
4. Click Upgrade to Connected App. If that button doesn't appear, skip this step.
5. Click Connect, then enter your sandbox org login credentials.
6. Confirm that your Salesforce Org ID is correct (found under Setup | Administer | Company Profile | Company Information in Salesforce)
7. Integrate the API user:
8. If you have any other users who need access to Marketing Cloud via Sales or Service, integrate them using the "API user" steps above.
1. Log in to Sales or Service, then click the Marketing Cloud tab.
2. Click Configure Marketing Cloud Connector.
3. Confirm that the API user is correct. If so, your connection is complete. If not, continue to the next step.
4. Click Change API User.
5. Click through each of the "Warning" dialogs.
6. Enter the login credentials for the Marketing Cloud API user.
000384712

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.