Today’s column is written by Steve Sullivan, VP, Digital Supply Chain Solutions, IAB.
In the 1991 Australian film Proof, Hugo Weaving plays a blind photographer named Martin, who must rely on his other senses to determine how the world around him appears. In the film, he hires a trusted third party, Andy (played by Russell Crowe), to describe for him the contents of his own photographs so he can have “proof” that what he experienced was actually there.
Marketers seeking to allocate more of their budget to digital advertising are a lot like Martin. They have limited senses that can verify the value of the goods for which they pay. This is less of a problem when the goods are premium and the partnerships are stable and highly trusted. However, the increased use of networks and exchanges has intensified advertisers’ need for their own proofs.
They need Russell Crowe’s Andy.
In order to provide the industry with its own “Andy,” the IAB is assembling an influential working group consisting of member companies with an interest in the ability to safely enable communication between an ad and the page. The goal of this group is to develop and present a set of standard protocols that any agency ad server could implement to address the proofs of viewability advertisers desire, in a manner that protects the contents of the page.
It is as if Andy can see the content of some photos, but not others.
The simplest solution to this problem is to remove the barrier represented by the iFrame. This is actually a risky proposition, because, in addition to being a handy container for ads, the iFrame is also responsible for securing a trust boundary. A trust boundary is like the walls of your house. Some people, family members and very close friends or partners, have unrestricted access to your house because they are trusted. However, no matter how much you love pizza, you are never going to give the delivery guy a key to your front door.
Similar to your home, the iFrame can be opened to allow trusted parties access to what is on the other side without opening it indiscriminately to just anyone. A better solution is for the industry to develop a standardized safe iFrame. Safe iFrames use an Application Programming Interface (API) to enable secure communication across the trust boundary of a cross-domain iFrame. What makes this communication secure is the simple fact that it is limited. The API exposes a specific set of properties or functions the ad can use to determine its viewable state without providing unfettered access to the page content.
In order to achieve broad industry adoption, the safe iFrame API must be implemented by trusted third parties who have already a relationship with the site on which ads are served. This would be any outfit playing the role of agency ad server (sometimes referred to as Third Party Ad Server). Despite the name, these organizations act as neutral agents when it comes to the implementation of the safe iFrame API. Their role is to maintain a secure pathway (the API) through which the ad can gather only the information needed by the advertiser to determine viewability.
Broad industry adoption of safe iFrames is an important step for the interactive media landscape and one we plan on exploring even further at the upcoming IAB Ad Operations Summit on November 7 in New York City.
Safe iFrames are the online advertising industry’s Russell Crowe. With a trusted partner, like Russell’s Andy, safely describing the state of the world around their ads, advertisers will have the chance to see new metrics, obtain new insights and more accurately measure an ad campaign’s success. Without safe iFrames, advertisers will be left blind, most often guessing whether their ad was actually viewed by the consumer.