Tealium Customer Data Hub vs. Twilio

Well suited: Any company that has a variety of data interspersed across multiple systems and is trying to get a more unified understanding of their customer profile—that enriched customer view of having all these disparate data sources and wanting to bring them together in a relatively seamless manner, and then having that more nuanced understanding of the entirety of the customer and being able to action off of it. Which again, I feel like is a core marketing use case.

Incentivized

I found Twilio to be excellent and very easy to use for a programmer in all aspects related to voice, SMS, and other features utilizing their API. I found the node client to be excellent and helpful. We previously used the Apex client for Salesforce before it was discontinued. Although we try not to use Twilio from Apex anymore, using that client was easier than implementing our own.

Incentivized

• Activation in real time - it's really good and you can literally see the information being activated in all other technologies that my clients use, like TikTok, Facebook, Google, et cetera. At the time that a client arrives on your website, you have instant data to enrich the profiles and activate on this channel. So this is really good and it's something that Tealium give us the control in order to do that.
• The other thing is that you have the power to choose what data you want to collect and what data you do not want to collect. Tealium is particularly very good on doing that.

Incentivized

• Easy to see my team in one place, when they log in and out and what call status they are in.
• Twilio is a simple, user friendly way to log in and out of work activities.
• Excellent services and support.
• The omnichannel feature which allows agents to get request from all channels.

Incentivized

• Audiences—don't they technically exist in Tealium? They are just streamed—no count, no backfill, etc.
• Working backward to identify issues involves lots of clicking in the UI, going from audience to audience attribute, badge to event attribute, and so on.
• You have to wait for a Real-Time event to see the payload. There is no sample or other option.

Incentivized

• Segment’s email identifier is case-sensitive, which is ridiculous because emails themselves are not case-sensitive. This means that if I send a capitalized email address in an identify call, it will create a duplicate user rather than matching it with the lowercase email. I think this is a technical oversight that should be corrected.
• I’d like to see more information about the eventual transition of existing Frontline customers to Twilio Flex
• I’d like to see some integrations between Twilio Studio and OpenAI or another open source LLM to provide automated responses, if this hasn’t been done already
• I would like to be able to drag and move the actual lines connecting the steps in Twilio Studio, sometimes mine can get pretty messy
• I think a Bug Report form would be beneficial for developers

Incentivized

I already know that my company has no plans to discontinue use of Tealium. We are heavily reliant on it due to a huge number of product teams and developers we would have to work with to place tags across many pages. Tealium is already there on the pages, and our application/product teams are familiar with how to integrate it. It is just the simplest way to ensure that new data requirements are implemented in a timely manner.

Incentivized

Unless we can get this handled quickly -- less than 1 week -- we will likely switch to another provider who, in my opinion, we'll have to spend close to $3,000 in development time to build a new integration for texting. Our clients need texting and I feel Twilio has failed us miserably.

Incentivized

Once you understand how it works and how to implement things, it is a dream and very user friendly. There is the initial learning curve but there are oceans of helpers available to you to help you bridge that initial gap and get going. Take the time to learn it up front and you will never have any problems. And support is great and available to answer questions

Incentivized

Twilio has well documented APIs and examples. There are several tutorials, videos and Q&As regarding their services. So, usability is very good. I must say that advanced knowledge of telephony, API/Programming and error-handling is essential to make good use of Twilio. It's not just plug-and-play unless you are integrated with a system that has all of the programming built for it.

Incentivized

It's been flawless as far as I am concerned.

Incentivized

Sometimes publishing can take longer than expected

Incentivized

Twilio executes what it is designed to do: send SMS messages at scale while providing very good deliverability. I believe that Twilio is very good at what we use for adding SMS messages to our comms strategy. We can see those messages get opened and replied to, which is exactly what we are looking to achieve.

Incentivized

The support team often is so quick to respond and so helpful when it comes to working with the needs of my clients and being able to resolve potential shortcomings or technical issues or surrounding the tool. There have been times more recently that I’ve gotten more generic service rather than the tailored experience that I have come to expect.

Incentivized

I have not had to communicate with Twilio support in the last 3 years but my past experience with them has been very positive. They replied to my previous requests promptly and kept me well informed to resolve my inquiries. With their documentation that's available, I hardly imagine why anyone would need to contact support since it's all there in a concise and easy to understand format. It would probably take you longer to type out a support ticket than to just open their doc websites.

Incentivized

Did what we needed to onboard us onto the platform

Incentivized

Implementation had some bumps in the road and it was new for all of us, but for the most part, it was easier than many other implementations we've done with other technologies.

Incentivized

The developer APIs and SDKs are super easy to follow.

Incentivized

Tealium Customer Data Hub can do it all in one. Whereas, I think by using multiple Tealium Customer Data Hubs, we can utilize what each tool is really good at. In an ideal world, we'd like to use Tealium Customer Data Hub for everything, but one thing that we struggle with is Audience Segmentation, and we are looking for a one touch solution, without a lot of the work since the data is already there.

Incentivized

We evaluated many fundraising-based text-to-give programs and found the subscriptions prohibitively expensive for our small scale and uncertain first few years of development. While we may be willing to invest that kind of money after discovering how things work, we're happy with Twilio now and have no desire to start over.

Incentivized

Like anything it could be cheaper but we still feel we get value from it.

Incentivized

Being in South Africa, direct local currency support would be nice

Incentivized

Never had an issue, scales as we use it.

Incentivized

Very easy to work with and relatively cost effective

Incentivized

• There has been a near immeasurable return on customer data and improvement of our quality for our physical products due to be in tune with the customer. This has changed our way of doing things for the better to gain a better flow and overall workplace experience.
• A negative is that Tealium AudienceStream becomes harder to manuever and use data analytics for when a database has been existing for a fairly large amount of time. It goes from an agile ship to a huge vessel that takes many components to be able to move.

Incentivized

• It helps drive the adoption of multi-factor authentication by making second-factor authentication quick and easy.
• Decreases the number of times a user spends migrating to a new device from an old one.
• Enables easy access to second-factors of authentication by offering multi-device support, making multi-factor authentication painless.

Incentivized