You need the region or numeric value of the server stack where your Marketing Cloud Engagement tenant resides in some instances. For example, this information helps you learn the current health of the stack, know where customer data is stored, configure a Web Collect URL, or obtain the URL endpoint for use with Web Services API.
This article is applicable to the services branded as Marketing Cloud Engagement (formerly ExactTarget) and Intelligence Reports for Engagement. For more information on security, privacy, and architecture for these and other services, please see the Trust and Compliance Documentation.
Follow these steps to help you find the details for your instance.
This page shows the instance where your account is located, along with a status bar for the current health of the stack of servers. Once you have this information, you can also sign up for health notifications to made aware any time that there is a known issue occurring on your stack of servers.
After you log into the Marketing Cloud Engagement application, your URL shows like these examples as such, depending on your instance:
Note: Most of these URLs include S followed by the numeric value of the stack. The S1 instance 1 is an exception, as it does not include an S or number within the link.
This table includes all current instances mapped to their respective Marketing Cloud Customer Region.
|
Stack |
Customer Region |
|
1 - 13 |
AMER |
|
50-51 |
EMEA |
| 401 | AWS India (Mumbai) Region |
| 402 | AWS Sydney Region |
| 403 | AWS Tokyo Region |
| 406 | AWS Canada Region |
For more information regarding a tenant’s Customer Region and data storage, review Marketing Cloud Trust and Compliance. Country specific details can also be found on the Trust and Compliance site under the "Salesforce Infrastructure & Sub-processors Documentation" section.
Engagement on Hyperforce does not currently support Customer migrations.
000383566

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.