Overall Satisfaction with Litmus
We mainly use Litmus to share tests of customer emails with other stakeholders in our organisation. We also use the builder functions to work out any HTML issues in email templates when necessary. We have a team of five people who use Litmus multiple times on a daily basis, as we have tens of email campaigns sent out every week.
- Easy to share tests with stakeholders without formatting breaking, as it can in email clients like Outlook
- Annotation of email tests makes it easier to collaborate with stakeholders. They can just comment on a test rather than replying in long email threads or track changes in a Word doc
- Easy to update versions of email tests and prevent your inbox from getting too crowded
- Builder tool is easy to use and makes code simpler to review than certain email marketing platforms
- Wider choice of email clients in the Previews & QA tab would be nice
- Further integration with marketing platforms like Salesforce, so we can make changes in Litmus and send them back to our campaign in Salesforce automatically
- Make it clearer for new users signing up for free Litmus accounts when proofing tests. While most are able to do it, some less tech-savvy stakeholders get confused
- Email notifications for every comment left by a stakeholder can get grating, especially if multiple comments are made within a few minutes
- Litmus saves lots of time getting feedback on email tests, as the inbox is less cluttered and it's easy to sift through feedback via comments and annotations
- Litmus makes it much easier to present a test email in its intended form, as forwarding it on Outlook can break email templates sometimes. This is completely avoided with Litmus.
- Litmus' ability to separate out Apple clients and devices in stats is incredibly helpful, allowing us to provide more accurate statistics to stakeholders
We use Salesforce Marketing Cloud and it does appear to be integrated with Litmus, but it is unclear how we're supposed to use it. At the moment we just switch between the two, sending tests from Salesforce to Litmus.
We're looking at implementing a Litmus tracking code in our email campaigns which should give us more accurate data, but we haven't been able to make it work yet. I'm sure we would benefit from not needing to switch between the two platforms so that is something we'd be interested in fixing.
We're looking at implementing a Litmus tracking code in our email campaigns which should give us more accurate data, but we haven't been able to make it work yet. I'm sure we would benefit from not needing to switch between the two platforms so that is something we'd be interested in fixing.
It hasn't yet, though we hope to use more of Litmus' analytics function when we sort out Litmus tracking codes in our campaigns.
We use this on a daily basis. It is extremely useful for allowing us to gather feedback and collaborate with stakeholders across our organisation. Before, people would reply to emails with their changes or attach word docs with track changes to their emails, which could be hard to keep track of and risk losing them in a cluttered inbox. Multiple stakeholders have complimented us on how impressed they are with Litmus' proofing function. They find it incredibly simple to leave comments and annotations on an email test and it has made the approval process smoother. It would be nice if stakeholders could get notified if we update the test with a new version though, as currently I still have to tell them that it's been updated.
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?
Yes
Did implementation of Litmus go as expected?
Yes
Would you buy Litmus again?
Yes