The concept of sponsorships is often confused and intermingled with advertising in the online world. In reality, sponsorships are a different vehicle than traditional display or video advertising and as a result have different objectives for the advertiser and different intended effects on the consumer. The Interactive Advertising Bureau (IAB) distinguishes sponsorships from advertising as the following:
In line with the definitions above, a complete site takeover of the NY Times home page by a brand like Coke (that includes a complete buyout of the ad inventory on the page) will be considered a sponsorship. The intent is for Coke to have a stronger brand association with NY Times, which cannot be achieved by the purchase of a simple ad unit.
With their unique nature, sponsorships can pose several issues for publishers:
Sponsorship placements are not standardized by the IAB
The assumption with sponsorships is that advertisers want to create a truly unique and custom experience on a publisher website or mobile app. While the desire for customization is largely true, there is still a huge demand among advertisers for some standardized sponsorship placements on websites (e.g. page skin, media player skin etc). For this reason, publishers such as ESPN (http://espncms.com/index3.aspx?id=249) and Washington Post (http://advertising.washingtonpost.com/index.php/solutions/page/sponsorships) publish their sponsorship specifications on their website, so the advertiser can pick the one that they want. This standardization enables faster adoption of sponsorships and increase in revenue for the publishers.
The custom nature of sponsorships puts strain on the development organization to get them live and running. Unlike traditional advertising, where the ads are remotely served by an ad platform and does require any incremental development work on the publisher end; sponsorships are for the most part implemented as changes on the publisher site. This requires the publisher development team to be involved every time a sponsorship is created or updated. As a result, sponsorships require a longer lead-time and the allocation of scarce development resources.
Publishers have a hard time calculating the ROI, inhibiting further sponsorships. Implementing a sponsorship requires the creative design, engineering, ad operations and marketing organizations on the publisher side to be involved. Given the amount of staff needed to accommodate these sponsorships, the publisher is often at a loss to calculate the ROI on the sponsorship. Therefore, the publisher does not really have the incentive to create additional sponsorships. Similarly, advertisers don’t have a discrete ROI metric to gauge the impact of their sponsorship outside of traditional reach and view metrics.
Standard IAB Ad units are easier to sell; ad sales know how to sell them; brands know how to buy them. Standardization of IAB ad units have enabled publisher ad sales to easily sell this inventory on their sites, either directly or via ad networks since advertisers know exactly what they are buying. This is not the case with sponsorships; the custom nature of sponsorships implies that the publisher has to engage in a conversation with a potential advertiser to explain the nature of the digital sponsorship, the creative placement etc. As mentioned above, sites such as ESPN and Washington Post have attempted to standardize these placements and in some ways define a standard for their own site.
Cisco Eos and Sponsorships
With its focus on delivering high-value, brand experiences, the creation of digital sponsorships on Cisco Eos websites is greatly simplified by the flexible site customization tools and the separation of the presentation and and application layers. Publishers can leverage Cisco Eos to create and manage digital sponsorships without disrupting the content experience, or day-to-day operations of their websites.
Case Study – Variety Screenings 2010
In a recent implementation, Variety Magazine created an Eos-powered web site to host video content around their Variety Screening Series 2010 (cisco.varietyscreeningseries.com). To enhance the value of the sponsorship of the physical movie screening, Variety enabled three different digital sponsorships (site takeovers) on the home page – Dell, Altoids and West Hollywood Tourism Bureau.
Dell Takeover of the Variety Screenings 2010 Site
Altoids Takeover of the Variety Screenings 2010 Site
Publisher was able to enable three different sponsored versions of the site with rotation of the versions, without making any code changes to the site. The sponsorships were de-coupled from an implementation standpoint from the actual site.
Following are the key benefits of using Cisco Eos to enable digital sponsorships.
o The site customization tools enable the publisher to create a sponsored version of the site without impacting the live site and without having to make any code changes. Cisco Eos’ versioning capabilities enable the publisher and the advertiser to review the sponsorship site and when ready, make the sponsored site live.
o Cisco Eos streamlines the process of creating digital sponsorships on a publisher site and turns it more into a creative exercise as opposed to an engineering task.
NOTE: The Variety Screening Series site only implemented site takeovers as a type of sponsorship on the publisher website. However, Cisco Eos is agnostic of the specific type of sponsorship and provides the same flexibility to implement other types of sponsorship (such as player skinning, specific page skinning, module attributions to a brand etc).
Using the flexible design and customization features in Cisco Eos make it easier and more efficient for publishers to offer sponsorships as part of their digital inventory. This empowers them to build more sponsorships more often thereby increasing revenue and reducing costs.