Third-party tags for online marketing solutions started out simply enough, but have grown from a few pixels to full-on data chaos. Here’s a brief look at how it happened and where we go from here:
Third-party tags were introduced in the 90s to help ad servers and analytics packages measure the effectiveness of online advertising and site usage. Tags work by requesting an invisible piece of content — often a transparent image file that is one pixel in size — from a third-party server, allowing the server to record basic data about the user’s visit to a website. As online marketing has expanded, every third-party service provider has created a tag to help collect the data needed to power its solution.
Third parties in control of data collection
Complex implementation of tag code
Updating tags requires a site build
Basic tag containers can’t handle complex tags
Most tag containers are not designed for universal deployment across all pages of a site
Page performance degrades as tag containers insert more third-party code onto a site
Piggybacking & Data Chaos
While basic tag containers have evolved to help site owners wrangle their tags, third-parties have needed their own mechanism for extending data collection beyond a single tag. As online display ad spending grew, ad networks chained together ad server tags in order to increase audience reach across multiple publisher sites. This chaining, often called “piggybacking,” allowed one tracking server to introduce tags for another tracking server, which could then in turn introduce tags for yet another tracking server, and so on. The ability to connect audiences across sites through piggybacking has allowed dramatically new ways of buying and selling advertising to emerge, and is at the heart of today’s real-time bidding systems and data exchanges.
Data chaos: Site owners have no visibility or control over the tags that third-parties piggyback
Piggybacking chains can add literally dozens of tag calls to a site
High-levels of data loss due to tag loading issues