Salesforce Email Studio OAuth2 (ExactTarget) Connector Setup Guide
This article describes how to set up the Salesforce Email Studio OAuth2 connector.
Prerequisites
- Salesforce Marketing Cloud Account
- Salesforce Marketing Cloud App Client Credentials
- Appropriate permissions set on the Salesforce Marketing Cloud App
Connect Using the OAuth2 Authentication Scheme
Use the following steps to connect Tealium to ExactTarget using OAuth2 authentication scheme:
- Log into your ExactTarget account and from the top right menu, select Setup.
- Navigate to Platform Tools > Apps > Installed Packages.
- At the top right of the Installed Packages panel, click New to create a new package.
- In the opened dialog box, name your package and click Save.
- In the newly created package, click Add Component.
- Select API Integration as the component type and Server-to-Server as the integration type.
- Set appropriate Server-to-Server properties.
If correct permissions are not provided, the integration may fail. Changing permissions after the package has been created may require some wait time for the permissions to apply. - Save your component.
In the package window, the component named API Integration displays the authentication information. - Copy the following values to use later in the connector configuration:
- Client ID
- Client Secret
- SOAP Base URI
- Also copy your account’s MID value, found in the top menu bar.
Connector Actions
Action Name | AudienceStream | EventStream |
---|---|---|
Send Email to User | ✓ | ✓ |
Add to Email List | ✓ | ✓ |
Remove from Email List | ✓ | ✓ |
Upsert Subscriber and Add to Email List(s) | ✓ | ✓ |
Data Extension - Add Record | ✓ | ✓ |
Data Extension - Add Multiple Records | ✓ | ✓ |
Data Extension - Delete Record | ✓ | ✓ |
Data Extension - Update Record | ✓ | ✓ |
Data Extension - Upsert Record | ✓ | ✓ |
Configure Settings
Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector.
After adding the connector, configure the following settings:
This connector requires the following information to connect to ExactTarget’s SOAP protocol, upgraded with OAuth2 authentication scheme.
-
Market Cloud App Client ID
- Required.
- Provide your app client ID.
- See: Get OAuth Client Credentials
-
Client Secret:
- Required.
- Provide your app client secret.
-
Account ID
- Required.
- Provide account identifier (MID) of the target business unit.
-
Tenant-specific subdomain
- Required:
- Provide tenant-specific subdomain for your application.
- If your SOAP Base URL looks something like this:
https://mctg-xxxxxx.soap.marketingcloudapis.com/
, then provide the portion of this URL between two slashes and the first period, in this example it would bemctg-xxxxxx
. - The connector will automatically augment this subdomain name with correct suffixes for authentication and for SOAP messaging.
-
ExactTarget Account ID (MID)
Action Settings - Parameters and Options
Click Next or go to the Actions tab. This is where you configure connector actions.
See Salesforce Marketing Cloud Email Studio for details about actions setup.
This section describes how to set up parameters and options for each action.
Action - Send Email to User
Parameters
Parameter | Description |
---|---|
Business Unit |
|
Triggered Send Email Interaction |
|
Subscriber Lookup By Key |
|
Disable Subscriber Lookup |
|
Subscriber Email |
|
Attributes to Add or Overwrite |
|
Don’t Send Email to Subscriber with Status |
|
Enable Asynchronous Processing |
|
Action - Add to Email List
Parameters
Parameter | Description |
---|---|
Business Unit |
|
Email List |
|
Subscriber Lookup By Key |
|
Enable Asynchronous Processing |
|
Action - Remove from Email List
Parameters
Parameter | Description |
---|---|
Business Unit |
|
Email List |
|
Subscriber Lookup By Key |
|
Enable Asynchronous Processing |
|
Action - Upsert Subscriber and Add to Email List(s)
Parameters
Parameter | Description |
---|---|
Business Unit |
|
Subscriber Key |
|
Subscriber Email Address |
|
Add Subscriber to Email List(s) |
|
User Status |
|
Enable Asynchronous Processing |
|
Action - Data Extension - Add Record
Batch Limits
This action uses batched requests to support high-volume data transfers to the vendor. For more information, see Batched Actions. Requests are queued until one of the following thresholds is met or the profile is published:
- Max number of requests: 1000
- Max time since oldest request: 10 minutes
- Max size of requests: 1 MB
Parameters
Parameter | Description |
---|---|
Business Unit |
|
Data Extension |
|
Record Fields |
|
Enable Asynchronous Processing |
|
Action - Data Extension - Add Multiple Records
Batch Limits
This action uses batched requests to support high-volume data transfers to the vendor. For more information, see Batched Actions. Requests are queued until one of the following thresholds is met or the profile is published:
- Max number of requests: 1000
- Max time since oldest request: 10 minutes
- Max size of requests: 1 MB
Parameters
Parameter | Description |
---|---|
Business Unit |
|
Data Extension |
|
Record Fields |
|
Enable Asynchronous Processing |
|
Action - Data Extension - Delete Record
Batch Limits
This action uses batched requests to support high-volume data transfers to the vendor. For more information, see Batched Actions. Requests are queued until one of the following thresholds is met or the profile is published:
- Max number of requests: 1000
- Max time since oldest request: 10 minutes
- Max size of requests: 1 MB
Parameters
Parameter | Description |
---|---|
Business Unit |
|
Data Extension |
|
Record Lookup |
|
Enable Asynchronous Processing |
|
Action - Data Extension - Update Record
Batch Limits
This action uses batched requests to support high-volume data transfers to the vendor. For more information, see Batched Actions. Requests are queued until one of the following thresholds is met or the profile is published:
- Max number of requests: 1000
- Max time since oldest request: 10 minutes
- Max size of requests: 1 MB
Parameters
Parameter | Description |
---|---|
Business Unit |
|
Data Extension |
|
Record Lookup |
|
Enable Asynchronous Processing |
|
Action - Data Extension - Upsert Record
Batch Limits
This action uses batched requests to support high-volume data transfers to the vendor. For more information, see Batched Actions. Requests are queued until one of the following thresholds is met or the profile is published:
- Max number of requests: 1000
- Max time since oldest request: 10 minutes
- Max size of requests: 1 MB
Parameters
Parameter | Description |
---|---|
Business Unit |
|
Data Extension |
|
Record Lookup |
|
Enable Asynchronous Processing |
|
Vendor Documentation
This page was last updated: November 25, 2024