1. Home
  2. Email Marketing Software
  3. Litmus Reviews
  4. User Review of Litmus
Litmus is a great supplement to any tech stack!
Updated September 24, 2021

Litmus is a great supplement to any tech stack!

Anonymous | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User

Overall Satisfaction with Litmus

Litmus is a critical tool used by our Developer and Production teams for custom pixel tracking, reporting, and render testing and is leveraged across our service line for clients across industries and verticals. From initial HTML render testing, final HTML QA and email deployment reviews, Litmus is regularly used across technical teams in addition to resolving issues and questions raised by non-technical groups (internal and external).

We leverage custom tracking to enhance our data validation and to craft future-state stories around the impacts of iOS15 and the deprecation of 3rd Party Cookies. The testing environment is critical to our ability to develop and deploy more advanced HTML builds across ESPs and devices that otherwise would substantially slow our time to market.
  • Integration with SFMC! Testing available directly from Content Builder Preview&Test.
  • Analytics reporting to supplement existing results/data.
  • Test sharing internally and externally for stakeholder review.
  • Device tracking in Analytics.
  • HTML best-practice alerts to advise Creative teams for optimal end-user experience.
  • Errors in render engines do not always replicate true HTML rendering.
  • Custom type attributes in analytics reports do not track mobile devices consistently.
  • In tandem with other process improvements, decreased production time from 15 to 10 business days.
  • Device-specific performance metrics across ESPs.
60 seconds saved not waiting for proofs to deliver to Litmus Inbox, multiplied by 6 technical/functional reviews, multiplied by 150+ creatives per year, saves 15 hours of work per year for my client alone. Add in repeat review rounds for changes, the fact we build more than 150 emails per year, and we typically have several concurrent/competing projects and the efficiencies gained from Litmus have increased team output quality (and quantity) to grow our relationship while remaining under budget.
We have used the engagement/performance metrics for client benchmarking and tracking against industry performance for monthly reporting and quarterly reviews in addition to using the individual-level data to deepen the data available for customers.
Sharing the public link effectively shares the same information across service lines and functional groups to more effectively fold into an agency agile approach without cutting corners or manually sharing test results.
Litmus has the preferred GUI setup for easy user setup and training. Despite some render engines potentially running as a mockup rather than the live render engine on different ESPs, the implementation and accessibility benefits outweigh the gaps in performance analytics or in render testing. Litmus is also one of the top industry names for quality and reliability and the time-efficiencies gained track against company KPIs along with client KPIs for effective case studies.

Do you think Litmus delivers good value for the price?

Yes

Are you happy with Litmus's feature set?

Yes

Did Litmus live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of Litmus go as expected?

I wasn't involved with the implementation phase

Would you buy Litmus again?

Yes

Litmus is the perfect supplemental tool to add into technical SOP for testing but as rendering issues present, your first troubleshooting step should be re-deploying HTML to test if inconsistent results are causing issues. For analytics, we leverage Litmus tracking for an additional data source for reporting that is not readily available through other platforms.

Litmus Feature Ratings

Email & Online Marketing
8.3
Ability to test dynamic content
8
Mobile optimization
10
Email deliverability reporting
7
Reporting & Analytics
8.5
Standard reports
10
Custom reports
7
Pre-Send Testing
9.0
URL Validation
9
Link Tracking
9
Spam Testing
9
Email Previews
9

Using Litmus

There are several hundred associates, managers, and teams in general that leverage Litmus in my organization. This number includes teams across not just accounts or verticals but spans multiple service lines from Client Success, Platform Services, Email Development, Creative Strategy, QA/QC, CX, and Digital Messaging. While teams like mine have a greater familiarity with how to leverage Litmus as a solution, all teams listed benefit from the "highlight reel" capabilities of Litmus. Whether that is rolling out a new creative/dev tool for clients and testing functionality, or a creative agency providing code and QA/QC teams running through the render engines to test for rendering issues for poor end-user experience, if your team is working with email, Litmus does have a capability that could be used as an asset to increase efficiencies in the medium term once you have rolled Litmus into standard process.
As a tool that has been fully integrated into a delivery model there are only a handful of people with allocation dedicated to Litmus support. While that is partly due to team comfort and confidence in navigating the tool and addressing questions and/or issues, the support team also fields quite a bit which is fantastic from a resource management perspective. However, if you do have the budget for an IC and or manager with a technical preference, but be mindful of their ability to manage strategic/client facing teams to prevent mis-representations of timing or capabilities to ensure your team is not over-promising and under-delivering. Litmus is a major component in our stack but, as with all things, rarely will a single platform fix ALL issues, but if done diligently and planned appropriately, the right people can DEMONSTRATE efficiencies gained if given the appropriate space to deliver.
  • QA/QC of Final Deliverables
  • HTML development/review
  • HTML issue resolution
  • Custom pixels used to plan anticipated data loss from iOS 15
  • Test new HTML/Creative platform for enhancement issues
  • Teams higher in pipeline may integrate to have HTML-friendly mindset in concept discussion.
Litmus has become so integrated in our technical workflow for a reason. We have already and will continue to renew, and by investing out TIME into the tool (not just budget) my team, and the larger service line, has discovered ways we are able to incorporate Litmus as an ingredient to our overall competitive advantage to in-house client teams or our competitor agencies.

Using Litmus

ProsCons
Like to use
Relatively simple
Easy to use
Well integrated
Consistent
Quick to learn
Convenient
Feel confident using
Familiar
Requires technical support
  • Render testing
  • Standard Tracking Pixel with Reporting
  • Integration with SFMC
  • Custom analytics (as with ALL things custom analytics)
  • Custom pixel modification (make sure you know ALL requirements before starting!)
Yes, but I don't use it
This is a solid platform that is fast and straightforward when it comes to learning and incorporating the "bread and butter" Litmus capabilities. And those work well, work consistently, and are readily available at scale. The complications in the more advanced (aka what will set you apart) functions are, clearly, more advanced in the setup, modification, deployment and monitoring but THOSE are the challenges that, when Litmus is the right tool and you invest the time AND resources to set up, will differentiate the work your team delivers.

Litmus Reliability

With our enterprise account, scalability is not an issue. I have not yet seen or heard of significant issues with user access, API connections for integrations etc. This includes down time for "Scheduled Maintenance" as some providers call them, Litmus has the technology backing to support a global team with a 24-hour workday across regions.
Litmus is up and running when you need it! My team has folks across a LOT of international time zones and Litmus to date has been what keeps the wheels moving, we rarely (no examples come to mind but there must be one out there) see platform issues as the cause for any problems.
As with all technology, there are inevitably use-cases where you are unable to get to your original goal without some good old-fashioned experimenting. Some situations will (and are) more urgent which complicates an effective integration of a new process or a new team using an existing process but the "issues" are regularly resolved by re-starting the process specific to when Litmus is introduced to a project. If it doesn't come out the way you're anticipating, run it again and verify there is an issue before declaring all is lost.