Product changelog and announcements

Key Pair Authentication for Snowflake is now Available to all users on Free, Team, and Business plans (previously only available to Business Tier users). This authentication adds an extra layer of security for connections to Snowflake warehouses, replacing the use of username/password. Therefore, implementing key pair authentication helps customers maintain compliance and enhance connection security. Note: Secure authentication for SQL Traits with Snowflake is not yet supported, but we will add this feature soon.

Snowflake plans to discontinue support for username/password logins by November 2025.

For more information see our docs:

• Reverse ETL Setup

• Data Graph Setup

• Warehouse Connections

Users can now choose to be alerted when an Audience Computation/Run completes

Description example: This new alert can be discovered and configured via Monitor > Alerting > Default > Engage > Audience Run Completed and is GA.

Audience Event Health alerting has shipped to GA and is available to all Engage users.

• This alert allows users to be notified when a specific Audience’s events fail to sync to the destination by X%.

• Users can choose to send the notifications to an email of their choice, to Slack, or via in-app notifications.

• This release has introduced a new “Alerts” tab to the Audience overview page, one of the places where relevant alerts can be found moving forward for Engage

Segment’s native alerting features have a new home in-app, within Monitor / Alerting. This new interface allows to view and configure all available alerts across their Segment Workspace. A single place to review, configure, and enable/disable alerts for any of our features. 

With SAML-based SSO, users can now automatically join a primary team when they sign in to Flex. In addition, when supervisors sign in to Flex, they can automatically gain oversight of multiple teams as the assigned owner. By using attributes from your identity provider (like Okta), this update simplifies team assignments right from the start. 

To learn more about Flex Teams and how to set up SSO, see Teams in Flex and Configuring SSO and IdP in Flex.

Entity Property Condition Groups is now available for Linked Audiences to all customers on Business Plans with Linked Audiences. When filtering on entity properties in your entity condition, you can now create entity property condition groups, allowing you to utilize both the AND and OR operators in the same entity condition, streamlining the audience building experience. For more information on Linked Audiences, refer to our documentation. 

Meta has announced they will no longer support the allow_category_change property during template creation. Previously, if set to true in a template creation request, this allowed WhatsApp to update a template’s category to marketing, if they determined marketing to be its category per its content and our guidelines. This is now the default behavior.

When Twilio passes our equivalent parameter into WhatsApp it will no longer prevent reclassifications. We have now unpublished this field from our documentation as it will no longer function. API calls with this field will still submit the template for approval but will no longer prevent recategorizations. 

We’re excited to announce that Flex UI 2.12.0 is now available. This release includes:

• A new Flex UI action for Conversations messages that lets you send rich text using a content template and associated variables.

• You can now localize dynamic strings, such as agent status, in custom Flex plugins.

Throughout Flex UI, you'll find feature and UI enhancements, bug fixes, and more. 

For complete details, see the Flex UI release notes for 2.12.0.

Accept PIX Payments on WhatsApp with Twilio/pay
Move from conversation to conversion with native in-chat payments

We’re excited to announce support for PIX payments on WhatsApp using Twilio/pay templates. You can now guide customers through completing a financial transaction directly in WhatsApp.

Use Content Templates with Twilio/pay to:

• Send Order Details messages with a PIX copy code button that opens the user’s banking app

• Send Order Status updates as payment progresses through stages like pending, shipped, or completed

• Display itemized order summaries, expiration details, and total amounts—all within a single message

To enable this, your business must:

• Have a valid WhatsApp sender in Brazil

These templates support variables for payment ID, merchant name, itemized details, and expiration. Rich metadata can be passed to payment processors, with updates automatically sent to users through Order Status messages.

Ready to embed seamless checkout into your messaging flows?
Explore the docs to get started:
twilio/pay