What do you like best about Listrak?
The onboarding team made the transition from our previous ESP seamless. Their technical team integrated 4 separate brands with Shopify+ and built templates and journeys to get us up and running quickly. In some cases we provided detailed XD files and in other instances just screenshots for their team to replicate.
Listrak handled porting our customer data, including custom properties, with the data export I provided. I shared our subscriber data and Listrak provided all the unique segments for the IP Warm-up process.
As a new user, I don't always know what I didn't know (as expected), but every time I had a question, I got an almost instant reply and explanation. It is reassuring to know that they are watching and can catch (my) mistakes before I do. The level of attention is what I've noticed and appreciated most about the Listrak onboarding process.
I haven't had a chance to take advantage of the dynamic content blocks yet, but I have found the product recommendations and Shopify product blocks to be both robust and customizable.
My favorite feature of Listrak, and a significant advantage over our previous ESP, is the Saved Content blocks. I love having multiple elements in Saved Blocks (image, text, CTAs) that I can update across all messages as a single block or separate blocks (e.g., header/footer). Review collected by and hosted on G2.com.
What do you dislike about Listrak?
Every platform has its pros/cons and Listrak is no different. I have appreciated the UX of the Journey hub for building workflows, but would love to have more pre-built journeys that I could replicate on my own (e.g., a birthday anniversary). The latter had to be built in their legacy automation system (called Conductor) which isn't nearly as user-friendly. Thankfully, our Listrak contact built it out for me!
I am still learning the content folder structure and wish I had spent more time thinking how my file naming convention (and sub-folders) would impact future messsages. If you change a file name or location, file references will break as they cannot find the specific file. With 1000s of images and saved content blocks already, I have created a mess of files in a few short months. It is difficult to search and view existing content files without a good folder structure.
My biggest complaint about the Composer message editor is the inability to switch to an HTML-view within the editor. You can build an entire email in HTML, but I would like to see what the existing HTML looks like to double-check my formatting. It is annoying IMO to check font size, font family, and event hyperlinks in the WYSIWYG editor. You have to highlight the relevant content and then click on the different elements to see how it is assigned. Review collected by and hosted on G2.com.