Risk
7/3/2012
01:54 PM
Connect Directly
LinkedIn
Twitter
Google+
RSS
E-Mail
50%
50%

Google Plans Button To Block Ads

Feature may put an end to ads that follow you across websites.

Google Nexus 7 Tablet: 10 Coolest Features
Google Nexus 7 Tablet: 10 Coolest Features
(click image for larger view and for slideshow)
Google said Monday it will soon provide users with a capability that has been available for years through third-party browser extensions: the ability to block ads.

Google characterizes this forthcoming feature--available in a few weeks--as a "mute this ad" button rather than an ad-blocking button.

Google's choice of words is imprecise. Muting generally refers to audio made inaudible; it can be applied to the visual realm, but muted colors remain present in a less vibrant shade, unlike muted sounds or muted ads.

Google's mute button, designated by an "[x]" in the upper right-hand corner of some Google Display Network ads, will affect ad visibility rather than audibility. Perhaps Google opted for more figurative terminology to avoid spooking its advertising customers with talk of ad blocking, while still appealing to its end users and regulators.

Google product manager Michael Aiello in a blog post cites ways in which Google has given users more control over the ads they see, such as YouTube's TrueView ad product, which allows users to skip video ads, and Google's Ads Preferences Manager, which allows users to edit advertising interest categories or to opt out of online ads, including remarketing done through the Google Display Network.

[ Google is also trying to turn down the volume on its legal woes. Read Google Proposes Remedies To EU Antitrust Woes. ]

Remarketing refers to the way that advertisers target website visitors based on a cookie file placed at a previously visited website. Google plans to begin deploying its "mute this ad" button on ads delivered via remarketing and interest categories. This will give Internet users the opportunity to silence unwanted ads that follow them from website to website.

Aiello says that the mute button has some limitations. "The muting is not a 100% guarantee you won't see that ad again as a consumer--for example, the same ad could be shown by a different ad company, or the marketer could run a separate campaign targeting specific Web content," he explains. "But we believe it's an early step in the right direction of giving users control over ads, while helping marketers and websites deliver ads that perform better."

Author and ad company entrepreneur John Battelle in a blog post said he was glad to see Google innovating in advertising, even if belatedly. One person commenting on Battelle's post observed that the subtext of Google's announcement was, "Please don't use ad-blockers, because you can choose which ad we will show you."

Here's Aiello's translation of that sentiment: "Online advertising underpins the Web and supports millions of businesses," he said. "It's already unique in the level of control it can offer users."

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-6335
Published: 2014-08-26
The Backup-Archive client in IBM Tivoli Storage Manager (TSM) for Space Management 5.x and 6.x before 6.2.5.3, 6.3.x before 6.3.2, 6.4.x before 6.4.2, and 7.1.x before 7.1.0.3 on Linux and AIX, and 5.x and 6.x before 6.1.5.6 on Solaris and HP-UX, does not preserve file permissions across backup and ...

CVE-2014-0480
Published: 2014-08-26
The core.urlresolvers.reverse function in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 does not properly validate URLs, which allows remote attackers to conduct phishing attacks via a // (slash slash) in a URL, which triggers a scheme-relative URL ...

CVE-2014-0481
Published: 2014-08-26
The default configuration for the file upload handling system in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 uses a sequential file name generation process when a file with a conflicting name is uploaded, which allows remote attackers to cause a d...

CVE-2014-0482
Published: 2014-08-26
The contrib.auth.middleware.RemoteUserMiddleware middleware in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3, when using the contrib.auth.backends.RemoteUserBackend backend, allows remote authenticated users to hijack web sessions via vectors relate...

CVE-2014-0483
Published: 2014-08-26
The administrative interface (contrib.admin) in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 does not check if a field represents a relationship between models, which allows remote authenticated users to obtain sensitive information via a to_field ...

Best of the Web
Dark Reading Radio
Listen Now The Best of the Rest of Black Hat: The Enterprise View
This episode of Dark Reading Radio looks at infosec security from the big enterprise POV with interviews featuring Ron Plesco, Cyber Investigations, Intelligence & Analytics at KPMG; and Chris Inglis & Chris Bell of Securonix.