Skip to main content

October Webinar Product Chat

Thank you for joining our October Product Webinar: How Iterable Helps You Create Authentic Experiences at Scale. It brings us so much joy to share with you how we’re innovating and what we’re working on behind the scenes, and we are really excited to continue the conversation with you right here in the community. For the next few days, the Iterable product team will take your questions about the products that we recently launched and showcased during our webinar. You can post your questions and feedback in the comments section. As a refresher, here are the products that we covered during the webinar:

Creating Great Customer Experiences

* Custom Fonts in Iterable * Campaign Content Selection * React Native SDK * Deep Link Configuration * Unified In-App Animations (_coming soon!_)

Optimizing Customer Experiences With Empathy

* Send Time Optimization * Brand Affinity (_currently in private beta_)

Measuring Your Customer Experience

* Custom Events Usage * Exporting Reports * New Conversion Metrics * Messaging Insights (_coming soon!_)
Thanks for today's webinar. It's great to see the current & future updates. One question on STO. How does it work with experiments? For example, if you're running a 2-hour subject line test would STO impact the test or results? Would the STO activate after the test has completed?
Hi, Will a link to this session be available to view?
Hi @"Ann-Lee Chin" Yes! We'll send it out first thing tomorrow morning.
Hi! Thanks for a great webinar. My team is really looking forward to the updates to Workflow nodes allowing for descriptions. They also thought it would be nice to have a floater description node to explain various test setups within a workflow. We haven't had much success with STO (admittedly we have only dabbled with it) but after seeing the great results other teams have had, we're going to test it more in the coming months. Thanks again!
@Laura Bowers That's a great question. If you run a timed experiment like a 2-hour subject line test, we run the test as normal (no STO) for that portion of your list and decide the winner. Then, after a winner is selected, we optimize the remaining sends using STO. We do it this way because we don't want STO to interfere with determining the winner of the experiment by scheduling sends outside of that initial two hours. Again, great question and let me know if you have any more. 😀
@Abbey Trefzger Thanks for the feedback. I'm glad you enjoyed the webinar. As we look at future workflow and collaboration enhancements, annotations and commenting are top of mind. This isn't yet on the roadmap but is something we will actively considering as we look ahead.
Terms & ConditionsCookie settingsAccessibility statement