What’s New in Litmus Builder: Webinar Recording + Q&A

[ 0 By

Building amazing email campaigns is challenging. From design and development to testing across email clients, there’s a lot to worry about. 49% of brands spend two weeks or more producing an email campaign, with most of that time going towards the development, review, and approval process, according to our 2018 State of Email Workflows report.

That’s why we created Litmus Builder, a code editor that allows email designers and developers to create better email, faster. With Builder, you can quickly build and test in the email clients that matter most to your audience, plus utilize a host of features that help to reduce errors, maintain brand consistency, and get your campaigns approved, into your email service provider (ESP), and out to your subscribers faster than ever before.

Litmus Builder is better than ever. We recently launched new additions to the Builder feature set, allowing you to fine-tune the editor to your liking, quickly create new projects, see additional information about your campaigns, and more.

In this webinar, Litmus host Kevin Mandeville walks through the new features and talks with guests Heidi Olsen (Senior Developer at eROI) and Pete Biolsi (Email Marketing Program Manager at King Arthur Flour) about how they use Litmus Builder in their own workflows. Along the way, they share insights for getting the most out of the Litmus Email Creative Platform and tips on how to send valuable emails that your subscribers will love.

Watch the recording above, see the featured email slides below, and read the follow up Q&A.

Webinar Q&A

There were a lot of great questions during the live webinar. While we tried to answer all of them, we’re posting them here on our blog as well. Have any other questions about Litmus Builder or how to use it in your own workflows? Please leave them in the comments below.

What is the difference between snippets and partials?

Although snippets and partials are similar—they both allow you to quickly add code to emails—they have a few key differences.

Snippets quickly generate code that can be customized on a per-email basis. Using a keyword, for example button, and hitting the tab button fills in code for common elements within an email. You can set up snippets within Litmus Builder for nearly anything, but most people use them for individual elements like images, buttons, and content sections. Snippets inject the code directly into the Builder document, where you can customize it as needed.

Partials, on the other hand, are global components that are dynamically compiled in the Builder document. Using keywords surrounded by double curly braces (e.g. {{header}}), Builder pulls in the code partial when the document is compiled rather than injecting the code directly into the document. Unlike snippets, you can’t directly edit the underlying code in partials in the email itself.

What are the best uses for snippets and partials? What type of content works best for each?

Taking into account how snippets and partials are pulled into a Builder document, a few good use cases present themselves.

Since you can directly edit the code once a snippet is triggered, they work well for elements within an email that will be customized on a per-email basis. Buttons are a perfect example. They are common elements across emails, but the call-to-action language, URL, and even color change between emails. Saving a button as a snippet lets you quickly inject that code and change what’s needed based on the goals of your campaign.

Snippets are also great for:

  • Adding images
  • Copy elements like headings and paragraphs
  • Content blocks like articles, event invites, or product features

As partials are global and dynamically added to Builder documents, they work well for components that don’t change between email campaigns. Headers, footers, and unsubscribe information are excellent candidates for partials. When these components change, those changes populate across every email using that partial within Builder. Instead of having to manually update dozens of emails when your logo changes, partials allow you to update once, leaving you more time to focus on other, more important aspects of your campaigns.

For more information on the difference between and use cases for snippets and partials, check out these articles on the Litmus blog:

Is it possible to create and manage snippets or partials that can be used or not edited by others in an organization?

Since snippets expand code directly into a Builder document, that code can immediately be changed by anyone working in the project.

Partials, on the other hand, are global and dynamically pulled into a document. The code is not expanded into the code editor, so people working in that document won’t be able to immediately update partials. Users can still navigate to both the snippets and partials libraries using Builder’s navigation and make changes, but the dynamic nature of partials helps keep them consistent across different email campaigns. Combined with internal policies or guidelines around who can update what in Builder, snippets and partials allow teams to quickly and safely build brand-consistent emails.

How can you manage version control in Litmus Builder? How can I use Builder as a system of record for changes?

By default, Litmus Builder tracks all changes saved to a document. Every time you hit save, a log is made of any changes made from the last save event. You can view all of the changes in a document by clicking the Timeline option in the navigation bar within Builder. This opens the Timeline showing all of the previous versions of an email, including who saved the document and at what time.

Version control with Builder’s Timeline.

You can quickly preview older versions and revert to a previous version by clicking the Restore link associated with that version.

Should I be inlining my CSS?

That’s a complicated question, one without a single answer. Ever since Gmail made updates allowing for embedded CSS, email developers have been debating the merits of inline and embedded CSS. It’s something we even tackled on The Email Design Podcast.

As with most things in email marketing, it depends. If you know your subscribers are opening your email in a client that supports embedded CSS, you can probably stop inlining. But, if there’s any uncertainty about which email clients your subscribers use, you may want to keep inlining CSS for maximum compatibility. If you’re not sure, Litmus Email Analytics will give you the insights you need to tailor your development process to your audience.

If you want to dig deeper into the debate, read our post that attempts to answer the perennial question, “Do email marketers and designers still need to inline CSS?”

Create better emails, faster

Access all of the latest features in Litmus Builder by starting a free Litmus trial today. Quickly develop emails using snippets and partials, test in the latest email clients, and create campaigns your subscribers will love.

Try Builder now →