App Connect supports
connecting to Salesforce Marketing Cloud via a Marketing Cloud
package. You can create different types of Marketing Cloud packages however App Connect supports
installed packages with server-to-server or web app API integrations only. In the App Connect connection panel you will be prompted to select one of the
following packages:Figure 1. Selecting an application type in App
Connect
A description of the application types:
Salesforce Marketing Cloud - Legacy package
An installed package with legacy functionality most likely created before 1 August 2019. For
more information, see Installed Package Types.
Salesforce Marketing Cloud - Enhanced package
An installed package with enhanced functionality. For more information, see Installed Package Types.
If you select the Salesforce Marketing Cloud - Enhanced package you can choose one
of the following authorizations methods:
Provide client credentials (OAUTH 2.0 CREDENTIALS)
This option is most suitable for server to server installed packages. If you select this option,
you need to provide the tenant subdomain, client ID, and client secret.
Use the application's website to sign in (OAUTH 2.0 AUTH CODE)
This option is most suitable for web app installed packages. If you select this option, as well
as providing the tent subdomain, client ID, and client secret, you need to add the redirect URI
provided by App Connect to your installed package.
Provide client credentials to use (BASIC OAUTH )
This option is most suitable for web app installed packages. If you select this option, you need
to provide the tenant subdomain, client ID, client secret, access token and refresh token.
Connecting to Salesforce Marketing Cloud
To connect App Connect to a Salesforce Marketing Cloud account, you need to provide the following
connection details.
Table 1. Salesforce Marketing Cloud credentials
Field
Description
Tenant subdomain
The subdomain of your tenant in the Salesforce Marketing Cloud instance. The subdomain is a
28-character string that starts with the letters ‘mc’. For example, ‘mc563885gzs27c5t9-63k636ttgm’,
which is part of your endpoint API URL,
https//mc563885gzs27c5t9-63k636ttgm.rest.marketingcloudapis.com.
Client ID
The unique client identifier for the Salesforce Marketing Cloud installed package.
Client secret
The client secret for the Salesforce Marketing Cloud
installed package.
Access token
Note: This field is required for BASIC OAUTH authorization method only.
Specify the
access token that is generated from the application client ID and client secret.
Refresh token
Note: This field is required for BASIC OAUTH authorization method only.
Specify the
refresh token that is generated from the application client ID and client secret.
The authorized redirect URI for your Salesforce Marketing Cloud application
Note: This field is required for OAUTH 2.0 AUTH CODE authorization methods only.
Use
the value in this field when you create the web app installed package that generates the client ID
and secret used above. If you already have an application, you can add the URI by editing the
package.
To create the values you need to connect to Salesforce Marketing Cloud, complete the following steps:
Note:
These instructions assume that you are creating an installed package in Salesforce Marketing Cloud for the first time.
To complete these steps, you must have the Administration | Installed Packages | Administer
permission. Or you must have the role of Administrator or Marketing Cloud Administrator. For more
information about how to assign permissions and roles, see Assign a Role and Permissions to a Marketing Cloud User from the
Users Screen.
From your Salesforce Marketing Cloud instance,
open your user icon menu and click
Setup > Apps > Installed
Packages.
In the New Package Details window, enter a name for your package and click
Save. The Package details tab is displayed.
Click Add Component.
Select API Integration and then click Next.
Select Server-to-Server or Web App and then click
Next.
If you selected Web App, in the URIs field, add
the redirect URI provided by App Connect.
Figure 3. Adding the redirect URI provided by App Connect
Select the scopes as required by your business needs. For the minimum scopes
required by App Connect, see Table 2.
Click Save.
In the Components section of the resulting page, the Client ID, Client secret and
Tenant ID are displayed as illustrated in the following screen capture.
Figure 4. Salesforce Marketing Cloud web app installed package
General considerations for using Salesforce Marketing Cloud in App Connect
(General consideration) You can see lists of the trigger events and
actions that are available on the Applications and APIs page of the App Connect Designer.
For some applications, the events and actions depend on the
environment and whether the connector supports configurable events and dynamic discovery of actions.
If the application supports configurable events, you see a Show more configurable
events link under the events list. If the application supports dynamic discovery of
actions, you see a Show more link under the actions list.
(General consideration) If you are using multiple accounts for an
application, the set of fields that is displayed when you select an action for that application can
vary for different accounts. In the flow editor, some applications always provide a curated set of
static fields for an action. Other applications use dynamic discovery to retrieve the set of fields
that are configured on the instance that you are connected to. For example, if you have two accounts
for two instances of an application, the first account might use settings that are ready for
immediate use. However, the second account might be configured with extra custom fields.
The following table specifies the minimum scopes required for installed
packages. Failing to select the minimum scopes will result in an error with status code 403
- No permissions to perform the specified action.
