Salesforce Marketing cloud integration with PromoMats

What is it? Automatically export to Salesforce Marketing Cloud (SFMC) your approved email’s execution files (HTML package) with one click from PromoMats. In approximately 15 seconds, steps such as: the HTML upload, the images upload and their link paths replacements are completed for you.

Having issues?
Click here to scroll down directly to our Troubleshooting Checklist

Core benefits

More efficiency:

Creating a SFMC Email step by step: from PromoMats to SFMC integration

1,2,3. Optional: Copy, Author and Sync changes of the Email in PromoMats with Assembler

These three steps are optional, in order to author SFMC emails using PromoMats and Assembler. This integration will work authoring the email with any HTML editor or your preference, just take a look to the pre-requisites below.

This list is an overview of the Assembler workflow, If you are interested in knowing more about how to take advantage of Assembler, read this article

4. Start the Approval process in PromoMats

Start the Medical Legal Review process

5. “Send to SFMC” Auto-Upload integration from PromoMats to SFMC

Keep in mind for this “Send to SFMC” integration button to work, your material has to follow three Pre-Requisites (learn more details below):

It consists of an automatic upload of the HTML and the images of the email, rewriting as well the image link-paths. This automation will save the digital publisher’s time and will make the email ready to be tested and sent to customers in SFMC. This is done when saving your project as “Ready for review”.

Once your Material is approved, click on “Send to SFMC” option to start this action, selecting the three dots menu.

Be sure you have followed the 3 pre-requisites for the “Send to SFMC” option to be available, check them below.

PRE-REQUISITES:

The ‘Send to SFMC’ option is available for Material documents only and appears in the Actions Menu when:

A. Document is in any of these states:

B. And both fields of the metadata below have the indicated values selected:

C.The HTML zip package should be uploaded as a Component that is linked to the material. We recommend you perform this action between “Approved for Production” and “Approved for Distribution” status of the material:

*NOTE: The Production Package can be created by any authoring tool. However, for the integration to work, it must comply with the following:

  1. It should be a ZIP archive containing the email HTML file and required image files
  2. Images should be in one of the SFMC supported formats
  3. Images and HTML should not be too large per SFMC requirements

6. Relate content blocks and include click metrics on SFMC

Once the email is built, the team can add the content blocks using the custom tag and click rates on the HTML area inside the SFMC tool and keep taking advantages the same way of the great customized journey mappings that SFMC allows.

7. Test and Send

Assembler emails advantage: the auto-generated HTML code offers a high quality, offering the same result in most common Email clients and technical adjustments are not needed when tested.

Job owner can review the functional Email tests and “Approve For Distribution” in PromoMats.

Finally the planned dates for sending can be activated for HCP deployment.

When sending the email material to SFMC, you will see that all the images and the HTML file travelled from PromoMats to the Content Builder on Salesforce Marketing Cloud. When testing the email, make sure that you’ve added the Profile center snippet and the Physical mailing address to the HTML so that it works when you send it:

Send to SFMC” Troubleshooting Checklist

If you do not see the “Send to SFMC” option in the action menu, check the following:

If you did not receive an email from SendToSFMC.com, check the following:

If you receive an error related to the package format, check the following:

If you cannot find your job on SFMC, check the following:

If images are not displayed when you preview your email in SFMC, check the following:

If you cannot resolve the issue, please open a ticket here