Track OTP success with AWS End User Messaging SMS feedback
AWS End User Messaging introduces Message Feedback API for tracking OTP delivery and conversion success AWS has published guidance on implementing message feedback for SMS one-time passwords (OTPs) using the AWS End User Messaging Message Feedback API. The solution addresses key OTP tracking challenges by providing first-party delivery and conversion data, moving beyond reliance on carrier-provided Delivery Receipt (DLR) data. The implementation involves two phases: OTP request flow where the MessageFeedbackEnabled parameter is set to true when sending SMS, and OTP verification flow where the PutMessageFeedback API updates message status to either RECEIVED or FAILED based on user verification success. The approach enables organizations to accurately measure authentication success rates, identify regional and carrier-specific delivery issues, and can be extended to track other SMS conversions like promotional clicks and appointment confirmations.
EUM / SES Relevance
Directly relevant to AWS End User Messaging SMS capabilities. The Message Feedback API enables customers to track SMS delivery and conversion success for OTPs and other use cases, providing first-party data insights that improve message delivery monitoring and authentication success measurement.
Key Takeaways
- arrow_right_alt Message Feedback API provides first-party data for OTP delivery and conversion tracking, offering more accurate insights than carrier-provided DLR data.
- arrow_right_alt Implementation requires enabling MessageFeedbackEnabled parameter during SendTextMessage API calls and storing message IDs for tracking.
- arrow_right_alt PutMessageFeedback API updates message status to RECEIVED upon successful OTP verification or FAILED if verification fails or times out within 1 hour.
- arrow_right_alt Solution can be applied beyond OTPs to track other SMS conversions including promotional link clicks, account activations, and delivery notifications.
- arrow_right_alt Configuration sets can be used to enable message feedback for bulk implementations without specifying feedback settings in each API call.