Product Updates

Public API Transformations is available to all workspaces on Business Tier plans with the Protocols add-on.This feature enables you to programmatically maintain your Transformations on Segment instances.With Public API Transformations, you can: Create transformations that support track, identify and group events Perform single event matches Rename events and properties. Perform CRUD operations for source and destination transformations For more information, see the Transformations documentation. 

Reverse ETL is available as a public beta offering.This feature makes it simple to activate data from a warehouse and load it into downstream destinations. Bringing the power of the CDP and the data warehouse together empowers core business teams with valuable customer data so that they can focus on driving business value, such as optimizing customer acquisition, increasing lifetime value, and so much more.For more information, see the Reverse ETL documentation. 

Profiles Sync is available as a public beta offering.This feature makes Twilio Segment's identity-resolved customer profiles portable. Data teams can now access ready-to-query models and data sets, within the warehouse of their choice, to enrich customer profiles in the warehouse according to business needs.Profiles Sync enables data teams to focus on creating valuable audiences in the data warehouse that power personalized customer experiences.For more information, see the Profiles Sync documentation. 

Journey Archive helps marketers end Journeys while preserving historical data. Archiving a Journey stops all Journey calculations and prevents users from entering or progressing through the Journey. Segment retains all of the Journey's data, though, letting you view its historical performance while freeing up compute credits.Learn more in the Build a Journey documentation. 

Segment has enhanced the application of profile merge and mapping limits in the Identity Resolution algorithm.Previously when a profile was at these limits, Segment didn’t resolve any subsequent events to profiles. With this change, Segment uses identifier priorities (as configured in your Identity Resolution settings) to resolve events to the profile.Segment ignores lower priority identifiers that would add merges or mappings to the profile and resolves the event based on the higher priority identifiers. This ensures profiles update with fresh data and eliminates event loss.For more information, visit Segment’s public documentation. 

This month, four new partner-built destinations were released in beta: Kana (documentation) - Beta as of November 1 Kable (documentation) - Beta as of November 1 Aampe (documentation) - Beta as of November 14 Akita Customer Success (documentation) - Beta as of November 22 For questions and support related to these integrations, please reach out Segment's partners. 

New Transformation Types through the Public API, available to all Protocols users, provides support for commonly requested transformations, such as creating new property values, property value changes, capitalization functions, and more.For more information, see the Transformations documentation .

Selective Sync is a service that allows customers to fetch selected data from the Salesforce source. This feature enhancement allows Self-Serve (non-BT) customers to use the Selective Sync functionality without the need to create a ticket with Success Engineering.For more information, see the Salesforce Source documentation.

Segment for Healthcare is now HIPAA-eligible. Twilio's BAA now covers Segment for all Business tier customers. Customers can now use personal health information (PHI) and personally identifiable information (PII) in Segment to deliver personalized care journeys for patients at scale. You can refer to our Architecting for HIPAA documentation and healthcare specific Recipes for how to build on Segment for Healthcare compliantly.For more information, see HIPAA Eligible Segment. 

The Pardot (Actions) destination is now in Public Beta. With this destination, customers can create and update prospects in Pardot. Data is sent server-side and can be used to automate marketing campaigns. For more information, see the Salesforce Pardot (Actions) documentation.

The Intercom Web and Cloud Mode (Actions) destinations allow customers to create leads, contacts, and companies in Intercom. Contacts and companies can be updated with their latest attributes and events. With this data, customers can personally communicate with their users with targeted content, behavior-driven messages, and conversational support. Learn more in the documentation: Intercom Web (Actions) Intercom Cloud Mode (Actions)

The LinkedIn Audiences destination, built on Destination Actions, is now in Public Beta. With this destination, customers can send Engage audiences to their LinkedIn Ads account. Benefits include OAuth support and the ability to sync multiple audiences using the same destination instance to better advertise to users on LinkedIn.For more information, see Segment's LinkedIn Audiences (Actions) documentation. 

The new HubSpot Web and Cloud Mode destinations, built on Destination Actions, are now in Public Beta. With these destinations, customers can benefit from a number of improvements, including OAuth support, clearer mapping of data for an easier setup, and support for custom behavioral events. Learn more in the documentation: HubSpot Web (Actions) HubSpot Cloud Mode (Actions)  

With Engage Channels, you can now deliver personalized experiences where, when, and how your customers want with our native email and SMS channels. Engage Channels includes: Email & SMS Campaign Builders, allowing you to design and deliver email and SMS messages directly within Engage Marketing Engagement Analytics, allowing you to understand the performance and ROI for every email and SMS message you send Subscription Management, allowing you to manage the subscription statuses of your customers directly in the platform  For more information, see the Engage onboarding documentation.

This month, our partner Statsig released their Source integration, which is in Beta as of October 6th for Segment.For questions and support related to this new source, please review the Statsig Source documentation or reach out to Statsig. 

Web Device Mode Destination Filters is available to all users on Business Tier plans. This feature enables you to use the same interface and APIs to prevent certain data from flowing into a destination and gives you more flexibility when working with Segment and your various marketing tools. For more information see the Destination Filters documentation.

Reusable Tracking Plans & Libraries includes two new features: Property Library Syncing and Duplicate Tracking Plans & Libraries. Both features are available to all customers with access to Protocols.Property Library Syncing enables Protocols users to apply changes made to a Property Library across any synced Tracking Plan.Duplicate Tracking Plans enables Tracking Plan users to duplicate existing Tracking Plans and libraries.For more information, see Property library syncing and duplicate Tracking Plans & Libraries. 

What is the Marketing Campaigns (Actions) Destination? Create an Action Destination for SendGrid Marketing Campaigns in Segment’s Catalog. This destination allows marketers to add and update contacts to leverage the power of a CDP and the ease of Marketing Campaigns to create compelling and targeted campaigns. For more information, see the SendGrid Marketing Campaigns Destination documentation. 

Mobile Device Mode Destination Filters is in beta to all users on Business Tier plans and is exclusive to the Analytics-Swift, Analytics-Kotlin (Android), and Analytics-React-Native 2.0 libraries. This feature enables you to use the same interface and APIs to prevent certain data from flowing into a destination, and gives you more flexibility when working with Segment and your various marketing tools. For more information see the Destination Filters documentation as well as the Analytics-Swift, Analytics-Kotlin (Android), and Analytics for React Native 2.0 documentation.

The Engage Event Tester lets you send test event payloads to downstream Destinations.You can use the Event Tester before you publish a Journey to verify that events from the Journey's Audiences successfully make it their Destination.For more information, see the Test event payload documentation.

The Show an ad step lets you send users to an advertising destination. You can also configure exit settings that remove users from the ad step after a specified period of time.For example, you may want to show an ad for only one week to users who abandoned a cart during a purchase. With the Show an ad step, you can remove users from the ad destination seven days after they enter it.For more information, see the Show an ad documentation.

Reusable Tracking Plans & Libraries includes two new features: Property Library Syncing and Duplicate Tracking Plans & Libraries. Both beta features are available to all customers with access to Protocols.Property Library Syncing enables Protocols users to apply changes made to a Property Library across any synced Tracking Plan.Duplicate Tracking Plans enables Tracking Plan users to duplicate existing Tracking Plans and libraries.For more information, see Property Library Syncing and Duplicate Tracking Plans & Libraries. 

The Developer Portal is the place where partners go to manage their integrations with Segment.Once invited, partners can log into the Developer Portal where they can view their integration’s status, manage their integration’s catalog metadata, and invite additional team members to join their team. This feature is only available for partners.For more information, see Segment's Developer Portal.

This month, Bento released a new integration with Segment, which is in beta as of September 21.For more information, see the Bento Destination documentation.For questions and support on Destinations, please reach out to the Destination partner. 

Segment Data Lakes for Azure is available to all users on business tier plans.Segment Data Lakes for Azure makes it easy to build and maintain a customer data lake by landing optimized and schematized behavioral data in Azure Data Lake Storage Gen 2.For more information, see Segment Data Lakes Overview.