Litmus Reviews

All of our email developers use Litmus.

Litmus Proofing is by far one of the best tools in the industry for any email marketing company. Litmus has provided our team with the quickest and most accurate information on how an email will render on all devices that clients want to see. This efficiency of being able to edit the code within the same platform also allows teams to find solutions quickly and get nicely rendered emails out to clients faster.

We use Litmus on a daily basis to ensure all of the emails we design are perfect across all platforms. We're a small team, and our designers rely on Litmus every week. We couldn't do our job without Litmus when it comes to marketing emails. It's a must!

We send out email tests to our team, but that's about it. If there are other ways we can use Litmus to collaboratively test and review, we probably need to investigate that.

Litmus is being used for testing and developing newsletters spread over various email clients. It is used across different departments of the same organization. The main problem it addresses is that we can have quick turnaround time by rapid bug fixing on various email clients. Also, the checklist feature helps in organizing the workflow of the email testing.

We usually send a public URL link as email proofs to the testing team to test them out and give back the review. The approval is streamlined because of this.

I run our email program at Lurie Children's. I use Litmus on every email I send, so it is used across the organization. I support many departments and Litmus helps to make sure our emails are rendering correctly, links work, tracking works, and now, the new accessibility review is great too. We wouldn't be able to send email without Litmus.

We do not have access to Proof.

Litmus is being used for HTML template building and email MKT campaigns testing by our demand generation cell within the marketing area. By using it, we ensure standardization best practices for our promotional emails, the application of HTML, links, and images for all team members and focus markets. Having this tool is very important to also gain operational efficiency and minimize errors.

Litmus is used by 3 email marketing analysts in my organization. We use it mostly for spam testing and to edit our HTML codes.

My team mainly uses 2 features in Litmus at this time. The first is for testing email formatting in various clients. This helps us execute mobile-first designs and catch any unwanted formatting issues for our users. Secondly, we use the tracking code to learn more about the behavior of our audience. Looking at the time in email helps us measure the success of content and the optimal length of an email.

We haven't used this feature yet. But there is a real need for it within my department.

Litmus is used as a "check-up" tool with Litmus Proof for our all approval process within all our Marketing teams across the whole organization. We solve problems like manual transcription errors with a bulletproof review process and visualization on both desktop and mobile versions which was time-consumming without this tool.

Yes, this is the most useful feature for us now and we use Proof for every campaign we send out now.
As the developer, I am the only one using the task list for now but looking forward to extending this throughout the team.

I use Litmus in our email channel department to review, provide feedback, and approve custom HTML emails. It allows me to not only have a preview of the email in a more user-friendly format than would be available in our marketing automation platform but I can circulate it to my other marketing partners who don't have access to our automation platform. The ability to assign tasks and manage changes is helpful. The tracking functionality is a great bonus and provides useful insights to our user's email habits and preferences.

In my role, the testing, review, and approval features are most impactful. Litmus allows me to streamline the proofing process, assign tasks where necessary, and with the appropriate parties and follow-up accordingly. Having this functionality overlayed with the actual email proof makes the process far more efficient and pleasant. Go Litmus!

Litmus has changed our email program workflow tremendously. We’ve seen a great increase in productivity since we adopted it nearly two years ago now. Our higher up executives are able to make quick edits and revisions in a way that they feel comfortable with and in a way that doesn’t require a lot of hand-holding. It has been an absolute game-changer for our organization.

Our organization has 20-30 sub-organizations each with their own email representatives and opinions. Proof has enabled us to streamline and improve this process by creating users and groups for the various sub-organizations as needed. It is something that, at this point, we honestly could never imagine not using. It has revolutionized our email program workflow at the proofing stage.

We use Litmus mainly to get the rich email analytics tracking and to test that each of our communications looks perfect in every platform. We love the tracking code it has as it is far superior to what we get through Salesforce normally. We send our emails through the Marketing cloud due to better integration with Salesforce but we build them, test them, and track them with Litmus. Also, Litmus' newsletter and resources are of great help to keep our communications updated and up to date with the latest trends.

We haven't used this feature much since the email team is small and in close proximity. We will be using these features more as time passes by.

We use Litmus on a daily basis. Initially we sought their tool out because we needed a way to check how our emails were rendering across various email clients, but it quickly became so much more than that. The tool offers advanced analytics that tell us how long recipients had our email open for, their geolocation at time of open, what type of device they were using and even the version/operating system! The checklist, spam checker, approval tool (currently called Proof) and other features have become staples of our email marketing program and we use Litmus on every. single. email. that we send.

We already have an internal collaboration tool to track revisions made to our assets that's tied to our project management tool, and we won't be able to incorporate Litmus Proof until we switch project management systems. Proof is so focused on email, that it solves all of our pain points when reviewing, revising and ultimately approving our content. When we switch project management tools, one thing I'll be sure to introduce alongside the new tool is Litmus Proof.

Our creative team comprises more than half of our organization, and uses Litmus to quality-check and AB test html layouts created in-house for our various client's email marketing campaigns. Using Litmus as a tool in our workflow has given us the ability to address potential rendering issues that could otherwise have derailed, or at the very least held up project timelines, which of course ultimately benefits our clients.

As stated previously, the ability to share test results and collaboratively review our campaigns across platforms saves a lot of time and helps to define our strategy internally and with the client. Litmus' proof feature is our primary use of the service and acts as a failsafe before we send any email marketing creative for review.

It's being used across our organization, in my Email Marketing team we use it a lot for analytics and spam testing, but also to build emails.

We're currently using Litmus primarily as a rendering tool to gauge how our HTML-coded emails display across the most popular email clients. The developers use it to QA their work before sending it to QC for a full and thorough review. The developers also use it to build HTML and make quick updates to their code. Post QC, team members who load the HTML into our platform system also use Litmus to confirm that any HTML updates haven't negatively affected rendering.

We use Litmus at Movember for testing and QAing our global email marketing campaigns. We use the Checklist feature specifically to preview how each of our email campaigns will appear across different user devices. This addresses the problem of having to manually test each email on different browsers or devices.

Compassion International uses Litmus for their bulk email testing. We have an email list of over 600,000 constituents and send tens of millions of emails every year. Litmus is utilized by both the marketing department and our digital production department who are responsible for sending bulk email. We have a diverse audience that utilizes the majority of email clients on the market. Litmus provides the most robust testing environment, we're currently testing our emails in over 70 different email clients. We also utilize Litmus' analytics to measure the engagement and to better understand the technical demographics of our audience.

We currently have a routing process that is outside of Litmus for reviewing and approving our emails. However, I believe we can improve our process by using the tools that are already built into Litmus. We will be testing campaigns of different sizes with Litmus Proof and comparing it to our current in-house routing process. I anticipate Proof will bring further time savings to our organization.

Litmus is used across my department, from production to management. We rely on Litmus to make sure our email templates render correctly across a vast array of inboxes. Litmus Checklist instills in me the confidence that my carefully crafted message will be received as intended. Litmus Proof makes it easier to get stakeholders to collaborate on one document. It streamlines the often painful process of having a project reviewed and approved.

We've used Proof to streamline the approval process, by having all stakeholders in a central location with a solid visual representation of an email template is a huge time saver. Having a history of revisions and approvals produces a grand paper trail, for posterity.

The Marketing CRM team uses Litmus as part of our QA process for every email campaign and new email template we deploy. We use the tool to test email responsiveness and rendering among commonly used devices, browsers, and email providers. It's a very powerful tool that we use over the email rendering service integrated into our current ESP. We've also recently adopted the proofing tool within our QA process to have stakeholders review content, share feedback, and provide approvals.

We only recently started using Litmus Proof after our Account Manager reached out and scheduled a chat with our team to learn more about our use of the tool and some features we weren't aware of. It has been integral to streamlining email review and approvals with stakeholders who aren't on our team and wouldn't have logins of their own. We have also used it internally to review new templates and touch points. As an email developer, it provides a seamless way to review comments from reviewers and implement updates.

We test how emails look in different email clients and use analytics for insights and decision making on what method to use for building emails. Through partials and templates you're able to put everything in Litmus.

Litmus is being used by the Email Marketing team. It helps us when it comes to creating HTML templates, testing in different email clients, and conducting spam tests. Litmus helps a lot to avoid inbox problems.

We use Litmus to test marketing emails across clients. It's important to ensure brand consistency across devices, and Litmus helps us do that.

Seeing all the previews in a central place helps us catch any issues, communicate to stakeholders, and find a resolution quicker.

Litmus is being used at a department level. It helps examine the deliverability and accessibility of emails in between browsers. Sometimes, when test emails do not send, we use Litmus to build the email in HTML to send it around for approvals. It fits a niche need and is a solution for it.

Litmus is being used in Tangerine by Developers and Software testers. It is used to check the emails in development on various desktop and mobile clients. Also, we use it to test on various mail platforms like Gmail, Outlook, Hotmail, etc. Testing team use it for all new developments to be tested in different browsers.

As a tester, I am using a checklist to drive my testing and enter issues accordingly. As a team, we review and solve the issues for the required fixes.

Litmus is currently being used by our Digital Marketing team to test how emails will render on various emails clients across multiple platforms, and for their robust email analytics to gain insight about our subscriber base.

We have not used Litmus Proof feature to gather feedback, but have considered it. Currently, only those responsible for email development in our organization are Litmus users.