Product changelog and announcements

Segment has added a new PROFILE_TRAITS_UPDATES table with Profiles Sync, making it even easier for Unify customers to build materialized views.

This table accelerates computation of the PROFILE_TRAITS materialized view, with each row representing a unique customer profile and its most recent traits. We've also included dbt scripts for building materialized views using the new table.

For more information, read Segment's Profiles Sync Tables and Materialized Views documentation.

BigQuery and Redshift Supported as Linked Audience Warehouse Sources - General Availability

Linked Audiences empowers marketers to effortlessly create targeted audiences by combining behavioral data from the Segment Profile and warehouse entity data within a self-serve, no-code interface. With this GA release, the Data Graph now supports both Redshift and BigQuery as a warehouse source.

For more information view our documentation.

Configurable Lookback for Historical Event Data is now available to all users on Business plans. When creating or editing real-time audiences, you can set a lookback window (e.g., “last 90 days”) under Include Historical Event Data to limit how far back event data is processed. Disable it to use only data after creation. This will speed up initial computations by reducing backfill time, while batch audiences continue to include historical data by default.

Starting September 24, 2026, we're requiring HTTPS for all traffic to Functions and Assets, which means customers need to update any webhook or callback subscriptions for these URLs to use https:// instead of http://. After September 24, 2026, any HTTP requests will receive a 301 redirect response and disrupt customers’ Functions. 

Starting January 31, 2026, any new function customers create will default to Node.js v22. Existing functions will keep running on Node.js v18, and they'll only move to v22 when customers choose to redeploy them. 

We fixed an issue where newly created subaccounts didn’t inherit Voice Insights Advanced Features even though it was enabled on the parent account. If you created subaccounts between September 1, 2025 and January 9, 2026 and relied on automatic inheritance of Advanced Features, you can enable those subaccounts in the Subaccounts tab of Voice Insights Settings or via the Voice Insights Settings API.

We're excited to announce that Profile Identifier Deletion is available in Public Beta. 

Until now, profiles in a Unify namespace have been immutable. Profile data flowed in through live events, Unify created profiles, and there was no way to directly modify an existing profile. The only option was to delete the entire profile - there was no way to remove or correct a specific identifier such as an email or phone number.

We’re changing that. Profile Identifier Deletion is the first feature in a new set of capabilities that make profiles editable. With this administrative API, you can now delete individual identifiers (like an incorrect email, phone number, or UserID) from a Unify profile without removing the entire record.

These delete calls can be triggered manually or programmatically using APIs to administer and manage profiles. They are not live events and do not originate from user behavior on websites, apps, or servers.

Customers using the Braze Cloud Mode destination will gain access to Ecommerce Recommended Events through this major upgrade.

We are adding two new actions to the Braze cloud mode destination to support new E-commerce Recommended Events in this integration:

1. Ecommerce Event (multi product)
2. Ecommerce Event (single product)    

Supporting these events provide a more robust and structured approach to tracking e-commerce interactions, purchases, and customer behavior in Braze.Note- The Braze Cloud Mode destination is already in GA, but the new ecommerce actions and presets are labelled with (beta).

Link to API Documentation, here

Now mobile developers can take complete control of how incoming call notifications are delivered to mobile clients using the Twilio Voice SDK. With the Client Call Notification Webhook, your application can receive notifications via a webhook so you can deliver them to your client users on your preferred channels without Twilio in the middle.

And for ISVs who manage subaccounts for their customers, this option also eliminates the need to upload and maintain push notification credentials for each subaccount. 

In all, Client Call Notification Webhook provides 

• End-to-end control of binding management and notification delivery

• Choice of notification channels and configuration options

• Simplified troubleshooting of notification delivery issues

• No need to upload and maintain credentials with Twilio

Check out the documentation for full details!

You can now search for Studio flows by friendly name when selecting a flow from a menu. Search results are limited to the most recent 1,000 Studio flows within a flow menu.

The Studio Flows page now supports searching using a friendly name within the current page of flows. The default page size has been increased to 1,000 flows.