Twilio’s Messaging Insights is a real-time dashboard with multiple reports ranging from messaging delivery and errors to responses and OTP (one-time password) conversions.
Use Messaging Insights to analyze your application's messaging, identify and debug issues, optimize delivery, and find areas to boost engagement with your end users.
You may come to Messaging Insights, which lives in the Twilio Console, to answer questions such as:
- What are the delivery rates for my messages, both incoming and outgoing?
- What caused delivery rates to drop during a certain time period?
- What are my opt-out rates?
- How many of my OTP messages are converting successfully?
This guide walks you through the basic functionality and the four main reports that you'll find in the Messaging Insights dashboard with common usage examples.
You can use filters to narrow down your data across different dimensions throughout all of the Messaging Insights reports. These filters include:
- Time range
- Delivery Status
- Messaging Service
- Error Code
- Twilio number
Use these filters to narrow down the range of messages to the one you care about for a given task.
Messaging Insights' four main reports give you specific insight into the aspects of message delivery:
- Overview: This report displays a high-level view of your outgoing and incoming messages.
- Delivery & Errors: This report displays three deep dives into factors that affect deliverability to help you identify what is causing an issue.
- Responses: This tab includes different ways to visualize and filter the inbound messages that you’re receiving back from your end users.
- OTP Conversion: This report aggregates and visualizes the information that you have sent to Twilio about successful OTP messages.
When should I use it? Analyze delivery health in your messaging application with this view of incoming vs. outgoing messages. Use case, carrier filtering, and geography all affect message deliverability, so we recommend regularly monitoring the Overview Report to establish a baseline.
In this report, the following tiles give you a high-level understanding of delivery rates:
- Status OK: Messages with Delivery Status of “Delivered”, “Delivery Unknown”, and “Sent” are counted as Status OK
- Messages with Errors: Messages that are “Undelivered or “Failed” are counted as Messages with Errors
- Received: Incoming Messages that are successfully received and passed to your incoming webhook URL
- Failed: Incoming Messages that were not successfully received and passed to your incoming webhook URL
When should I use it? Use the three views in this report to identify patterns in delivery status, error code, and message rates of undelivered or failed messages. Once you’ve identified the patterns that affect message deliverability, you can find the most prevalent error codes, look at individual messages to see what is happening at a granular level, and go straight to the docs.
For example, you could visit the Delivery & Errors reports to identify the following patterns:
- A carrier incident causing a rise in undelivered messages
- A Twilio number being filtered
- Country-specific issues
- A mis-configured Messaging Service
The three views break down your deliverability data into different buckets, making it easy to find patterns in delivery status, error codes, and total messaging volume:
- Delivery Status tab: Monitor delivery status over time and identify issues by carriers, countries, and subaccounts, Messaging Services, and phone numbers. Look for spikes to indicate changes.
- Status Code: Drill into error codes to quickly understand which ones are commonly appearing. You can click on the legend to go straight to the relevant documentation.
- Total Messages: See how many messages you sent, divided into different categories.
Selecting one of the three breakdown views changes the view of the data in the six charts below. Additionally, you can filter all of the charts by time range, carrier, and the to/from country.
Say that you notice a rise in the number of failed outgoing messages. Let's use the Delivery & Errors tab to debug.
- Triage the spike by narrowing down to the time window that has the most instances of failed messages. Under the Delivery Status tab, select only the Failed delivery status.
- Drilldown to find the most common error codes on the Status Code tab.
- Fix: Use the linked documentation to learn possible solutions, and view the list of messages to get a comprehensive view of the messages that are failing with that specific error code. For example, if you identified Error 21614 as the most common error code within the pool of failed messages, the linked documentation explains possible solutions for handling invalid
When should I use it? This report gives you a picture of how your end users are engaging with your messages. Catch spikes in rates of opt-outs or “help” messages to find places where your users are disengaging or need more information.
The Responses report displays all of the different responses that you receive from your end users:
- Other: Most Twilio users want to optimize for increased "other" responses. These are messages that contain actual responses from your end users, signaling engagement.
- Opt-Out: These are responses from users who choose not to receive further messages from you. (See the documentation on Advanced Opt-Out.)
- Help: These are responses from users which match your defined "help" keywords.
- Opt-in: These are responses from end users matching your defined "opt-in" keywords.
If you notice a sharp increase in the number of opt-out responses in the Responses tab of Messaging Insights, hover over the chart to see the trend for a given day. From there, you can view the message list for these opt-out responses and determine if the spike is related to the content of messages that you sent during that time frame.
When should I use it? If you are using the Feedback API, use the OTP Conversion report to see how effective the funnel is when someone uses Two Factor Authentication ("2FA"). This is a crucial business outcome for customers.
Many Twilio customers send verification code messages using Twilio. These messages are also called OTP, 2FA, MFA, Verification Code, Pin Code, etc. with a 4-6 digit passcode that a user uses to authenticate.
In the OTP Conversion report, you can get a high-level view of your OTP delivery with the following tiles:
- OTP Messages Attempted: A message request to Twilio with the
provide_feedbackfield set to True
- OTP Messages with Status OK: A message request to Twilio with the
provide_feedbackfield set to true that has a delivery status of "OK"
- OTP Conversion: A "Confirmed" outcome that been provided for a Message is considered a conversion event.
You can add the
provideFeedback parameter on an API request to create a message. When your end user correctly inputs the OTP and authenticates, you send message feedback to Twilio. Your messages will be delivered more consistently if you use the Feedback resource to send Twilio a confirmation when you know one of your end users has successfully received your message.
This feedback on message delivery provides more accurate and complete information than what is often provided by carriers. Twilio uses AI-based routing systems to monitor the conversion signal that we receive and improve our messaging traffic. If our systems detect a drop in OTP conversion rates, for example, Twilio will quickly change the routing accordingly.
You must be using Twilio’s Feedback API to activate the OTP Conversion tab.
We recommend using the
provideFeedback parameter on only OTP messages to ensure a clean set of OTP-related data in the OTP Conversion report.
Let's say that you have used the
provideFeedback parameter and submitted feedback information via the Feedback Resource. In the OTP Conversion report, Twilio aggregates all of the data streams to show you:
- how many OTP messages you have attempted sending via Twilio ("OTP Messages Sent")
- how many messages had no delivery issues ("OTP Messages with Status OK")
- how many messages converted ("OTP Conversions")
- the number of countries in which you are sending OTP messages
First, calculate the cost of total messages attempted ("OTP Messages Sent"). Dividing this number by the number of total successful conversions ("OTP Messages with Status OK") yields the average cost per conversion. Knowing this metric indicates whether your systems are using user authentication in a cost-effective way.
Additionally, you can visualize your per-country data in the OTP Message Volume chart. Clicking on any of the countries listed will filter down to that specific country so that you can track delivery and conversion on a per-country basis.
Visit the Messaging Insights dashboard in the Console to explore the different reports and learn more about the factors influencing your message delivery rates.