Product changelog and announcements

Beginning March 16, 2022, for new customers only, Twilio SendGrid will begin limiting category statistics on a seven-day rolling basis. This means all categories will be available for the first seven days. After seven days, the top 100 categories will be retained for free customers, and the top 1,000 will be retained for paying customers.

Customers who require access to all category statistics can use the Event Webhook to retrieve and retain the data on their own systems as long as they save it within seven days of first sending the event.

Twilio SendGrid accounts created before March 16, 2022 will continue to have access to all category statistics during this phase of our changes to the category statistics system. Limitations for existing customers are planned to begin in Q2 2022.

For more information about how this change works, please see the "Limitations" section of our "Working with Categories" documentation.

Many customers find that Unique Arguments, which are not limited, are the best solution for their needs. See the "Categories vs Unique Arguments: Benefits & Limitations" blog post to better understand these two tracking tools.

Previously, requests that Twilio made to <Pay> action callback URL or <Autopilot> action callback URL have included encoded parameters. Twilio will start decoding parameters in responses. Your application will need to be updated to be resilient to this upcoming change by March 31, 2022.

As of March 15, 2022, Twilio Group MMS is limited to existing accounts until further notice. Twilio accounts that created Group MMS before March 15, 2022 can continue to use the Group MMS feature.

If you are new to Group MMS and attempt to use it, you will receive an error message that the service is unavailable. We are sincerely sorry for any disruption this may cause. For any questions, please contact the Twilio Support team.

Customers can now keep up with the latest Regulatory requirements by updating their Regulatory Bundles through Public API and Console using the new action required compliance information update experience. The new compliance information update workflow allows customers to continue provisioning new phone numbers for a specified amount of time while updating a Bundle Copy and submitting to Twilio for review.

The Conference Summary and Participant Summary from Conference Insights is now available via Event Streams. Both summary records return useful metadata about the conference and its performance. For more information see our docs.

The Conference Summary and Participant Summary from Conference Insights is now available via Event Streams. Both summary records return useful metadata about the conference and its performance. For more information see our docs.

Analytics Swift and Analytics Kotlin represent the next generation of mobile instrumentation in Segment. They are more performant than Analytics-iOS and Analytics-Android, and provide a host of other benefits, including better extensibility and increased target platform support.

For more information, see the product documentation for Swift and Kotlin.

Built on Segment’s Actions framework, these conversions destinations provide flexibility in how events and properties are identified as conversions.

These destinations send hashed and encrypted first-party conversion data in real-time to Facebook, Google, and TikTok respectively. Once in the downstream tool, you can use the data for ad measurement, campaign optimization, and reporting.

For more information, check out each destination’s documentation:

• Google Enhanced Conversions Destination
• Facebook Conversions API Destination
• TikTok Conversions Destination

The Google Analytics 4 destination lets you send data to the fourth version of Google's widely-used analytics platform, taking advantage of its powerful new features.

New users can implement easily, and current users can migrate without making any changes to the events and properties they are already collecting.

For more information, see the Google Analytics 4 documentation.

A deleted call recording can now be fetched via Programmable Voice API using a new IncludeSoftDeleted querystring boolean param and set its value to true when fetching a recording resource or reading multiple recording resources. By default, fetching a deleted recording returns not found and deleted recordings are not returned in the list.

Prior to this release, when a recording was deleted, metadata was only available in the Twilio Console. With this change, recording metadata is also accessible and behaves the same for Programmable Voice API.

Note that when a recording is deleted, the recording media cannot be recovered and no storage cost apply. The recording is set to a status of “deleted” and the metadata is preserved for a period of 40 days, during which time the metadata is still available.