Litmus

We used Litmus as an inbox monitor tool and for analytics. We had a constant challenge on the length of the email which engagement analytics helped with. Providing clear stats to stakeholders on reading time helped us to improve overall engagement. Great tool and very easy to set up. Inbox rendering was also helpful to address any changes to ESPs rendering engines without a need to test everything manually.

We have not. We have one designer that tests the emails and is responsible for renderability.

End-to-end testing for all email campaigns. This allow us to focus on the 97% of email clients used by our members.

We use it most of the time with different stakeholders including copy, design and developers.

My team handles outbound communication, and emails are a large part of that. We have an in-house tool that creates and sends emails, and we use Litmus to view the emails in a variety of email clients. We need a quick and dependable view into how the emails we have created will look on email clients that no one on our team has access to.

We have not used these features. We typically do most of our work in our in-house tools, and just use Litmus as final Quality Assurance on how the email looks in other email clients.

I use Litmus to review email design and ensure that emails render correctly in a user's inbox, regardless of the email client they use.

Litmus has allowed us to have multiple teams collaborate and comment / approve an email design before launch. It is easy for us to look at an email and flag if updates need to be made to the code for a specific design based on the email client.

Our agency uses Litmus to test previews for all email marketing communications. It is our primary tool for reviewing how our emails look on the most common browsers. We also use tracking codes to collect device and browser data on opened emails.

We have not used the Proof functionality.

I primarily use Litmus previews to QA/QC our email development for dozens of agency clients. Without this tool, it would be very difficult to quickly see how our emails look across all the most populated devices and email clients. I also use Litmus tracking to gather data that email platforms do not collect. Lately, one of those unique pieces of data has been the Apple-privacy impacted opens.

We do not use Litmus Proof because we post proofer feedback to an internal project management system. We will reconsider working Proof into our system because of how great other Litmus features are.

We send out thousands of emails a year to our membership. We primarily use Litmus to gauge our reader's interest in our emails. We have great interest in the open and read rates. We also determine what topics are of interest to our membership. It is a great tool in allowing us to know if we are hitting the mark in our marketing and general interest topics. It also allows us to test our emails to make sure they will appear properly on different devices and different browsers.

Although we do not use this feature as much as we should, when we have, it has saved us time and effort. It has allowed us to comment directly on the proof about changes on important messages. This showed designers/editors exactly what needed clarification. The link tracking showed what worked and what didn't. Finally, the approval process allowed it to get reviewed and approved along with the different steps so that nothing was sent out without the appropriate eyes looking it over first.

We primarily use Litmus for the testing component for our email, seeing previews and reviewing the QA components. Being able to see how our emails look from different clients and on mobile and desktop is incredibly helpful for us to optimize our emails.

One key business problem that the product addresses is being able to see the spam testing, loading speed, and accessibility for clients. Having intel from the get-go on problem areas to help us ensure a higher inbox placement rate is key and has been so helpful for us.

My team members will often use Litmus to review emails, but I am the owner of our email program, so I primarily am the one utilizing the tool. My manager and teammates use the system to review the emails at times. We haven't used the task list features or commenting features but look to doing that in the future.

We use Litmus daily with our email marketing program. Once our developers build and code out our email sends, we use Litmus to preview our send across various email clients, apps, and devices to ensure the email appears cohesive across all platforms. This ensures our emails are always on-brand, error-free, and always looking great.

Our team has used Litmus to streamline the email approval workflow and reduce review cycle time—there is much less back-and-forth. Emails are approved faster, have fewer errors, and our rounds of feedback have dramatically decreased.

We primarily used Litmus to test the rendering in different email clients. It's very easy to use Litmus in this aspect, as we could fairly quickly view the rendering across multiple clients. We did not really use any of the other features.

Didn't use it.

At Scripps, we have internal customers who provide overall goals, copy, and assets to support various carelines. Our team uses the Previews and Q&A section to ensure our links are working properly and identify any issues prior to sending for proofing. We use the proofing in Litmus as an email approval platform for our internal customers. Finally, for large sends, we also use the Analyze feature to add tracking code to our campaigns when we feel we need deeper analytics than our email platform can provide. Additionally, the level of service, blogs, and help articles are so helpful for our small team. I lean on Litmus for best practices and tips.

Litmus proof is a crucial part of our email review and approval process. All of our internal stakeholders and customers are trained on how to use Litmus proof and we will not launch an email without going through this process.

This is the second organization that I have used Litmus for, and I'm a strong believer in its benefits. At my current company, we use Litmus to test emails in various browsers before sending. In my previous role, we also used the collaborative review function that allowed all team members to provide input on an email proof in one place.

In my previous role, my team used the Litmus Proof function to collaboratively review and edit emails before sending. This saved a vast amount of time, effort, and confusion by avoiding manually sharing various versions of the email. Unfortunately, this function is only available in more expensive versions of Litmus, so the startup I am currently working with has a limited marketing budget, and doesn't have the ability to use Litmus Proof.

We utilize Litmus to confirm the appearance of e-mails in various e-mail clients. Litmus is beneficial in ensuring that the e-mails we've built and developed are populating without visual errors on desktop and mobile platforms. The Litmus previews allow for a simple and efficient yet thorough QA of the e-mails.

We primarily utilize the Shared Link function to allow for easy testing and review. This feature has helped share Litmus previews and contributes to a simple review process.

We test our marketing emails in Litmus to see how they render in multiple desktops, mobile, and web-based email clients. Additionally, we look at feedback from Litmus regarding our subject lines, accessibility, link integrity, loading speed, and spam testing.

We have not used this feature.

Litmus is used in the Office of Admissions for developing and testing all email communications with prospective and admitted students. We have approximately 350+ distinct marketing emails and numerous other transactional ones for various events, and they need to be well designed and function correctly in multiple email clients. Litmus ensures that our emails are bulletproof and will be delivered as coded. Litmus has significantly cut down on the amount of time it takes to build an email with snippets and partials, as well as the CSS inlining capabilities. Large email newsletters that previously would take 2 hours to build, can take as little as 30 minutes, and our average build time is only 10 minutes.

We don't use Proof, because we don't have that level of Litmus.

We use Litmus before sending any emails, to any clients. Once our emails are designed and coded, we run them through Litmus to get a comprehensive, guided checklist of the critical elements that affect email performance and delivery. Litmus provides a 360-degree view of our email will appear across 100+ different email clients, allowing us to spot flawed formatting at a glance. It even lets us test in Dark Mode to ensure everything looks good.

We do not currently use this functionality.

Litmus is an essential component of our email marketing process. The whole marketing team uses it to test their emails before sending, and a good number of them also use the "Proof" function to collaborate on email development. We have found that built-in Analytics provides a different view to that of our ESP, and in particular, has helped us tackle the recently Apple Mail Privacy changes by identifying Apple Mail users. We also use the Builder for one of our newsletters, and I would have no hesitation in implementing a Litmus Builder-based master template for general email creation if we weren't already using our ESP's built-in email builder and templates to great success. In addition, an often overlooked bonus resource is the Litmus Community and their newsletters/blogs which are really good for sharing new ideas and clever tricks, as well as getting to the bottom of really niggly irritating problems with finicky email HTML.

Litmus Proof has been beneficial to teams working collaboratively on larger campaigns, as well as providing feedback to users, particularly those who are newer to the team. The core functionality is to be able to share a visual of the email with others, who can then add comments by adding a bubble in the place that their comment relates to, visually. Those comments can then be replied to as a distinctly separate thread, and marked as resolved (which hides them, though they can be viewed in a separate area if needed). It then has approvals, though there is no built-in workflow integration which would be a really interesting and useful future enhancement.

We primarily use Litmus for quality assurance purposes with our marketing emails. Beyond that, it allows us to be innovative. Litmus builder helps us develop custom-coded modules when we want to test out animated, interactive, dynamic, and personalized elements. The education and networking that Litmus facilitates within the email marketing community with webinars, forums, and annual Litmus Live events is where we see real value.

Litmus proof allowed my team to QA over 200 nurture emails in the span of a week. All the comments were in one area. It was a very streamlined process to edit, QA, and approve all from the same platform.

Litmus has become a staple for our organization when it comes to ensuring that our emails look their best for each and every send. Their new offerings of analytics, Builder, and Design Library have added an entirely new level of value to our email marketing team. Litmus has been important in helping us produce emails that are best-in-class when it comes to design and user experience.

Yes, Proof is an integral part of our email creation workflow. We use the collaborative review and approval to ensure that we communicate what needs to be changed in an email before its launch.

Litmus helps us preview our emails in real-time on desktop and mobile devices along with different browsers and operating systems for those desktops and devices. It's extremely beneficial to see the problem areas (if there are any) and be able to address them quickly and on the fly.

We have started using Litmus Proof to facilitate the approval process of emails. As a result, we are able to visually understand the exact changes that need to be made as well as clearly see when an email has been approved by the stakeholder. We have used Litmus Analytics to enhance reports and provide deeper understand of the devices our customers use to view our emails. Using this tool, we are able to see what device was used to view the email as well as the region where the email was opened and how long the contact spend on the email. This allows us to make modifications to our messages to meet the viewer's needs, such as shorter messages for groups of customers who use mobile devices or longer messages with multiple links to targets who spends longer on emails.

This has reduced the time needed for edits and also clarified the changes to be made.

Litmus is an email marketing platform that helps me and my company on a day-to-day. We like to use this platform to collaborate with each other as well as with some of our clients. There [are] also many insights that I and my fellow colleagues are able to use, which has increased productivity for the company as a whole. Overall, the biggest business problem this product addresses is communication and productivity, and it has improved in both areas.

My team and I have definitely used marketing emails to streamline email approval workflow and reduce review cycle time. [The] biggest way we do this is by creating a team task list to understand what needs to be done and what we can check off. This has really helped with productivity as we know what everyone in the team is doing and are able to better help those that could not necessarily complete a task.

We use Litmus to Q/A all of the emails that go out to our global audience (over 200,000 contacts). We make sure the design looks good across all devices/clients, and that there are no other flags (email size, subject line/preheader wording concerns) that would cause the email performance to be in jeopardy. It is part of our process to check every email in Litmus.

We have not yet used the Litmus Proof feature. The email drafts go through (too) many hands in the project process, and we cannot offer access to the tool to 3rd party vendors (our proofreader is not in-house). But perhaps we will consider this option in the future if it can work with our access processes.

We primarily use Litmus to quality check emails, ensuring they render correctly across different email clients, and they do not have other issues like accessibility. We also use Litmus to track additional data such as email clients that are not tracked by the email service providers. We sometimes use it to troubleshoot coding issues with emails.

We have not to use Litmus' Proof feature.

We use Litmus to test emails on various email clients, including testing for Light vs Dark mode more recently. Without this service, our emails would break across multiple email clients that we don't have access to for testing.

We have not used this feature yet.