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).
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.
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.
Today we want to shine our Tealium Expert Spotlight on Damian Savvides! Damian was recently hand-selected to join the Expert group for his contribution to solutions in the iQ Tag Management discussion forum. Keep reading below to learn more about Damian, then visit his profile and select the "Send a message" button to connect with him directly.
The Tealium Learning Center (TLC) is geared towards helping you get the most out of your Tealium products. The community is comprised of all levels of users: from first-timers to experts, and even Tealium employees. We encourage you to explore conversations and ideas, sharing information and best practices for the benefit of the entire community.
As we all know, although the functionality of Load Rules is similar to Conditions, we can't manage extensions using Load Rules or use those Load Rules to replace Extension Conditions. Load Rules are always in the same location in the UI and can be applied more than once which makes them easy to maintain. They also have the bonus ability to manage timeframes as conditions as well. We often have the problem of needing to maintain multiple extensions with the same Conditions which could be leveraged by a Load Rule instead. Here is my take on how we can take advantage of Load Rules within Extensions, and perhaps simplify some implementation and maintenance.