Product changelog and announcements

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)

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.

Twilio Microvisor is now in Public Beta. Microvisor provides managed connectivity as well as managed security for the lifetime of IoT devices. With Microvisor, you can continuously debug and improve a connected hardware product after it has been mass-manufactured and deployed to the field – by offering unbrickable over-the-air firmware updates and secure remote line-by-line debugging live on deployed devices. Microvisor leverages Arm TrustZone to achieve security and failsafe connectivity through hardware-level separation of communications and application and a hypervisor architecture.

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.

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.