Litmus for multi-language reviews
June 30, 2019

Litmus for multi-language reviews

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

Overall Satisfaction with Litmus

Litmus is used for approval of email language and translations. It is used by the localization team across the globe to gather feedback from native speakers before a mass send to the recipients. It is also used by the email team along with Eloqua, so they build a layout once instead of many times for each language.
  • Interface is easy to use, especially when the email owner does not speak the language of the email approver. Highlighting different sentences for language tweaking makes the changes more specific and less confusing to EN-only speakers who wouldn't be able to tell what is different so easily.
  • Eloqua-Litmus integration makes it easy to build a single email that can be applied to many different languages and footers. This means our team doesn't have to build the same email many times in different languages, since Litmus correctly applies different pieces of content to the same email template.
  • Pre-header text: This doesn't work well all the time, many times we have trouble adding localized pre-header text to emails, and we have to add those as comments instead for language approval.
  • Notifications: We get those via email for every single new comment or implementation, and they stack up on Gmail, which isn't an easy read. Push notifications per project would be more reasonable in my opinion.
  • Dynamic fields: They don't work too well when localization kicks in. For instance, in English, "Hi there" is often handed to native speakers as "Olá there" or "Hola there," which is not ideal and has to be fixed in post before email launch.
  • It's given a much more clear sense of what cross-team collaboration looks like, since the different inputs from different approvers and reviewers are made very clear and synthesized as "comments" on a single email file. The changes are specific to sentences or buttons in the email, which makes it much easier for the email builder to understand what needs to be changed and where that change is located in the HTML.
  • Negative impact on the approval of nurture sequences, since emails are handled separately, and you have no sense of continuity or sequence.
  • It's a negative on comparing two emails (in English and in a different language, for instance). There is no way to compare emails-- you have to open them in different tabs and switch those yourself for comparison.
Litmus works much better than a shareable Google Doc, for instance, since you can see the visuals of the email (banner, header, footer, pre-header text, etc). Like Google Docs, you can add comments anywhere you like and your input is clearly placed where it's meant to refer to. It's better for approval than Eloqua email tests, given the commenting feature and multi-review capability.
It's very well suited for team collaboration on a single email, as well as international language approvals.
It's not too well suited if you want to approve a large cadence of emails all at once, which used to be the case for me since Litmus carries different URLs for every single email, and you have to send those separate links in order for the approver to have a sense of sequence and continuity.

Litmus Feature Ratings

WYSIWYG email editor
Not Rated
Dynamic content
Ability to test dynamic content
Landing pages
Not Rated
A/B testing
Mobile optimization
Email deliverability reporting
List management
Not Rated
Triggered drip sequences
Not Rated
Standard reports