Author: Alwin Viereck, Head of Programmatic Advertising and Ad Management, United Internet Media
In my last blog post, I outlined the challenges to maintain identity in a programmatic first ecosystem and in this blog I will cover what building blocks for solutions exist. There is, in my opinion, currently five key areas of work:
For this blog, I will focus on the first two.
As we understood, IDs are as good as their survival (=persistence/storage time) in the ecosystem they are maintained in, their interoperability (multi-device capability) and their pervasiveness/scalability (can everybody generate or read/match them) they offer. For clarity it is important to cluster the existing solutions. In general, the solutions are:
Partial market overview:
Based on different types of identifiers mentioned, the advertising industry has started to develop advertising ID initiatives such as the IAB DigiTrust or the Advertising ID Consortium to define frameworks with the aim to be used throughout the programmatic landscape for “unification”. In this context vendor specific solutions such as ID5 or TradeDesk (Unified ID) have also started to gain ground.
Beyond that, login alliances such as netID or verimi progress as alternatives market players with logins such as Google or Facebook, for the programmatic advertising ecosystem as persistent, not cookie reliant solutions for unified identity frameworks.
In case these frameworks manage to gain scale, they will bridge the loss of identify as we face it today and lead us to a real post cookie era solution landscape.
The supply side has widely started to use prebid as a standard header bidding solution. A very interesting feature called the User ID Module has been released by prebid.org with its version prebidJS 2.10. Quotation: The User ID module supports multiple ways of establishing pseudonymous IDs for users, which is an important way of increasing the value of header bidding. Instead of having several exchanges sync IDs with dozens of demand sources, a publisher can choose to integrate with one of these ID schemes […]”. This development will force the standardisation of supply side vendor connectors to transfer “unified” identifiers into the programmatic ecosystem.
You may have asked yourself how server-to-server bidding is connected with persistent identity. Well, the availability of persistent identity provides a dramatic change in the way bidding is executed. While today the vast majority of bidding is client-side, a reliable identifier will provide us with the bases of going server-side with the bidding process.
Google with EBDA (Exchange Bidding Dynamic Allocation) and Amazon with TAM (Transparent Ad Marketplace) have shown ground for server-to-server solutions. A widely accepted persistent identifier for the open internet would mean, that prebid server or other alternatives to given walled garden solutions can come into place.
With a move to the server-side, the majority of third party scripts involved in bidding, tracking and profiling would disappear from websites resulting in an increase of usability due to reduction of loading times, a dramatic reduction of timeouts due to real parallelisation/threading on server-side, reduction of latency problems caused by a high number of script calls used for bidding and cookies syncing and finally also an independence of the header bidding process from browser gatekeeping.
In a persistent ID driven programmatic world, which runs bidding processes on the server-side, we are left with ad delivery to be solved properly in the future to avoid bad user experience, ad blocking or other gatekeeping through browsers we face. That’s where the third building block for solutions “first party ad delivery” comes into play. But this might be a topic for a later post.