When experiencing issues with Marketing Cloud Connect, such as tracking-related, expired Marketing Cloud API token, sending performance, etc., enabling Tenant-Specific OAuth Endpoints is recommended to assist in resolving this and making the MCC connection improved and more stable.
Note: If you are a Hyperforce customer, Tenant-Specific OAuth Endpoints for Marketing Cloud Connect is mandatory if your organization utilizes Marketing Cloud Engagement. If your organization utilizes Marketing Cloud Account Engagement (formerly Pardot) these steps are not required. If your Org is about to be migrated to Hyperforce, you must follow the instructions below before the Org Migration, to avoid unintended disruption to the MCC connection. For more information, please refer to the Retain uninterrupted access to Salesforce services on Hyperforce article.
To properly enable Tenant-Specific OAuth Endpoints, please see the resolution below:
*Enabling Tenant-Specific OAuth Endpoints will clear your configuration. Prior to enabling Tenant-Specific OAuth Endpoints, we recommend taking a screenshot of the Marketing Cloud Configuration Settings page, so that you can reference this when setting your configuration settings up again*
1. Log in to your Salesforce CRM instance.
2. Navigate to the Marketing Cloud tab.
3. Click “Configure Marketing Cloud Connector”.
4. Scroll to the bottom of the page to the "Advanced" section and click the small arrow to expand.
5. Toggle “Tenant-Specific OAuth Endpoints” on to enable.
6. This will clear the configuration. You might be prompted to verify a new Remote Site Setting. If you are prompted to do so, please verify.
7. Next, you'll be prompted to reset the Marketing Cloud Configuration. Click the “Automatic Setup Wizard” and go through the steps to complete the new configuration.
8. Reconnect the Marketing Cloud API User by clicking “Connect to Marketing Cloud”.
9. You'll be redirected to the Marketing Cloud Connector Settings page where you'll re-setup based on the screenshot of your previous settings.
For more information on the Tenant-Specific OAuth Endpoints feature, please see the Tenant-Specific OAuth Endpoints with JSON Web Token Authentication section of the October 2019 Release Notes.
000390168

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.