ESP Sync for Salesforce Marketing Cloud

With ESP Sync for Salesforce Marketing Cloud (SFMC), you can automatically sync your email code and assets from Litmus Builder to SFMC while you build. When it’s time to review your email with Proof, Previews & QA, or run a Spam Test, you can quickly select a draft email from SFMC to view in Litmus without ever switching tools.

NOTE: Litmus Salesforce Marketing Cloud integrations are available on Enterprise plans only.

Create an SFMC installed package

Note: For all ESP Sync functionality to work, your SFMC account must have the All Subscribers List setting enabled. This setting is disabled by default and can be enabled by submitting a request through SFMC support.

Log in to Salesforce Marketing Cloud, choose your name in the upper right corner of the screen, and select Setup from the Settings menu.

Salesforce Marketing Cloud settings dropdown menu

Find Installed Packages under Platform Tools > Apps in the left menu.

Salesforce Marketing Cloud setup menu with Installed Packages highlighted

Choose New, give the package a name and description and then Save.

New Package Details modal

Under Components, click Add Component, select API Integration, and then Next.

Add Component modal with API Integration selected as the component type

Select the integration type Server-to-Server and then Next.

Add Component modal with Server-to-Server selected as the integration type

In the permissions section select the following permissions, then choose Save:

  • Channels - Email: Read, Write, Send
  • Assets - Documents and Images: Read, Write
  • Assets - Saved Content: Read, Write
  • Contacts - List and Subscribers: Read, Write
  • Data - Data Extensions: Read, Write

Add Component modal with Server-to-Server properties selected

Why does Litmus need this information? In order to send emails on your behalf, we use the Marketing Cloud Transactional Messaging REST API that requires access to both contact addresses and data extensions in order to create a contact and send a test email to that contact. 

Once you choose Save, you will see the API Integration details for the Component you just created including Client ID, Client Secret, and Tenant subdomain. Keep this page open or copy these details somewhere safe so you can enter them in Litmus later to complete the sync setup.

The Tenant subdomain can be found between the "https://" and ".auth" portions of the Authentication Base URI. The Tenant subdomain should be a 28-character string starting in "mc" as shown below.

To find your Tenant instance (also referred to as server stack) you'll need to take a look at the URL in your browser’s address bar when you're logged into Salesforce Marketing Cloud.

Details tab of the created Installed Package with Client ID, Client Secret, and Tenant subdomain highlighted in green

Litmus requirements

Note: You will need Administrative rights on your SFMC account to create the setup. Account Holders, Admins, and Full users can complete the sync in Litmus.

You can now set up your connection to Salesforce Marketing Cloud from the Settings > Manage ESPs page in Litmus. You will need to enter your Tenant subdomain, Tenant instance, Client ID, and Client secret for the API component you created in the previous steps.

Sync with Salesforce Marketing Cloud enter your credentials modal

Select Authenticate & Add ESP to complete the setup.

Your Litmus account should now be connected and ready to sync with Salesforce Marketing Cloud.

Connecting multiple business units with Litmus

To differentiate between business units when selecting the account to pull the email in from, set a custom nickname for each instance on the Manage ESPs page. You can also create a subaccount in Litmus for each business unit and create the connection there. Connected ESPs are not shared across subaccounts.

You cannot create one API connection between Litmus and SFMC for use with all of your Salesforce business units. You can create an installed package for each individual business unit by setting up ESP Sync for SFMC within each of them using the instructions above.

Our troubleshooting page has answers to some frequent questions.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us