StreamSets DataOps Platform vs. Tealium Customer Data Hub

Majorly for all Batch and Streaming Scenarios we are designing StreamSets pipelines, few best suited and tried out use cases below : 1. JDBC to ADLS data transfer based on source refresh frequency. 2. Kafka to GCS. 3. Kafka to Azure Event. 4. Hub HDFS to ADLS data transfer. 5. Schema generation to generate Avro. The easy to design Canvas, Scheduling Jobs, Fragment creation and utilization, an inbuilt wide range of Stage availability makes it an even more favorable tool for me to design data engineering pipelines.

Incentivized

For more suited, I'll say highly regulated industry around data like healthcare, insurance, finance, where Tealium can be very helpful and for clients that don't have much different channels where they interact with their clients. So companies that only sell on internet and are a small company, I can see Tealium being the best usage for these clients, for these companies.

Incentivized

• A easy to use canvas to create Data Engineering Pipeline.
• A wide range of available Stages ie. Sources, Processors, Executors, and Destinations.
• Supports both Batch and Streaming Pipelines.
• Scheduling is way easier than cron.
• Integration with Key-Vaults for Secrets Fetching.

Incentivized

• Simple tag management that is tough to beat. So many solutions that are incredibly simple to setup and gather data for.
• Security around the data is key and Tealium excels in this area.
• The speed impact of the tag setup is key to optimizing and allowing our web properties to run more effectively, which is a better experience for the end user.

Incentivized

• Monitoring/Visualization can be improvised and enhanced a lot (e.g. to monitor a Job to see what happened 7 days back with data transfer).
• The logging mechanism can be simplified (Logs can be filtered with "ERROR", "DEBUG", "ALL" etc but still takes some time to get familiar for understanding).
• Auto Scalability for heavy load transfer (Taking much time for >5 million record transfer from JDBC to ADLS destination in Avro file transfer).
• There should be a concept of creating Global variables which is missing.

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

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

Tealium iQ Tag Management System does exactly what it is intended for, it manages vendortags. Changes can be made to websites and apps in minutes. The frontend is well structured, updates are easy to carry out, and Tealium support is available at all times.

Incentivized

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

Incentivized

Sometimes publishing can take longer than expected

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

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

StreamSets is a one-stop solution to design Data engineering Pipelines and doesn't require deep Programming knowledge, It's so user-friendly that anyone in Team can contribute to the Idea of pipeline design. In Hadoop One has to be programming proficient to use its various components like Hive, HDFS, Kafka, etc but in StreamSets all these stages are built-in and ready to use with minor configuration.

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

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

Incentivized

Never had an issue, scales as we use it.

Incentivized

Very easy to work with and relatively cost effective

Incentivized

• Simplified Improvised Overall data ingestion and Integration Process.
• Support to various Hetrogenous Source systems like RDBMS< Kafka, Salesforce, Key Vault.
• Secure, easy to launch Integration tool.

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