Loading
Salesforce now sends email only from verified domains. Read More
Market to Your Customers with Account Engagement
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            Considerations for Designing and Sending Emails

            You are here:

            1. Salesforce Help
            2. Docs
            3. Marketing Cloud Account Engagement

            Considerations for Designing and Sending Emails

            Review these considerations before using the enhanced email experience in Account Engagement.

            Required Editions

            Available in: any Account Engagement Edition with Salesforce Professional, Enterprise, Performance, and Unlimited Editions

            Browsers and Edition Availability

            • The enhanced email experience is available only in Account Engagement Lightning App.
            • You can preview email in sandboxes, but you can’t send test emails. To test the CMS image repository integration select the default CDN domain during channel setup.
            • Support for managing and sending email content is limited in Developer Editions. Access to Salesforce CMS images and the ability to send an email aren’t enabled.
            • Internet Explorer 11 and Microsoft Edge aren’t supported browsers for designing emails in this experience.

            Email Content and CMS Management

            • Users with the Manage Email Content user permission see all email content records. You can’t filter or hide email content records.
            • You can’t delete an email content record with related sends.
            • Email content records can’t be recovered after deletion.
            • If an email content record is deleted from an associated CMS workspace, you’ll be unable to edit the email if you try to open it from the Email Content tab in Account Engagement.
            • To upload a CMS image when designing emails, a user must be a contributor to the associated CMS workspace.
            • Developers can build custom Lightning Web Components to help bring third-party surveys, webinars, or other content into your emails.

            Building and Tracking Emails

            • You can edit the HTML Body field in the drag-and-drop editor only. The field isn’t editable on the email content record or via the API.
            • Pardot Merge Language (PML) variable tags aren’t supported. Use Handlebars Merge Language (HML) merge fields instead.
            • Account Engagement-only standard and custom fields are unavailable as HML merge fields. Use Salesforce standard and custom fields instead. Or, map your custom Account Engagement fields to Salesforce fields.
            • The following tools aren’t supported: folders, dynamic content, snippets, and A/B testing.
            • The domain associated with the CMS channel is only visible to customers in image URLs and email source code.

            Account Engagement Business Units

            • When an email is sent or activated for automation, the campaign, list, sender, and reply-to options are based on the user’s current business unit.
            • Your CMS channel is related to one domain and used for all sends. If you have multiple business units, the same domain and channel are always used.
            • Email content and templates ignore an asset’s business unit assignment when tracking engagement. For example, if you send Business Unit A’s form through an email connected to Business Unit B, we still attribute the form engagement to Business Unit A.

            Images

            • You can select images from a single Salesforce CMS channel only. Salesforce Files aren’t supported and don’t load when emails are sent.
            • Always use a publicly available, absolute URL for your links.
            • SVG images, JavaScript, and other active content aren’t supported in email content.

            Email Templates

            • To select an email template for use with email content, make sure that the template doesn’t contain Salesforce Files. Also, the related entity type must be Lead, Contact, or None.
            • Enhanced letterhead isn’t supported for email templates built in the Email Template Builder.
            • When you change the email template on the email content record, the Subject and HTML Body fields are overwritten with the template values. These two field values remain if you remove the template later, but don’t replace it.
            • We recommend that you avoid including Account Engagement-only merge fields, such as Email Preference Center, in an email template. When Sales or Service users select an email template to send to a lead or contact, the merge fields break.
            • You can’t create via API an email template that uses the enhanced sending experience.
            • Tags aren’t supported in the Email Template Builder.

            Allocations

            • The maximum character allowance for the HTML Body and Text Body fields is 384,000 characters.
            • You can send a test email to a maximum of 10 test lists of 100 recipients each. Or, you can send a test to up to 50 individual addresses.
            • If you exceed the character limit for an HTML component, try splitting the content into two HTML blocks.

            See Also

             
            Loading
            Salesforce Help | Article