Amplitude and Twilio integrate through Amplitude's Cohort Syncs and Behavioral Cohorts feature combined with the Twilio Messages API to trigger SMS when users reach specific behavioral milestones or drop off at critical funnel points identified by Amplitude analysis. This integration is used by product and growth teams that use Amplitude for product analytics and want to act on behavioral insights by sending targeted Twilio SMS to users who match specific cohort criteria such as users who completed onboarding but have not returned, users who reached the trial limit, or users who activated a specific feature. The connection uses Amplitude's Data Destinations to export cohort membership changes to your middleware or data warehouse, which then triggers Twilio SMS for newly qualifying users.
What You Need Before You Start
Create an Amplitude API key and Secret Key from your Amplitude project settings under General, noting both values as you will need them to authenticate when calling the Amplitude REST API to retrieve cohort membership data. Set up an Amplitude Data Destination by navigating to Data, then Destinations in your Amplitude account, clicking Add Destination, and selecting Webhook to point cohort sync exports to your middleware endpoint, configuring the sync to fire when a user enters or exits a specified cohort. From Twilio, collect your Account SID, Auth Token, and an SMS-capable phone number, and ensure your Amplitude user properties include a phone property set via the Amplitude Identify API at https://api2.amplitude.com/identify, as Amplitude does not natively collect phone numbers and you must instrument your application to pass the phone as a user property. Build your Amplitude behavioral cohort by navigating to Audiences, then Cohorts, defining the cohort criteria based on event sequences and user properties, and setting the cohort to sync on a scheduled or real-time basis to your webhook destination.
Step-by-Step Integration Guide
When an Amplitude cohort sync fires to your middleware webhook destination, the payload contains an array of user IDs and their cohort membership change type (entered or exited), along with any user properties included in the sync configuration. For users who entered the cohort, extract the Amplitude user ID and look up the phone property by calling the Amplitude User Activity API at GET https://amplitude.com/api/2/useractivity?user={userId} with Basic authentication using your Amplitude API Key as the username and Secret Key as the password, reading the userData.user_properties.phone value from the response. Normalize the retrieved phone to E.164 and dispatch the Twilio SMS by calling POST https://api.twilio.com/2010-04-01/Accounts/{AccountSid}/Messages.json with Basic authentication and a Body tailored to the cohort: for a Completed Onboarding but Not Returned cohort, the SMS might ask if the user needs help getting started, while for a Trial Limit Reached cohort the SMS offers a direct upgrade link. Log the SMS back to Amplitude as a custom event by calling POST https://api2.amplitude.com/2/httpapi with your Amplitude API key and a JSON body containing the event_type set to SMS Sent, the user_id, and event_properties including the message body and delivery status, enabling Amplitude to measure SMS impact on funnel progression using the Funnel Analysis and User Journeys charts.
Common Issues and How to Fix Them
Amplitude cohort syncs can batch large numbers of users in a single webhook payload when a new cohort definition is first activated and all qualifying users are included in the initial sync, causing your middleware to receive thousands of user IDs simultaneously that exhaust Twilio's per-second throughput limit. Implement a queue-based SMS dispatch in your middleware that processes Amplitude cohort users at a controlled rate of no more than one Twilio API call per second per phone number, and use a Twilio Messaging Service with sender pooling for bulk sends that need to complete within a reasonable time window. Amplitude's user_properties in the User Activity API response reflect the latest state but may not include historical properties that existed when the user first qualified for the cohort, causing the phone lookup to return null for users who had a phone property at cohort qualification time but have since had their profile updated without the phone. Store Amplitude user phone properties in your own database keyed by Amplitude user ID whenever the phone property is set in your application, and use your database as the primary phone lookup source with the Amplitude API as a fallback. Amplitude cohort sync webhooks do not include HMAC signatures for payload verification by default, making your endpoint vulnerable to spoofed cohort membership events that could trigger unauthorized SMS. Add a Bearer token to the webhook destination URL as a query parameter in Amplitude's destination configuration and validate it in your middleware, or restrict the endpoint to Amplitude's known source IP ranges.
How to Get More from This Integration
Build a behavioral trigger SMS system by creating multiple Amplitude cohorts for distinct moments in the user journey such as Reached Feature Limit, Invited Team Member, Connected Integration, and syncing each cohort to separate middleware webhook handlers that dispatch cohort-specific SMS with personalized content relevant to the user's current product context. Measure SMS lift on activation by comparing Amplitude activation funnel completion rates between users who received a Twilio SMS at a specific funnel step and users in a control group who did not, using Amplitude's A/B testing framework or a manual holdout cohort to attribute incremental activation improvement to the SMS touchpoint. Create a churn prediction SMS by building an Amplitude predictive cohort using Amplitude's machine learning churn prediction feature, syncing the high-churn-risk cohort to your Twilio middleware, and dispatching a retention-focused SMS with a personalized offer before the user churns, measured by comparing 30-day retention rates between the SMS-treated cohort and the control group. Add reply-based cohort updates by configuring your Twilio inbound number webhook to receive SMS replies, looking up the Amplitude user ID from the reply's phone number in your database, and calling the Amplitude Identify API to set a user property such as SMS Replied equal to true, enabling Amplitude to create new cohorts and funnel steps based on SMS engagement without manual data exports.
Conclusion
Amplitude and Twilio together let you act on product behavioral insights with targeted SMS that reaches the right user at the right moment in their journey, measured and iterated within the same analytics platform. Contact Telphi Consulting to build and deploy your Amplitude-driven Twilio SMS workflows.
Ready to Transform Your Business Communications?
Get a free consultation with our VoIP experts and discover how we can help you save costs, improve efficiency, and scale your business.
Comments (0)
Join the discussion and share your thoughts (AI-moderated for quality)
Be the first to comment
No comments yet. Share your thoughts below.