Product changelog and announcements

Analytics.js Classic has entered End of Life as of February 28th, 2023.

This means that Segment will no longer maintain or upgrade the Classic version of Analytics.js. 

All sources leveraging Analytics.js Classic will be auto upgraded to Analytics.js 2.0 by the end of March 2023.

With Subscriptions with SQL Traits, marketers will have the ability to quickly and easily import subscription data into Engage with SQL.

For example, some companies may enforce employee policies restricting the storage of PII on local computers, which makes subscription-related updates via CSV uploads redundant, and limits options for marketers who may not have developer resources readily available.

Marketers don’t always have the skill set to utilize an API but are often familiar with SQL, making our SQL Traits feature a much easier approach to syncing subscription data between their data warehouse and Twilio Engage.

Subscriptions with SQL Traits is available to all users on Engage Premier. For more information, view the Subscriptions with SQL Traits documentation.

The Webhooks (Actions) destination is now in General Availability.

With this destination, customers can submit real-time user data to any webhook URL.

For more information, see Segment's Webhooks (Actions) documentation.

The Salesforce Marketing Cloud (Actions) destination is now in General Availability.

With this destination, customers can create contacts, store contact and event data in data extensions, and send API events to Salesforce Marketing Cloud. Benefits include batch support, flexible primary keys, and an API upgrade.

For more information, see Segment's Salesforce Marketing Cloud (Actions) documentation.

New functionality to send Firebase app events to the Google Analytics 4 Measurement Protocol API is now available in Segment's Google Analytics 4 destination.

This allows customers to send mobile events to GA4 server-side. Google recommends a parallel implementation with the Firebase SDKs. You can use this new functionality to supplement any mobile data sent client-side.

In an ongoing effort to raise awareness of the risk of SMS Traffic Pumping fraud, Twilio has added a popup asking customers to acknowledge the risk when opting to send SMS traffic to countries Twilio has identified a rise of SMS Traffic Pumping Fraud. Twilio will update this list from time to time.

What do I need to do?

We recommend review of the current geo-permissions on your account in Console.

(Support Article) Please take the following steps to protect your account from SMS Traffic Pumping Fraud:

1. Log in to your Twilio Account and verify the traffic history on your account is legitimate in Messaging Insights.
2. Take steps to protect your applications from abuse by following best practices in this SMS Traffic Pumping article, including turning off geo permissions for countries when not in use.

This release addresses issues around increased plugin loading time and list of agents not displaying correctly when the hidden filter property is configured.

Twilio Application Connect for Programmable Voice is now Generally Available. We have added an <Application> noun to the existing TwiML <Dial> verb, which allows you to place Voice calls from one TwiML Application to another. This allows you to:

• Connect Voice calls across Twilio accounts, without using a Twilio number or SIP Proxy in-Between.
• Separate complex application flows into smaller, more modular applications.

For more information on Twilio Application Connect, please check out the Usage and TwiML documentation.

Language-specific client SDKs for the Public API are available to help you adopt the Public API more efficiently.

These SDKs are open-sourced, and available on GitHub for Go, Swift, TypeScript and Java.

In order to provide additional information and transparancy around delivery timing we are adding a new parameter (RawDlrDoneDate) to Delivered and Undelivered status update webhooks for MMS and SMS messages. This parameter is a passthrough of the Done Date included on the DLR (Delivery Receipt) that we receive from our carrier partners. It takes the format of YYMMDDhhmm where:

YY = last two digits of the year (00-99)

MM = month (01-12)

DD = day (01-31)

hh = hour (00-23)

mm = minute (00-59)

Important notes on this data:

The format only includes minute level precision.

• The format does not provide timezone information. In practice, the timezone offset varies between carrier partners and even within the same carrier.
• Because of SMS/MMS signaling intricacies, not all messages will receive a RawDlrDoneDate in the Delivered or Undelivered status. Not all carrier partners offer DLRs and some messages go undelivered before a DLR is available.
• This parameter will also be added to Event Streams in the near future. Integrating with the parameter in event streams will require upgrading to a new schema version.
• The feature will be rolled out gradually. We expect the vast majority of Delivered/Undelivered messages to include the data by the end of February 2023.

It is strongly recommended that you use a Twilio provided signature validation library to verify the provenance of all webhooks arriving at your servers. The specific ordering and parameters included with each webhook depend on a number of factors and will evolve over time; thus it is important to follow the full specification of signature validation. This is already fully implemented and tested in the Twilio provided SDKs.