Product changelog and announcements

If a SIM exceeds its data limit, it won’t be able to use any more data until the data limit resets at the end of its current billing period. Today, the Super SIM details page in Console now allows you to easily identify how close a particular SIM is to reaching its monthly data limit. There is a new section on the page which shows:

• the SIM’s current billing period start and end timestamps (1 month duration)
• its data consumption within this timeframe
• its monthly data limit, as defined by its Fleet

Use the data limit usage information to determine whether you need to take action such as:

• Move some SIMs to another Fleet with a higher data limit
• Update the data limit on the Fleet your SIMs are assigned to

When requesting a Super SIM eSIM Profile from the /ESimProfile API, you can now request that the eSIM profile be reserved with a matching ID by setting the new generate_matching_id request parameter to true. When you reserve a profile this way, you don’t need to provide the EID of the eSIM that will use the profile, which depending on your use case may be very difficult to know ahead of time or obtain.

When you want to download and install the eSIM profile, you will need to provide the matching ID to your device along with the SM-DP+ URL, both of which can be read from the ESimProfile when your reserved profile is available. The combined SM-DP+ URL and matching ID is often referred to as an “activation code” and often provided to end users via a QR code that they scan with their device during the workflow to add a new eSIM profile.

Refer to the docs to learn more about eSIM Profiles and different eSIM download methods.

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.

This solution enables organizations using Avaya Aura Contact Center solutions that include the Avaya Enterprise Session Border Controller (ESBC) to connect to the PSTN via Twilio Elastic SIP Trunking. You can learn more about this solution by referencing the blueprint guide here: Twilio Elastic SIP Trunking Solution Blueprints.

Twilio now supports new error codes for "Rejected" and "Paused" WhatsApp Templates. With Twilio Alarms, you can now get notified via webhook or email when these and other errors occur.

When a WhatsApp template gets rejected, Twilio surfaces a new error code of 63040 and will include the reason from WhatsApp.

Likewise, if a WhatsApp template is paused due to quality concerns from WhatsApp, Twilio will surface an error code of 63041. The message also contains when it will be unpaused. A template can be paused by WhatsApp when different users report messages sent using that template, or when users block the number after receiving those messages.

The following new Monitor Events have been created for Voice Recording and Transcriptions: recording.created, recording.updated, transcription.created and recording.bulk-delete.created to track bulk deletions from Twilio Console. In addition, we have updated the recording.deleted event to track pci-recording automatic deletion after 72h. The transcription.deleted event has also been updated to track deletion from the transcription detail page in the Twilio Console. These new and updated events are available in the Twilio Console and in the Audit Event/Monitor Event API. Monitor Events are a Twilio platform feature that provides comprehensive event-logging and change-tracking for Twilio resources.

With this release, developers can improve audit of their voice applications and have granular visibility on recordings and transcriptions to contribute to their security and compliance requirements.

See full list of all supported resource-types and event-types for additional information.

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.

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.

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.

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.