Customer.io vs Iterable

• Managing users, attributes and events. You are easily able to modify any user, based on their ID, and add or remove attributes, assign events to them. That makes it very easy to segment later and to assign them to several campaigns based on behavior. Just a warning: this integration isn't so easy (at least it wasn't for us).
• Creating workflows of campaigns is very easy. You can quickly create behavioral campaigns based on attributes, segments and add elements to the workflow. You can send an email, then wait, then send another, then exit the campaign if they converted, etc. The workflow is easy to configure and very powerful for automation.
• We don't use many email templates (we make them in MJML) but it's very easy to add senders, to change templates and in general to test designs.
• Deliverability works very well, at least for us. It sends emails pretty fast and without issues.
• Exporting is very quick and easy. Importing wasn't a feature until recently, but it works well too.
• Seeing activity it's also useful. In general, logs are awesome (be it of a customer, of activity on the site, email sends, etc.).
• We don't use environments, but it might be very useful for a bigger company.

Read full review

• I love Iterable's ability to A/B test not only the messaging but the timing and medium of messages as well.
• Iterable's workflow editor is fantastic. It's far more advanced than most competitors.
• Iterable was easy to get started with because of its Segment.com integration.

Read full review

• Push notifications are very rudimentary. Everything has to be done by hand unless you're sending an extremely simple message.
• A bit too email centric.
• Lacks an ability to schedule messages on a daily, weekly, etc. basis.

Read full review

• Workflow webhooks have limited customization and data options
• Custom events are great for segmentation and workflow triggers, but unusable to personalize an email based on past custom events.
• No rate limiting on webhooks. Easy to bring down a third party vendor if processing a list.

Read full review

• Fast testing for new products to specific groups. It saves a lot of time and money.
• Removed workload from marketing = more time to make it better.
• Better contact with specific groups, seeing a increase in sales because of this.

Read full review

• Hit or miss - our old ESP had a rock solid shared IP pool and sending domains that we were able to use so we never really had to worry about deliverability. Unfortunately it was sunsetted (bronto) and we've had a negative impact on ROI having to move things over but its not necessarily a direct reflection of Iterable hurting our ROI, just the nature of the situation.

Read full review