In this guide you will learn when, why and how to send Message Feedback to report the outcome of whether the recipient of a message performed a specific tracked user action.
Message Feedback
Message Feedback is intended for use cases where sending a message leads to a trackable user action performed by the message recipient. The primary use case is the sending of messages with one-time passwords (OTP) and similar authentication or account verification codes (PINs) in two-factor or multi-factor authentication (2FA or MFA) scenarios.
In these cases, there are consistently occurring trackable user actions which are uniquely identifiable, so they can be traced back to a specific sent Message and its Message Feedback subresource.
Examples of such trackable user actions include:
Sending messages nationally or internationally is not a one-size-fits-all operation. Message deliverability varies by geography, involved carriers, use case, and even for individual customers. Twilio uses a mix of automated algorithms and manual adjustments to ensure the best possible message deliverability for customers.
By providing Message Feedback you serve two related purposes:
ProvideFeedback
enabled
As the use case details of your tracked user action may differ, the following step-by-step instructions focus on the correct usage of the Message resource and its Message Feedback subresource.
For illustration purposes, the following steps assume that
id
as a query parameter.
id
query parameter.
Create a new Message with the ProvideFeedback
parameter set to True
to send the message underlying the uniquely trackable user action.
ProvideFeedback
must be set to True
at time of Message creation so that:
Twilio starts
We recommend using the ProvideFeedback
parameter only on OTP messages to ensure a clean set of OTP-related data in the OTP Conversion report.
Store the Message SID of the Message created in Step 1 such that you can retrieve it on the basis of the uniquely identifiable user action you are tracking.
For purposes of the illustrative scenario, the Message SID must be stored and retrievable on the basis of the unique id
query parameter value contained in the URL sent with the Step 1 message.
Track the performance of the unique user action performed in response to the successful receipt of the Message sent in Step 1.
For purposes of the illustrative scenario, you know the tracked user action has been performed, when your backend route handler for the URL sent in Step 1 is called with the unique confirmation id
as a query parameter.
Once you determine that the unique tracked user action in Step 3 has been performed by the message recipient, you
Outcome
parameter value
confirmed
to report to Twilio that the tracked user action was performed.
Update the Message Feedback even if the Message is received with a delay once the conditions for confirmation are met. This ensures the Messaging Insights are current and message delivery optimizations are based on complete information.
Do not update the Message Feedback if the tracked user action is not performed, this will result in the Message Feedback resource's outcome
status correctly remaining unconfirmed
.
Now that you have learned why, when and how to provide Message Feedback, you may wish to check out the following: