AI-personalized SMS and RCS content
In flows, Klaviyo uses AI to adapt tone and product names in SMS and RCS messages to each shopper's engagement, with automatic A/B tests against the original copy.
Entries on this page are generated by AI from vendor sources. How AI is used
Conditional and data-driven content, templating languages.
| Month | Changes |
|---|---|
| 2026-01 | 8 |
| 2026-02 | 3 |
| 2026-03 | 4 |
| 2026-04 | 8 |
| 2026-05 | 9 |
| 2026-06 | 4 |
| 2026-07 | 11 |
| 2026-08 | 5 |
| 2026-09 | 16 |
| 2026-10 | 2 |
| 2026-11 | 4 |
Select a month to view the whole-record timeline. This clears timeline filters.
Platforms with at least one feature state classified in this capability (primary or secondary, minor updates included), in the site's fixed order. Select one to filter the timeline. Counts are not shown side by side: they reflect how finely each vendor documents, not how much it offers.
Filters apply to the timeline. The chart and platform totals describe the whole record. Selecting a chart month clears timeline filters to show that same whole-record scope.
Matches the Release Matrix evidence: latest state reached in the selected period, entries under review excluded, primary and secondary capabilities included.
No recorded changes match these filters.
Within each period: major updates as cards, then notable ones as rows; newest first in each group. Minor updates below.
In flows, Klaviyo uses AI to adapt tone and product names in SMS and RCS messages to each shopper's engagement, with automatic A/B tests against the original copy.
Flow emails can show or hide blocks and add dynamic content using trigger event properties from any integration, with no code needed.
Marketing Cloud Next lets marketers reuse AI-generated agentic content blocks across email, SMS, MMS, and RCS messages.
Preview and test personalized content as list, individual or campaign recipients across email, SMS, WhatsApp, mobile app and RCS, rolled out by channel in phases in October and November 2026.
Orchestrated campaign email conditions can now reference related records via relational data, not just standard profile attributes.
The Personalization Editor adds a 'Fix with AI' option to resolve PQL syntax errors detected during expression validation.
Shows the live request and response for each Connected Content call in Preview & Test — URL, method, status, headers, payload, duration, and cache status — across messaging channels and Banners.
New Liquid tags provide one-click email subscription group unsubscribe links without changing global subscription state, and retrieve a contact's WhatsApp username from inbound messages.
Lets teams localize webhook payload values from one campaign, Canvas step, or template using translation tags, replacing per-language webhooks and Liquid logic.
The journey advanced expression editor can generate expressions from natural-language descriptions; now GA for all environments.
Developer APIs gain newly supported AMPscript and Handlebars personalization functions.
Non-marketing users can personalize and send distributed marketing messages to many recipients at once.
Handlebars and AMPscript personalization for landing pages, listed in the Winter '27 notes and withdrawn by Salesforce in October 2026 because the feature was not ready yet.
Build a personalization rule once and reuse it across email, SMS and other channels.
Now GA (9 Nov 2026). Current summary: In flows, Klaviyo uses AI to adapt tone and product names in SMS and RCS messages to each shopper's engagement, with automatic A/B tests against the original copy.
Now GA (17 Sep 2026). Current summary: Shows the live request and response for each Connected Content call in Preview & Test — URL, method, status, headers, payload, duration, and cache status — across messaging channels and Banners.
Lifecycle Studio campaigns can be built around a product catalog, selecting real products by title, SKU or free text for generated emails.
AEM Dynamic Media templates, like countdown timers, can now render personalized data at open time inside Journey Optimizer content.
Personalization expressions gain a dozen new helper and template-migration functions, plus a multi-argument concat.
New Handlebars helpers sortBy and groupBy let templates sort and group arrays and display each group with an item count.
Instagram posts can now be embedded directly into emails, SMS messages and sign-up forms without leaving Klaviyo.
Event-specific data such as product viewed or video watched can be used as personalization tokens in automated and workflow-triggered emails, with fallbacks.
Surfaces trending items within a specific catalog attribute such as category or region, instead of only global trends across all users.
Integrates real-time event and ticketing data from AXS, Oztix, Ticketek, and Ticketmaster into campaign content at the moment of send.
The personalization editor gains a Loop block that renders one content block per record from a relational collection.
SMS messages can now include personalized product recommendations built from real-time catalog and customer data.
Now GA (1 Sep 2026). Current summary: The journey advanced expression editor can generate expressions from natural-language descriptions; now GA for all environments.
Messages can be personalized with AMPscript and Handlebars to retrieve recipient data and reuse content programmatically.
Email Designer's conditional content is now supported within Fragments, matching the old email editor's Dynamic Content feature.
Inline profile attribute editing, launched earlier for the Email Designer, is now decoupled from AI Assistant and extended to Push.
Enhancements to Distributed Marketing and Alerts help maintain consistent tone, voice and brand.
Emails can be personalized from two new data sources: live Salesforce Objects such as Cases or Leads, and custom content variables mapped to any Salesforce Flow data source, including MuleSoft and HTTP connectors.
Landing page templates can preconfigure rule-based dynamic content and cross-object merge fields, linking variations across components, including locked ones.
Push, email, Banner, in-app message and Content Block sends can all use locale-based translations, extending earlier per-channel localization.
Content Blocks target users in different workspace locales with translated content; generally available with multi-language translations.
AEM Content Fragment variations, such as language or channel variants, can now be selected when inserting fragments.
Orchestrated campaigns can define global variables once and reuse them across all activities in a workflow.
Destination URLs can now be personalized by profile attribute across all environments, after an earlier journeys-only release.
Static product blocks now render with the recipient's language, currency, URL and market from Shopify Markets automatically.
Contextual personalization now works across email, push, SMS, RCS, WhatsApp and in-app, with a Loomi-optimized default and custom goal events.
Now GA (2 Apr 2026). Current summary: Content Blocks target users in different workspace locales with translated content; generally available with multi-language translations.
The executionMetadata helper function, previously in Limited Availability, is available to all Journey Optimizer customers to append contextual data to native actions and capture it in a dataset for export.
Experience event attributes in journey expressions lose support April 1, 2026 for orgs inactive on the feature for 90 days; already blocked for new orgs since mid-2025.
Rewrites the personalization preview with a unified rendering engine, self-serve syntax/data error debugging, and multi-event validation.
Email Designer's conditional content now applies to segmentations in shared folders, listed alphabetically, matching the old editor's Dynamic Content feature.
Product language, pricing and URLs can now dynamically match each customer's locale using Shopify Markets data.
Lets marketers showcase products from a catalog directly within messages.
Designer-developers can use Handlebars in Code View to add conditional logic or lookups to emails, converting existing emails to code with syntax validation.
Emails can pull Data 360 segment data, Apex class data such as full order collections, and lookup data graphs for product catalogs to power deeper personalization.