Salesforce Email Studio (formerly ExactTarget) Connector Setup Guide for AudienceStream (Legacy)
This article describes how to trigger your Salesforce Email Studio (formerly ExactTarget) email campaigns and manage subscribers in your ExactTarget Marketing Cloud lists and data extensions.
This is the legacy version of this connector, the new version can be found at Salesforce Email Studio OAuth2.
Prerequisites
The following items are required to configure the Salesforce Email Studio (ExactTarget) connector:
-
Username
- Enter your ExactTarget Marketing Cloud username.
- For additional information, see the following ExactTarget Developer documentation: Get Started with the SOAP Web Services API.
-
Password
- Your ExactTarget Marketing Cloud password.
-
Server Host Name
- Required.
- Enter your ExactTarget Marketing Cloud server host name.
- If you do not know the server host name, contact your ExactTarget Marketing Cloud representative.
- When entering server host, do not include protocol and path. For example, enter only
webservice.exacttarget.com
.
-
IP Whitelisting
- Optional.
- If your ExactTarget Marketing Cloud has whitelisting enabled, configure the system to whitelist the IP addresses.
- This is usually the default setting.
Connector Configuration Requirements
The ExactTarget Marketing Cloud API has 2 Web Service communication protocols, Simple Object Access Protocol (SOAP) and Representational State Transfer (REST). The Tealium Salesforce Email Studio (ExactTarget) connector uses SOAP. SOAP calls can be authenticated using an access token or a username and password. The Tealium connector authenticates using the username and password method.
For additional information, see Authenticate with Username Token in Get Started with the SOAP Web Services API.
You will need the following authentication information to configure connectors:
- The username and password used to access your ExactTarget Marketing Cloud account
- The server host name, such as
http://webservice.s10.exacttarget.com/
Supported Actions
Action Name | Action | Trigger on Audiences | Trigger on Events |
---|---|---|---|
Send Email to User | Triggers an email to subscribers | ✓ | ✗ |
Add to Email List | Adds subscribers to an email list | ✓ | ✗ |
Remove from Email List | Removes unsubscribers from an email list | ✓ | ✗ |
Upsert Subscriber and Add to Email List(s) | Adds subscribers to an email list and sends their data to existing profile attributes | ✓ | ✗ |
Data Extension - Add Record | Inserts new records in a data extension | ✓ | ✗ |
Data Extension - Add Multiple Records | Inserts multiple records in a data extension | ✓ | ✗ |
Data Extension - Delete Record | Deletes existing records from a data extension | ✓ | ✗ |
Data Extension - Update Record | Updates existing records in a data extension | ✓ | ✗ |
Data Extension - Upsert Record | Updates existing record and inserts new records in a data extension | ✓ | ✗ |
Configure Settings
Go to the Connector Marketplace and add a new Salesforce Email Studio (ExactTarget) connector. For general instructions about how to add a connector, see Connector Overview.
To configure your vendor,
- In the Configure tab, enter a descriptive title.
- Enter the username, password, and host name for your ExactTarget Marketing Cloud account.
Do not include http
or https
protocol in the host name.
- (Optional) Provide descriptive notes regarding the Salesforce Email Studio (ExactTarget) connector configuration.
Action Settings: Parameters and Options
Click Next or go to the *Actions tab. From here, you will set up actions and trigger each action.
Action: Send Email to User
This section describes specific parameters and available options for the Send Email to User action.
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 | Select one or more subscriber statuses that you want to exclude from your email list, as shown in the following list:
|
Async Processing |
|
Action: Add to Email List
This section describes specific parameters and available options for the Add to Email List action.
Parameter | Description |
---|---|
Business Unit |
|
Email List |
|
Subscriber Lookup by Key |
|
Async Processing |
|
Action: Remove from Email List
This section describes specific parameters and available options for Remove from Email List action.
Parameter | Description |
---|---|
Business Unit |
|
Email List |
|
Subscriber Lookup by Key |
|
Async Processing |
|
Action: Upsert Subscriber and Add to Email List(s)
This section describes specific parameters and available options for Upsert Subscriber and Add to Email List actions.
Parameter | Description |
---|---|
Business Unit |
|
Subscriber Lookup |
|
Subscriber Attributes Data |
|
Add Subscriber to Email List(s) |
|
User Status |
|
Async Processing |
|
Action: Data Extension - Add Record
This section describes specific parameters and available options for Data Extension - Add Record action.
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
Parameter | Description |
---|---|
Business Unit |
|
Data Extension |
|
Record Fields |
|
Async Processing |
|
Action: Data Extension - Add Multiple Records
This section describes specific parameters and available options for Data Extension - Add Multiple Records action.
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
Parameter | Description |
---|---|
Business Unit |
|
Data Extension |
|
Record Fields |
|
Async Processing |
|
Action: Data Extension - Delete Record
This section describes specific parameters and available options for Data Extension - Delete Record action.
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
Parameter | Description |
---|---|
Business Unit |
|
Data Extension |
|
Record Lookup |
|
Async Processing |
|
Action: Data Extension - Update Record
This section describes specific parameters and available options for Data Extension - Update Record action. This Action only updates existing records, it does not insert new 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
Parameter | Description |
---|---|
Business Unit |
|
Data Extension |
|
Data Extension |
|
Record Lookup |
|
Async Processing |
|
Action: Data Extension - Upsert Record
This section describes specific parameters and available options for Data Extension - Upsert Record action. With this Action, you can update existing records and insert new 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
Parameter | Description |
---|---|
Business Unit |
|
Data Extension |
|
Record Lookup |
|
Add Record |
|
Update Record |
|
Async Processing |
|
Vendor Documentation
For additional information, see the following vendor documentation:
This page was last updated: June 22, 2022