Product changelog and announcements

When users reply to a specific WhatsApp message, Twilio now passes additional context to the WhatsApp Sender’s webhook URL. The OriginalRepliedMessageSender and OriginalRepliedMessageSid parameters will include information about the previous message the user replied to. If you need the content of the original message, you can use this API to fetch the Message Resource.

Note that only message replies to messages sent within the last 7 days will contain this additional context. Incoming message replies to messages sent over 7 days ago will still be delivered, but will lack this additional information.

For more information about this and other inbound message parameters, please refer to this page.

Twilio is making changes to Geo-Permissions in the Twilio Console to better differentiate traffic being sent to both Israel and Palestine. Palestine, which previously was only +970 will now include Palestinian networks operating with +972 prefixes. If you enabled geo permissions for Israel and/or Palestine, then we have updated your selection based on the corrected prefixes.  Israel will no longer send traffic to +97256 and +97259 since these two prefixes are associated with Palestinian Jawwal and Wataniya cellular communication company.

If needed, you can enable or disable SMS Geo Permissions to any country at any time in Twilio Console by following the steps in this Support Article.

The default maximum size for queues has been increased from 100 to 1000; maximum size for existing queues remain unchanged, this change impacts newly created queues only. Maximum queue size can be adjusted using the /Queues API via the max_size parameter.

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.