You are here:
Salesforce Marketing Cloud Legacy API Connector
This connector provides data about email marketing campaigns.
- Channel: Email
- Data Stream Type: Email Marketing
Prerequisites
Valid username and password with API permissions
Known Issues
Not all metrics available in the UI are pulled by the connector.
Authentication
- Go to Marketing Cloud > Administration.
- Under Account, select Installed Packages and click New.
- In the New Package Details screen, enter a Name and Description.
- Make sure the Create with enhanced functionality checkbox is NOT selected.
- Click Save.
- Receive the Client Id and Client Secret.
- More details can be found here.
For Marketing Cloud Intelligence Data Pipelines you need:
- Client ID
- Client Secret
- Instance ID
If you’re not sure what the Instance ID is, you can find it within the URL string when logging into Marketing Cloud: it is the S(#) value in the URL.
Setup
When setting up the Data Stream there are 3 dropdowns that you need to consider under the ‘General’ tab. The ‘Credentials’ is where you would select the username on the Marketing Cloud platform. Each Workspace can have more than one username for which data is pulled. The dropdown is therefore populated with all the usernames that have been authenticated. Each username can be associated with more than one Account on Marketing Cloud and the dropdown will display all the Accounts associated with the respective username. The Business Unit selection is optional, it populates with all the Business Units associated with this Account.
This connector pulls LIFETIME measurements and every processing action pulls data for all existing Campaigns. This means that there’s no ‘Initial Data Fetch’ configuration in the Data Stream settings, as in other API connectors. Every time the Data Stream is processed, whether at creation or otherwise, it pulls all Campaigns data regardless of how far back such data exists historically. This means that configuring dates for Initial Data Fetch or for routine processing is irrelevant.
The Platform assigns the Processing Date as the Data Date for the retrieved data, since the LIFETIME values of the Measurements pulled (in every such instance) are true to that particular date.
To keep data for Failed Days at Date level, Failed Days must be reprocessed on the day that they failed. Reprocessing data on any other day would assign the new Processing Date to the reprocessed data. Similarly, if you delete data for dates prior to the current day, reprocessing assigns the Reprocessing Date to that date, overriding whatever dates it had before.
To avoid confusion, here’s a list of the Source Measurements and the Intelligence Data Pipelines Measurements to which they’re mapped:
| SOURCE | MAPPING |
|---|---|
| Sends | Emails Sent |
| Implicit Deliveries | Emails Delivered |
| Soft Bounces | Email Soft Bounces |
| Hard Bounces | Email Hard Bounces |
| Unique Opens | Email Opened |
| Unique Clicks | Email Clicked |
| Unique Unsubscribes | Email Unsubscribes |
| Forwarded Emails | Email Marketing Custom Metric 01 |
| Number Errored | Email Marketing Custom Metric 02 |
| Number Targeted | Email Marketing Custom Metric 03 |
| Other Bounces | Email Marketing Custom Metric 04 |
QA Your Data
- Create a report in the Marketing Cloud UI Analytics section.
- Filter for a certain campaign or campaigns.
- Reprocess the Data Stream in Marketing Cloud Intelligence Data Pipelines (to make sure you’re viewing the latest data).
- Create a Pivot Table/Report with the same filtering applied and compare the numbers.

