Skip to main content
  • 82 Product updates

Build Once, Personalize Everywhere: Introducing the Snippets API
Journey filtering improvements
Unknown User Activation (beta)
WhatsApp enhancement: Resubmit rejected templates
Updates to Iterable's Brand Affinity model
Quickly summarize Segmentation queries with AI
New send skip reason: MMSNotEnabled
New product catalog for Shopify customers
Improved link tracking for heatmaps added to Iterable Snowflake Data Share
New data for CC and BCC email campaigns
Gain insight into the performance of frequency optimized campaigns
New journey tile: Hold for Reply
Improved Movable Ink + Iterable integration
Upgrading to Shopify’s web pixel for enhanced privacy and security
Accessing journey exit events in Snowflake
Segmentation updates
New fields for Snowflake Data Share
New feature: Journey Events
WhatsApp messaging now available
Refreshed Project Settings
Heatmaps
Frequency Optimization Insights beta

Frequency Optimization Insights beta

April 24, 2025BETA FEATUREFrequency Optimization Insights is currently in beta. If you already have AI Suite enabled in your projects, you can start using it today!Frequency Optimization extends Iterable’s Frequency Management feature, so you can personalize the number of messages you send (for a campaign or message type), within a defined period of time based on each user's unique historical engagement data.After you’ve sent messages with Frequency Optimization enabled, you can learn a lot about how your optimized messages are performing by reviewing Frequency Optimization Insights. You can: Learn how key performance indicators (Open Rate, Click Rate, or Unsubscribe Rate) are performing over time. Learn how many optimized messages for a given channel (email, SMS, or push) were sent and how many users received them, along with the associated lift. Analyze the lift, unsubscribes, and send skips for each message type by channel. To review how your message sends are being optimized: Go to Insights > Intelligent Insights to open the Frequency Optimization Insights page. At the top of the page, filter message sending optimizations to display data for the past 30, 60, or 90 days. A 30 day view allows you to focus on the impact of a specific campaign, while a 90 day view may help you evaluate how well optimizations are performing more broadly. In the Performance Over Time chart, view how optimized message sends have performed for a specific metric over a period of time. You can also learn the average number of sends, and which performance metric had the biggest lift and change since the previous period. In Breakdown by Channel, click the tab for the channel you want to view (email, SMS, or push). You can view an overview of the audience size, average number of sends, and the associated lift with for the selected channel. You can also view metrics related to the performance of specific message types.

Related products:Optimize StrategyIterable AI Suite
Updated and new filtered metrics

Updated and new filtered metrics

April 24, 2025To ensure that the metrics you track for email and SMS represent actions by human users, not bots or proxies, this release includes:An updated Total Email Opens (filtered) metric New filtered metrics for email and SMS clicks, including Total Emails Clicked (filtered), Unique Email Clicks (filtered), Total SMS Clicks (filtered), Unique SMS Clicks (filtered)These metrics filter out actions that were performed by new user agents we’ve identified that are performing prefetches and proxied activities. For information, see Metrics Definitions.As part of this update, we’ve also added the isBot data field to filtered email and SMS open and click events. This new data field contains a boolean value set to true when the user agent meets criteria for prefetch or proxy activity. You can use this field in segmentation to generate lists that filter out users who are likely associated with non-human, bot opens. For example:NOTES In campaigns that are running at the time of this update, the Total Email Opens (filtered) metric will include a mix of opens for the non-human interactions that we previously filtered, and those that we’ve added with this release. The opens counted before this update are not retroactively filtered for the new user agents we’ve identified. If you’re using Total Email Opens (filtered) in your reporting, be sure to flag this update as a reason for a decrease in the number of opens reported. If the change gets some attention, you can let others know that the newly reported numbers more accurately reflect “real” user interactions, and will level out with time. We’ll continue to support our existing proxySource field, which can be used with the isBot field for advanced use cases.

Related products:Activate Data
Meet Iterable Nova