What This Article Covers

Solution Launchpad is available through the Keap certified partner program. This article covers what is included and excluded when an email broadcast is installed from one app to another using Solution Launchpad, which dependencies are carried over automatically, and a known limitation that affects broadcasts containing an appointment block.

To learn how to become a certified partner and access Solution Launchpad, see how to become a Keap Certified Partner.

An email broadcast is an email sent to a list of recipients at a scheduled time. The schedule is the same for all recipients. Broadcasts are best used when you need to send the same message to everyone at the same time — for example, a monthly newsletter or a time-sensitive announcement.

What Is Included When Installing an Email Broadcast

When an email broadcast is installed from one app to another using Solution Launchpad, the following data is transferred to the destination app:

• Broadcast name and subject line
• Preview text
• Scheduled send date and time — Note: If the scheduled send date is in the past at the time of installation, the broadcast will default to Send right away when it is opened in the destination app.
• Email design, layout, and content

What Is Not Included When Installing an Email Broadcast

The following data is not transferred when an email broadcast is installed using Solution Launchpad:

• Custom sender — The sender name and email address used in the source app are not carried over. After installation, the sender defaults to the contact owner in the destination app.
• Audience configuration — The recipient list and audience filters configured in the source app are not transferred. The audience must be reconfigured in the destination app after installation.
• User-specific email signatures — Personalized email signatures from the source app are not transferred. After installation, the signature defaults to the contact owner's signature in the destination app.
• Unused uploads — Files or images that were uploaded to the source app but are not referenced anywhere in the email content are not transferred to the destination app.

Email Broadcast Dependencies

When an email broadcast references other items — such as images, custom fields, or tags — those dependent items are also installed into the destination app alongside the broadcast. The following dependency types are supported:

• Files and images referenced in the email content
• Contact custom fields used in merge tags within the email
• Tags referenced in the email broadcast configuration
• Items referenced via URL within the email content

Known Limitation: Appointment Block Not Supported

Email broadcasts that contain an appointment block cannot be installed using Solution Launchpad. If a broadcast in the source app includes an appointment block, the installation will fail. Remove the appointment block from the broadcast before attempting to install it through Solution Launchpad.