Google working to target iPhone ad marketAdvertisers have reported that Google is working to build customized ad presentation options that target the iPhone, in recognition of Apple's market power among mobile web users.
A report in Adweek notes that "Google has presented a new option to show different ads in response to searches made from iPhones" in meetings with ad agencies. Although the company would not confirm the plans publicly, it did report that such plans have been "under consideration."
While systems to incorporate advertising support within iPhone apps are already common and ad networks targeting the iPhone's browser, including JumpTap and AdMob, already exist, Google's entry into the iPhone market is significant.
Google maintains a dominant lock on Internet advertising that even Microsoft has been stymied to challenge. It also reflects Google's view of the significance of the iPhone market, in much the same way as Microsoft's interest in partnering with Apple to provide Exchange Server support on the iPhone does. Both Google and Microsoft own their own competing mobile platforms.
The iPhone is unique in that it presents a standard desktop web experience as opposed to a mobile centric view by default. Many mobile phones present a simplified version of web pages using technologies such as WAP or Japan's imode mobile web.
Google hopes to offer advertisers the ability to target the roughly ten million iPhones in use with ads that present mobile users with options to access customized options, including direct links to phone support or iPhone-optimized web apps.
Adweek cited a report in the New York Times from January that named the iPhone the top source of Google's web traffic.
On Topic: iPhone
- TSMC reportedly sole supplier of next-gen 'iPhone 7' A-series chip
- iPhone controlled 40% of US smartphone market in 2015, data shows
- System outage prevents adding Visa cards to Apple Pay
- Proposed bill would ban US states from mandating backdoors in encryption
- Lawfirm considers suit over iPhone's Touch ID-connected 'Error 53'