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.
Tealium hosted 51 of San Diego's most ambitious coders this past weekend for a friendly competition and some stellar networking! After sessions with some of our in-house technical experts, attendees were set free to code and impress the judges with their presentations.
We invite the best and brightest to join us in San Diego for a friendly competition and the chance to win one of our many prizes. Tealium’s Game of Codes will run from August 17th through August 18th, with optional break outs for contestants and clients alike to learn more about the Tealium technology stack.
In my previous blog post, I covered how businesses use third-party cookies to identify users as they move across web sites. This practice is now being challenged by ITP 2.1 in Safari and by similar approaches in other browsers. I discussed two different workarounds that some vendors are using to combat the problem. But each workaround still has limitations, and this post is an overview of some other solutions we have seen our customers implement to maintain visitor identification for their website users.
This blog series explores the impact of data privacy regulation and third-party cookie blocking on data tracking techniques for anonymous and authenticated visitors on websites. The online advertising and marketing industry, that was built on a foundation of data collection, is now being challenged by new restrictions imposed by browsers to limit who and what data can be tracked.