Iterable for B2B and B2C
November 01, 2024
Iterable for B2B and B2C
Score 7 out of 10
Vetted Review
Verified User
Overall Satisfaction with Iterable
B2B and B2C full funnel marketing comms and transactional comms. We use email, in app, push and are starting to use SMS. We have about 7-10 daily users who are in Iterable building and/or QA'ing comms. On the B2B side most of our marketing comms are blast campaigns and on the B2C side we rely much more on triggered comms.
Since onboarding to Iterable just over 2 years ago we've gained more flexibility (A/B testing, having more users build comms) and given the marketing team more independent ownership over touchpoints (no longer need to involve product and/or engineering as much)
Since onboarding to Iterable just over 2 years ago we've gained more flexibility (A/B testing, having more users build comms) and given the marketing team more independent ownership over touchpoints (no longer need to involve product and/or engineering as much)
Pros
- It is easy to onboard new users with building communications. The drag and drop editor is very intuitive to use.
- Allows for complex data structures on user profiles and in events. This is a key reason we onboarded to Iterable and have stayed with it.
Cons
- - custom conversion windows
- - more scalable reports
- - comparing multiple events
- - setting up alerts that trigger to slack
- Segmentation - building segments and organizing lists that are already built.
- - relative dates can be confusing but are a critical piece of building lists
- - unable to compare multiple events
- - we have a pretty good naming structure for our lists but with so many daily users, no good way to organize them (with labels or folders) and searching for a list requires you to find the exact word we end up re creating dynamic lists each time
- - static lists don't show you what rules were used to create the list
- - no way to see changes over time
- Improved ways of collaborating. There's no way of knowing if other people are editing a list, template, campaign or journey. easy to overwrite each other's work
- I've been an Iterable user for about 4 years, at 2 different companies. SinceI started using Iterable I think the number of bugs has increased.
- I wish Iterable did a better job testing releases so we're not the ones discovering issues so frequently.
- In app message. We've had issues with this tool/channel starting at implementation. It feels like it never made it's way out of beta, despite us paying for it now.
- The app team offered to do working sessions with us to understand how we use it day to day and never followed up on that. There have been no improvements to the tool and any time we run into another issue with it (although Jena in support is great) it takes forever to diagnose or we are told the issue cannot be replicated. It just feels like we have constant issues with this tool.
- We've actually onboarded to another tool (not ideal for omni channel) for some in app messages because this one has so many downfalls and is so buggy.
- Self serve documentation is great when you have an idea of what you're doing but not entirely sure. It is not easy to understand for people who are newer or less well versed in the platform.
- Time to market. We're (marketing team) able to build campaigns and test them quickly and often without the need to involve other teams.
- The ease of A/B testing has helped us improve conversion rates, especially across key touchpoints.
- I do not think it provides data to inform customer retention.
We frequently use email and push notifications. We are starting to use SMS. We use in app but I really don't like the tool, if I'm being honest. It is buggy and we constantly run into issues with it (it really shouldn't be a tool that we pay for in our contract, it hardly feels like it is out of beta).
Being able to build journeys with all types of channels and include dynamic content in any type of channel has been great to personalize (and A/B test) campaigns.
I don't feel like there are great native tools to inform segmentation (we get analytics outside of Iterable that we use to influence segmentation).
Being able to build journeys with all types of channels and include dynamic content in any type of channel has been great to personalize (and A/B test) campaigns.
I don't feel like there are great native tools to inform segmentation (we get analytics outside of Iterable that we use to influence segmentation).
I'm not sure I totally understand this question.
We primarily use custom events to trigger comms throughout the customer lifecycle. We have custom user fields to indicate which stage of the funnel, or which segment, users fall into. This data gets used to determine the message we include in certain comms and can impact which comms people get.
We primarily use custom events to trigger comms throughout the customer lifecycle. We have custom user fields to indicate which stage of the funnel, or which segment, users fall into. This data gets used to determine the message we include in certain comms and can impact which comms people get.
We have been on Iterable for about 2 years and in that 2 years have evaluated other platforms, considering doing another migration.
The key reason we have stayed with Iterable is the ease of running (largely automated) omni channel comms with a complex data structure. We have started using Appcues for in app messages and cutting back on interable in app due to frustrations with the bugginess of that tool.
When evaluating other platforms we looked for
- native integrations
- ease of use and onboarding new users
- customizability of data
- flexibility of automations and a/b testing
- channels available
The key reason we have stayed with Iterable is the ease of running (largely automated) omni channel comms with a complex data structure. We have started using Appcues for in app messages and cutting back on interable in app due to frustrations with the bugginess of that tool.
When evaluating other platforms we looked for
- native integrations
- ease of use and onboarding new users
- customizability of data
- flexibility of automations and a/b testing
- channels available
Do you think Iterable delivers good value for the price?
Yes
Are you happy with Iterable's feature set?
Yes
Did Iterable live up to sales and marketing promises?
I wasn't involved with the selection/purchase process
Did implementation of Iterable go as expected?
Yes
Would you buy Iterable again?
Yes
Comments
Please log in to join the conversation