What is our primary use case?
My main use case for Iterable during that time was to verify marketing products, analytics, and engineering teams to design documents and optimize customer engagement and workflows.
A specific example of how I used Iterable for customer engagement or workflow optimization is that I was able to use Iterable for most power segmentations and personalization, which gave me a lot of capabilities, especially with real-time data and user events. It allowed me to move beyond static lists into behavior-driven personalization. Iterable's workflow and journey builder was also very helpful, providing a visual journey that made complex customer flows easier to understand and document. This explanation helped me demonstrate the value to cross-functional stakeholders, which is extremely valuable for large teams. From an API or data integration standpoint, it helped with my technical documentation and allowed me to track all events systematically and plan marketing integrations smoothly, resulting in a comprehensive internal system view and data pipelines.
How has it helped my organization?
Iterable has positively impacted my organization, as it enhanced campaign execution speed, increased engagement and conversion rates through personalization, reduced our dependency on engineering for routine campaign changes, and improved collaboration between marketing and technical teams. Overall, it contributes positively to both customer experience and operational efficiency.
I can share specific outcomes related to those improvements: the conversion rate has increased from around 15% to close to 60 to 65%. Furthermore, after using Iterable, customer acquisition rates improved from approximately 20 to 30% to nearly 70%. These numbers clearly reflect the positive impact of Iterable.
What is most valuable?
Iterable's best feature, in my opinion, is the unified cross-channel engagement, which relates to powerful segmentations and personalization. The strong API and data integration support create a wealth of information.
Iterable's unified cross-channel engagement and strong API data integration made a significant difference for me, allowing for seamless integration and engagement across various platforms.
Regarding features, I find that the unified cross-channel engagement is one of Iterable's greatest strengths, enabling true omnichannel journeys in a commendable way. Being able to design, trigger, and monitor campaigns across multiple touchpoints from one interface significantly reduces operational overhead and improves message consistency. From a technical and documentation standpoint, Iterable's API and event tracking are well-structured, well-maintained, and regularly upgraded. This ease of integration with internal systems and data pipelines is incredibly helpful.
What needs improvement?
I would like to highlight some information that could make Iterable even better, which I discovered during my tenure with Iterable. For example, more out-of-the-box advanced analytics and attribution views would strengthen its appeal to users. Second, additional guided templates for complex lifecycle journeys would be beneficial to avoid overwhelming users with too much complexity or tactics. Lastly, continued investment in performance optimizations for large-scale workflows is essential. It is crucial to focus on mid to large organization scales and serious lifecycle marketing personalization for customer engagement. If these points are addressed, it could help many users like me and others look forward to a better platform.
Iterable challenges I have faced include a steep learning curve for advanced use cases; basic campaigns are easy to launch, but advanced and personalized campaigns or event-based logic take considerable time, which is a challenge for new users. Another challenge is reporting and analytics at a deeper level; while the reporting is good, deeper analysis often necessitates exporting data or integrating with BI tools. Lastly, I have noticed that UI performance can lag with very complex journeys, especially in highly branched workflows, leading to a heavy interface that can slow down the loading times.
For how long have I used the solution?
I have been working in my current field for approximately nine months.
What do I think about the stability of the solution?
Iterable has demonstrated stability throughout my experience with it.
What do I think about the scalability of the solution?
Iterable provides good scalability, offering options and variations compared to competitors.
How are customer service and support?
My advice for others looking into using Iterable is that it provides very reliable and professional customer support, especially for time-sensitive campaign issues and complex integrations. Iterable's support team shares best practices and alternative approaches during onboarding and feature adoption. While resolutions to complex edge case scenarios may take longer due to escalations, communication remains transparent throughout, building trust. Overall, Iterable's customer support feels like a true extension of our team.
On a scale of 1 to 10, I would rate Iterable's customer support a nine because they are highly responsive, knowledgeable, and provide clear actionable guidance for time-sensitive campaigns and technical issues. Iterable's customer support is not a ten only because complex edge case issues can occasionally take longer to resolve due to escalations.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
We did not switch from a different solution; instead, we are using multiple options to find the best fit, with Iterable among the solutions. Previously, we tested Shopify and Shopify Wishlist Plus, but we are still determining which option will work best for us, and the feedback on Iterable has been quite positive.
How was the initial setup?
My experience with pricing, setup cost, and licensing for the enterprise version of Iterable indicates that the pricing is manageable and did not strain our budget. Iterable's setup cost was not high, as we had numerous videos available to guide us on setting it up, and the licensing options were flawless, leading to no issues with purchasing, uploading, and utilizing it for our team and company.
What was our ROI?
I cannot provide exact monetary metrics, but I can share that we observed a percentage improvement; our efficiency increased from around 20% to approximately 70%, which translates to a 40 to 50% increment since implementing Iterable.
Which other solutions did I evaluate?
We evaluated other options, such as Shopify Plus and others.
What other advice do I have?
As we continue to explore options, my advice for those considering Iterable is to start by clearly defining customer lifecycle goals first. Then, one can leverage Iterable's strengths in event-based personalizations and cross-channel journeys. It is beneficial to invest time into cleaning data integrations and event tracking early on. I recommend thoroughly utilizing Iterable's documentation and onboarding resources, beginning simply without over-complicating things at the start, and then gradually moving to more advanced journeys while actively engaging with customer support for best practices.
My company's relationship with the vendor is limited; we do not have a different business relationship besides being a customer. Iterable is best suited for teams that are ready to manage their customer engagement in-house, allowing for direct control and flexibility in customer engagement programs rather than relying on third parties for campaign management.
I appreciate your questions, and I have a few more final thoughts regarding the product. I would rate this review a seven overall.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?