A robust tool to handle user information
July 15, 2022

A robust tool to handle user information

Anonymous | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User

Software Version

Business

Overall Satisfaction with Twilio Segment

Twilio Segment is really useful when: - You have multiple services or microservices interacting with user data (names, personal preferences, etc) - You need to handle at scale Personal Information, GDPR, privacy, etc. - You want to create a pipeline of events happening in your applications and distribute them between other vendors or data tools - Managing and organizing multiple lead sources (Facebook leads, Unbounce, google ads, etc)
  • Handling PII information and GDPR
  • Managing multiple user data sources and making it easy to deduplicate
  • Building event pipelines across apps and integrations
  • Creating events using a UI or something like Heap's autocapture
  • Retrieving user data with frontend libraries
  • Rules for user identification and deduplication
  • Merging and deduplicating user info
  • Events planning and pipelines
  • Distributing information to other vendors, apps
  • Better marketing budget allocation by facilitating attribution
  • Centralized user information
  • Easiness to distribute user information and user events across multiple destinations

Do you think Twilio Segment delivers good value for the price?

Not sure

Are you happy with Twilio Segment's feature set?

Yes

Did Twilio Segment live up to sales and marketing promises?

Yes

Did implementation of Twilio Segment go as expected?

No

Would you buy Twilio Segment again?

Yes

Best suited: - Merging emails coming from: Facebook leads forms, Unbounce or landing pages forms, Google forms, any other kind of lead generation tool and bundling all that information together for a single user "profile". - Passing events generated in multiple applications by the same user (product selected in web, product discarded in cart, etc) and delivering those events into other applications (like a CRM) Less appropriate: - Reading/updating data directly from segment from a frontend application