Overall we've had a very positive experience with Iterable that has given me autonomy over email marketing and have had not to rely too much on developers to help me achieve my email marketing goals.

The WYSIWYG editor for emails is really nice because I can build emails without any code and make them look on brand and functional. The workflow tool is also really powerful for building automatic campaigns that continually perform well.

Iterable feels like it just slow sometimes. Loading campaigns, saving templates, navigating to different parts of the software. If the pages and elements loaded faster it would feel a lot more snappy.

There is no one tool in marketing automation that is perfect, but Iterable checks the most boxes today out of any of them. Customer support is fantastic. Segmentation is fantastic. UI is improving. The tool's overall power for users with little technical background is superb.

I think the reporting tools could be a bit better. Supports MMS through Twilio would also be a huge bonus.

Automatic blame deflection of any issues we've raised, canned responses and total failure to meet promised value

Cart abandoner targeting promised, non-engineer self-service of complex marketing and retargeting campaigns.

Blaming Segment for failure to merge anonymous events with identified users, blaming Segment for integration failures that caused significant loss of data. Awful limitations of workflows. No ability of non-engineers to actually successfully self-service on pretty much any features. Zero interest on actually enabling us to leverage the service to create value

When I first started using Iterable at my new job, I wasn't a fan. The capabilities were restricted especially in terms of analytics compared to other CRM tools. However, over the last 3 years, they have been adding new features slowly and catching up to other tools. My main problem with Iterable is regarding its UX and usability. As an everyday user, I find Iterable hard to use as you need too many clicks to achieve anything you are doing. I work fast and need to be able to generate campaigns swiftly. Iterable doesn't allow this and you sometimes need to click 5-6 different buttons to open a window.

It is a simple tool that's easy to use and easy to figure out. Great for simple use cases. Email template building experience and features are better than other CRM tools.

The platform is very click-dependant, meaning that you need so many clicks to perform a single function. Navigation is complex. Doesn't allow much flexibility when setting up campaigns.

Overall, I would definitely recommend Iterable. As much as SFMC and others have dominated the market, their data structures and backend setup are more archaic and not easily scalable without custom implementation (SFMC frequently has to shuffle databases around based on client volume since many share instances and the larger ones can take an entire instance down). Although I think Iterable has some catching up to do in terms of more robust customization capabilities, and certain platform capabilities, I still think it's an innovative new tool that has a promising future to bring more powerful function than the old school platforms can keep up with.

The interface is intuitive and easy to use. Having no prior experience, I was able to jump in quickly and navigate through setting up an email blast within a day. The object based data setup is also easy and intuitive to understand, despite coming from a traditional "relational tables" platform and background.

There are certain key features of an Email Platform that I find lacking for Iterable. Nothing show stopping, but things that I would have thought would be intuitively built in: no auto-suppression can be applied based on send classification (transactional vs. marketing), basic date comparison logic is not available (should be easy for eng to build, given they just need to set additional functions), no re-usable global content blocks available (think of SFMCs Content Areas, where you can house snippets of code, or static html, and wherever needed pull that content in to multiple emails, without having to recreate the same code over and over again - universal footer, header, etc).