Tealium is excited to announce that we recently won the 2020 Khoros Community award in the category of All-Ways Connected. We flexed our integration muscles to show how using Tealium on Tealium can improve the customer experience.
Tealium provides an HTTP API endpoint for collecting event data from any location. This means that you can collect data from events that happen in your app or, in the case of Alexa, events that happen in a cloud provider. This example shows an AWS Lambda function used for an Alexa skill that tracks usage of that Alexa skill. Alexa developer tools allow you to create the Lambda function without the traditional AWS setup and permissions.
We, as the greater Tealium Education Training team, frequently get questions regarding our certification process. I will say that, while the path to certification is (intentionally) a challenge, our team is here to help you along the way by providing top notch training and helpful resources along the way. In this post, learn how to become Tealium Product certified.
It’s June! Six months into a year that feels like it has seen brighter days. As always, the Tealium Recruiting team is moving forward - we’ve made several key hires with more on the way and making progress on various initiatives slated for 2020. Nevertheless, it has been impossible to ignore the collective fear and uncertainty we all face in the time of Covid-19.
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).
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.
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.
Implementing the Tealium Universal Tag (utag.js) on your website isn't rocket science, but it does require a fair amount of pre-planning and requirements gathering. We have a whole team of implementation specialists dedicated to guiding customers through this initial process. It's a non-trivial amount of work to get a robust implementation deployed to your production site. Which is why it's worth thinking about your long-term strategy for maintaining that implementation.