Tealium is a data hub platform that processes events at a large scale. We've seen tremendous growth in the amount of incoming customer data, where a single account might receive up to 30k events per second. Each of those events is then processed through a real-time data pipeline that requires a massive event driven system. This has forced us to evaluate which message broker platform will serve us best in the long-term: RabbitMQ or Amazon Managed Streaming for Apache Kafka (Amazon MSK).
I've been working with Tealium products extensively and am the creator of the UDO Debugger extension for Chrome. Recently, I completely refactored the tool with a lot of cool features that I hope will help other analysts and developers who work with Tealium products.
Surely, you've run across great content in the TLC, information you want to keep handy or stay in the know with ongoing updates. To help you stay organized and in the loop about the latest TLC content, this tiny tip will review bookmarks and subscriptions.
Welcome to a spin-off of our TLC Tips series! The TLC Team is introducing tiny TLC Tips, or quick explanations on some of the most useful features in our community. This tiny tip is about Accepted Solutions.
The TLC is a "one-stop shop" for everything from product information, to becoming recognized as a Tealium Expert. You’ve come to the right place to learn about Tealium products and to find more ways to optimize their use! As you learn more, you can share your knowledge with the community. This gives back to other Tealium users, and it's fun to increase your recognition, too!
The community wants to shine its Expert Spotlight on @pmeyerdk, representing the EMEA region! We were delighted to see Peter recently published in the ConversionXL blog with a post about TiQ. Way to represent! Keep reading below to learn more about Peter, then visit his profile and select the Send a message button to connect with him directly.
Google decided with AMP HTML cache to copy the world's content to their own CDNs on google.com, effectively keeping visitors on the google.com domain even after clicking a Google search result. This creates an interesting analytics challenge when your visitors are viewing your content, but are still on google.com. And when that visitor clicks a link to eventually arrive on your original website, it becomes difficult to build an accurate visitor path report using traditional web analytics tools.
Since data is the foundation for the Tealium solution, setting up a consistent data layer is a vital first step for implementation. The data layer defines attributes about your website or mobile app, such as country code or page name, as well as important user behaviors to track, such as logins and purchases.