I wrote an earlier post called “In a world without cookies” which was my early response to the default setting in Apple’s Safari browser. This issue has expanded such that we’ll see even fewer cookies out there, so I’m going to bring a little more light to the issue of privacy and privacy compliance in mobile, tablet and the desktop.
For the purposes of addressing privacy, the physicality of the device, whether it is a tablet, phone, or a desktop computer, can be mostly ignored. The real technical distinctions with regard to privacy are between browsers and apps. It’s also important to understand the need for advertising companies to maintain compliance with organizations like the NAI and initiatives like the OAB. Together, the OAB and NAI dictate opt-out rules that online advertising companies must adhere to.
3rd Party Cookie Blocking
Apple’s Safari browser has a default set to block third party cookies. Firefox will soon have a similar default setting.
The most prolific obstacle in privacy and compliance is probably a result of Apple’s move to disable 3rd party cookies by default in their Safari browser. This is not just the Safari that ships on your iPad or iPhone, but all Safari browser installs, including that one on everyone’s beloved Windows machine. Now, the team behind Mozilla’s Firefox browser has pledged to do the same. Blocking by default causes two problems: advertising companies can’t do simple things like frequency cap using a cookie, and there’s no way to determine the user’s actual intent. If the default setting was to allow 3rd party cookies, a user’s intent would be crystal clear if it was set to block. Read more
When evaluating advertising options on mobile devices, it is important to consider the screen size as well as whether the content is viewed in mobile web or a native mobile application. Content that is viewed in a browser is often suboptimal for advertising. When presented with a standard un-optimized web page the phone’s browser will shrink the content to fit the width of the display. This has the unfortunate side effect of also shrinking ads, often until they’re very small. In this scenario, advertisers are not getting their money’s worth, as their ads are often too small to see.
To successfully advertise on web pages displayed on a mobile phone a site’s layout must be mobile optimized. This single column of content optimized for a phone’s screen lends itself to an advertising unit that spans the screen unobstructed. While hardly anyone would think that these small banner units that span the screen are the answer to mobile advertising needs, this is at least a place to start.
In an attempt to expand the advertising opportunities on mobile, the IAB is working with advertisers and publishers to create new, more engaging ad units for mobile. These units have names like “Push” and “Slider”. They are initially inconspicuous on the page, but can take over the entire screen to create a more immersive experience. Adhesion banners stay in the same place on the screen, remaining in view throughout the user’s session. Creative thinking like this has led to ad units that expand to the limits of the screen of the device. Rather than being little boxes on the screen, these ad units use the full dimensions of the device to be more immersive and engaging.
Content viewed in mobile apps have distinct challenges from their web counterparts. These challenges are common to phones and tablets. The most prominent challenge is the requirement of the SDK (or Software Development Kit). SDKs are sets of code that an application developer integrates into their app to allow mobile ads to run within their app. Mobile inventory buyers, generally, develop SDKs. Their code enables the application to call the buyer’s ad server to get ads and render them properly. For each demand source that the application developer partners with, there is likely a new SDK integration. The problem is that all these SDKs have a distinct set of instructions to perform a fairly common set of tasks. The proliferation of distinct SDKs has resulted in more fragmentation in the market.
There are still stories of app developers integrating up to seven different SDKs to manage the need for competitive demand for inventory. Managing multiple SDKs can be problematic. There is non-trivial operational and technical overhead of integrating additional code to the application. Demand partners have their own development roadmaps and update their SDKs on their schedule. Each time an SDK is updated the application developer needs to re-integrate the code and re-submit the app for approval to iTunes or Google Play.
It’s not all gloom and doom in the app world though. The IAB has recently made efforts to normalize the SDK interactions to reduce the learning curve for integrating different SDKs. It introduced the Mobile Rich Media Ad Interface Definitions, or MRAID. MRAID is an effort to create a common set of standards. Indeed, many mobile advertising companies now offer MRAID compliant creatives. As support for MRAID grows we all can be hopeful that these woes will subside.
Through the use of SDKs, mobile apps are able to make use of functionality that is native to mobile devices to deliver a more engaging advertising experience. Companies such as InMobi or Celtra offer a rich advertising experience to the user instead of the standard still-image ad (with click-through) that is very prominent in online display advertising. The SDK opens the door for highly interactive and engaging ads, which have actually been well received by users.
Tablet inventory, whether accessed through an app or web, comes with some interesting opportunities. First among them is the larger screen offering the potential for larger ad formats. There are several tablet-specific formats gaining traction in the market. Some are custom for a specific application. Others, like the Filmstrip from IAB’s rising stars, are approaching a level of standardization that can be leveraged by application developers and the currently rare tablet-optimized web.
The impact of these challenges depends on the user experience that you design for your mobile users. You should decide what the appropriate experience is for your content type, and then deal with the relevant advertising issues that arise. Formatting and building content specifically for mobile is the first step toward monetizing content. Have you had issues integrating SDKs with your mobile apps?
As I covered in the first blog post, mobile presents a tremendous market opportunity for publishers. A large and growing share of traffic comes from mobile devices. According to comScore, 13.3% of pageviews came from mobile devices in August.
On a smartphone there are basically two ways to go online: web or apps. Let’s start with apps. In contrast to mobile web, apps have been built from the ground up for smartphones. Content has rendered into an experience that doesn’t require a mouse and/or keyboard. Additionally, apps normally don’t feel like a pared down or diminished version of their online display counterpart. Think about your favorite app – it’s likely that you’re playing a game, checking weather, interacting on a social network or looking for directions. These experiences seem natural on a smartphone app.
Apps vs Browser
In contrast to apps, using a browser on a smartphone to access a site’s “desktop experience” creates a number of challenges. When presented with a standard web page the smartphone’s browser will shrink the content to fit the width of the display. This has the unfortunate effect of making all of the content very small, forcing the user to pinch, zoom and swipe to see content.
In order to combat this effect, publishers create “mobile optimized” websites. These sites are built with the screen size limits in mind. They typically feature pared down versions of their online display (desktop) counterparts, and often put smaller versions of images in-line with text designed to take the full width of the smaller screen.
In contrast to a negative experience on a smartphone, a tablet has more in common with standard desktop experiences. Most standard web sites render just fine on tablets and even the ads can be seen. Users can view content on tablets with very little zooming and swiping. However, while the content renders mostly correct, tablets do share a challenge with their smartphone counterparts – the unique nature of touch navigation.
There are many resources online to guide you through the step-by-step process of optimizing your content for mobile devices. To get started it is important to recognize that mobile devices are navigated by touch, which is quite different than the mouse-driven, point-and-click navigation of the desktop world. Rather than clicks, you will design for taps; instead of scrolls you will design for drags and swipes. These are subtle differences that change the way that a user interacts with content. Button size becomes important. Drop down menus are harder to use. Anything that requires a hover is pretty much useless in a touch world.
Another thing to consider is the file size of your site. Since much of the content accessed via mobile devices will be downloaded over cellular rather than high-speed access via Wi-Fi, it is important to trim the fat and reduce that file size as much as possible. A final consideration is the absence of Flash in the mobile web world. Flash content will not render on iOS devices. Given the ubiquity of iPhones and iPads, this is an important issue to address. There are alternatives to Flash, such as HTML5, that deliver similar capabilities and work across all devices.
At the end of the day, these devices share many characteristics but what works on a smartphone won’t necessarily work on a tablet; and vice-versa. It’s important to examine these two device types independently to determine the best user experience for your content across these devices. They need to be evaluated in terms of screen-size and form factor for strategies across content. This goes from content to creative to analytics. Have you built a mobile optimized site? What challenges have you faced? Comment below for other readers and I’ll address questions in future posts.
Everyone recognizes that mobile advertising is a rapidly growing market. How fast is it growing? eMarketer has current year revenue estimates at $3.9 Billion. According to the Yankee Group mobile ad sales should nearly triple by 2016 to $10 Billion. I think this estimate is low given the acceleration in market growth we’ve experienced so far this year alone. Revised eMarketer numbers now indicate nearly 100% growth for 2012 over 2011. Further, eMarketer predicts that mobile will grow to over $23 Billion by 2016. This is much more consistent with Mary Meeker’s prediction of a $20 Billion mobile market.
Given this tremendous market opportunity, we have seen first-hand that numerous publishers are moving to mobile – building mobile applications, optimizing their web content and trying to figure out how to turn that mobile content into a dependable revenue stream. We are glad publishers are jumping in and are excited to be in the mobile space as well. However, we have also witnessed headwinds in this developing market and would like to use this blog to help publishers address these challenges.
The mobile display advertising space has some distinct challenges that fly in the face of the status quo of online display. These challenges conspire to make it more difficult for publishers to advertise across their mobile inventory. A primary complication is that there are three major operating systems (plus Blackberry), each with subtle differences that require research and technology to overcome. Let’s explore how each of these platforms differ.
Apple’s iPhones do not support Flash and ship with third party cookies disabled by default. The lack of Flash strongly affects the user experience and the ability to deliver Flash-based rich media creatives that render in online display (troublesome on iPad, where standard display ads are typically viewed with little loss of fidelity relative to their online counterparts). Additionally, the lack of third party cookies makes it difficult to perform simple audience targeting that we’ve grown accustomed to.
Microsoft’s Windows Phone 8 platform is touted as having twice as much HTML 5 support, but still lags behind Chrome (Android), Safari (iOS) and even Blackberry. We are hopeful that Windows Phone 8 will support HTML 5 to the point that publishers and advertisers can leverage the same mobile web ads across platforms. However, there is a possibility that a lack of full HTML 5 support will require custom ad units for this platform. On top of that, Windows Phone 8 may also ship with the new Do Not Track (DNT) flag turned on, severely limiting the ability for publishers to achieve higher rates through traditional tracking and targeting.
Google’s Android platform seems to be the most compliant to the needs of the industry. Android supports 3rd party cookies, DNT is disabled by default, device IDs are available in the app environment and it even supports Flash. Of course this all supports Google’s advertising business, but they’re nice enough to keep the platform open for a variety of complementary and competitive third parties. By creating an environment most closely resembling online display, Google has made it easier for publishers to incorporate Android to their mobile experiences.
Where does all of this fragmentation leave us? Many publishers have been successful in traversing this fragmented market. If you are new to mobile, it can be daunting to figure out where to start. A logical starting point is to figure out what mobile devices are most common among your audience and focus on building your mobile presence there (at least initially). That way you limit the number of challenges you have to deal with. Eventually you will have to accommodate users across a variety of devices and platforms, so working with a partner that is platform-agnostic is critical. Look for partners that have a history of ad serving across platforms and formats.
In this series of posts, I hope to help provide some insights to help publishers that are still trying to make sense of the market. What challenges do you face in mobile? What specifically would you like insight and tips on? Comment below and I’ll incorporate into the subsequent posts.
Apple has several sizes and shapes in their line of computers and iPods, but only one size and shape to their phone. Sure, you can get 3G or 3GS with a variety of storage onboard, but the device itself comes with the same processor, same graphics, same screen size, same camera, same ins and outs.
This same-ness has eased developer adoption to be sure. Having a single device to design for means there’s one stream of code, with some tinkering for backward compatibility. It’s also great for the accessory folks. A single physical shape means more consumers available per accessory.
There might be a problem with such a robust device running the iPhone OS. Folks who’ve purchased an iPad might not need the next iPhone. The iPad runs almost all the apps that the iPhone runs, and with the larger screen the apps are often far better. Owning an iPad means that users, like myself, could actually get by with a cheaper, run-of-the-mill mobile phone. Read more
iOS is still using the GD dark patterns to influence your choices. @AppleSupport, can you tell your folks to stop using dark patterns? If you have a recommendation, just make the recommendation. Don't trick people into tapping what you want them to tap. https://youtu.be/kxkrdLI6e6M