So Why Aren’t You Supporting SafeFrame?
Last year, IAB issued an industry-wide call to replace all iFrames used in digital advertising with SafeFrames. We did so, fully understanding the enormity of the work that would be required of publishers to re-tag an estimated 60% of the Internetnot a trivial task. SafeFrame is a new ad serving technology standard developed to enhance in-vivo communication between digital ads and the publisher pages where those ads are displayed, all while maintaining strict security controls. As we approach the one year anniversary of SafeFrame’s release (March 19th) I think it’s fair to state that, while industry adoption is chugging along, it could be better.
One notable early adopter of SafeFrame is Yahoo. Today a majority of Yahoo’s display advertising inventory is served in SafeFrames (that’s billions of impressions every day!) – and Yahoo is actively pushing towards a 100% deployment goal. To be fair to those still in the process of implementing SafeFrame, Yahoo co-led the industry initiative, along with Microsoft and IAB, to make SafeFrame an advertising standard. Nevertheless, to call Yahoo’s contribution to SafeFrame notable is really an understatement.
Since its release last year, a working group at IAB has been focused on tearing down barriers to SafeFrame adoption. The most cited of which has been the need for support by rich media vendorsan understandable barrier to those who comprehend the technical underpinnings of the digital supply chain. We realized early on that we were in a chicken-and-egg conundrum with respect to SafeFrame adoptionwithout dedicated support from rich media vendors, who package ad creative for trafficking across a variety of publisher sites, neither advertisers nor publishers would be particularly incented to adopt SafeFrame.
Yahoo stepped up to help the industry address the SafeFrame adoption challenge. Yahoo worked closely with top rich media vendors to get SafeFrame off the sidelines and into production environments globally. As a result of Yahoo’s leadership and efforts, 23 rich media vendors now support SafeFrame (see list of vendors.)
With this significant barrier removed, it’s time for those who have been on the sidelines to take action. And with Google’s update to DFP due to support SafeFrame in the first half of 2014, there should be no doubt that this new technology standard is here to stay.
Finally, what most people don’t know about SafeFrame: it’s not just about viewable impressions. Sure, SafeFrame provides publishers, marketers and third-party ad verification services a simple, transparent, standards-based and cost-free API for determining an ad’s viewability state. And with all the deserved attention 3MS (Making Measurement Make Sense) has brought to viewable this past year, it’s no wonder that folks have honed in on this key feature of SafeFrame. So, while SafeFrame helps to solve for viewability measurement, it can do so much more.
Think of SafeFrame as an extensible technology platform that can be used to solve for many issues confronting our digital supply chain. To name a few, SafeFrame already supports programmatic sale of expanding rich media, sharing of metadata, enhanced consumer security and privacy controls, enhanced publisher security and the prevention of cookie bombing. With more SafeFrame features currently in the development pipeline, we see SafeFrame as a base standard that will be extended in ways we have yet to conceive. Simply stated, SafeFrame is the new container tag for digital advertising: it solves many of the digital supply chain issues we face today as digital advertisers and publishers, and is extensible to solve tomorrow’s problems too.
To learn more about why your company should be supporting SafeFrame, we’ve made it simple, with easy to understand educational materials for the marketplace, including an educational video, a feature comparison chart of ad trafficking methods, and an extensive FAQ.
For questions involving SafeFrame or how to get involved with SafeFrame initiatives at IAB please reach out to Alan Turransky.