Develops user profiles from CRMs and third-party databases, so marketers can analyze user interest, location, and browser, and review click heatmaps to see which page elements to optimize
Filters standalone or complex segments into lists, enabling data to be split based on user profile or campaign interaction
Automates trigger campaigns based on custom drag-and-drop workflows, allowing marketers to push omnichannel messages to unique customer segments
Provides customizable messaging templates and A/B testing options, so marketers can develop and track metrics on unlimited campaign variations
How Iterable works
Iterable provides tools for communication with your customers across various channels. In order to extract any utility from these tools, however, you need to get all of your customer data streaming into Iterable first. You can install code hooks into your site or app, or send data directly to its API. Your developer will need to learn the ins and outs of how the platform accepts data and the methods the API supports.
There’s also a lot of valuable data generated by Iterable itself, some of the most important being email activity like Delivered, Opened, Clicked, etc. Getting that data out of Iterable and into other tools or a data warehouse for analysis usually means you have to learn its export APIs and build a custom ETL pipeline or realtime streaming engine to get those events out to your other tools, which takes a huge amount of developer time to configure properly.
Get more out of Iterable with Segment
When you use Segment to send your customer data to Iterable you won’t need to write any custom code hooks or ETL to get data into and out of the platform. Your existing Segment page views, events, ecommerce activity, and user traits are passed directly to Iterable without even loading its library on your page or needing to bundle its SDK in your mobile app. Everything is handled through the Segment server.
Additionally, when you use Segment to turn on the integration, all cross-channel activity from Iterable— like Delivered, Opened, Clicked, Unsubscribed, etc.— gets streamed back through Segment as an event and out to all your enabled integrations and data warehouses. No coding is needed for any of this configuration outside of a typical Segment installation, saving you countless development hours and resources considering the alternative of building a custom ETL pipeline and learning new APIs.