Risk
9/19/2013
04:47 PM
Connect Directly
RSS
E-Mail
50%
50%

Google's Plan To Kill Cookies

Google proposes anonymous identifier for advertising, or AdID, to replace cookies used by third-party marketers. Google would benefit -- but would consumers?

Google Nexus 7, Chromecast: Visual Tour
Google Nexus 7, Chromecast: Visual Tour
(click image for larger view)
Google is floating a plan to cease tracking Internet users with cookies, which are bits of code stored in browsers that allow third-party advertising and marketing firms to track consumers' browsing habits.

Instead, Google is proposing a new system that would use an anonymous identifier for advertising -- or AdID -- to collect information on users, USA Today first reported. Advertisers and advertising networks that agreed to abide by Google's code of conduct -- which has yet to be detailed -- would then be given access to AdID. Theoretically, that code of conduct would enshrine some basic privacy protections for consumers, including the ability to opt out, or to assign different AdID policies to different sites, but any such details have yet to be released.

Asked to comment on the report, a Google spokeswoman emailed the following statement: "We believe that technological enhancements can improve users' security while ensuring the web remains economically viable. We and others have a number of concepts in this area, but they're all at very early stages."

[ Here's how Google is personalizing its answers to your questions: Google Search: 5 New Ways To Get More Personal. ]

Google reportedly plans to meet with consumer groups, government agencies, industry groups and anyone else with a stake in the $120 billion online-advertising industry, which Google dominates. In addition, according to Net Market Share, Google's Chrome browser also enjoys a 16% share of the browser market. Although less than IE (58%) and Firefox (19%), that still gives Google added leverage.

Advertisers, however, have responded in a lukewarm manner to Google's suggestion, because it would largely consolidate advertising power in the hands of Google, as well as Apple, which last year introduced a unique Apple Advertising Identifier for all iOS devices, together with prohibitions on developers or marketers using a device UDID to directly track users. "There could be concern in the industry about a system that shifts more of the benefits and control to operators like Google or Apple," eMarketer's Clark Fredricksen, who tracks the digital ad industry, told USA Today.

Previous
1 of 2
Next
Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest First  |  Threaded View
David F. Carr
50%
50%
David F. Carr,
User Rank: Apprentice
9/20/2013 | 1:55:15 PM
re: Google's Plan To Kill Cookies
I know they haven't released details, but any clue how this AdID code would be tracked, if not with a cookie? Would browsers have to build in support specific to tracking this other type of code?
Lorna Garey
50%
50%
Lorna Garey,
User Rank: Ninja
9/20/2013 | 2:02:39 PM
re: Google's Plan To Kill Cookies
Nice analysis - killing cookies only makes them 'not evil' if they don't replace with something equally snoopy. I'm somewhat surprised Chrome is only at 16% - doesn't seem like a half-baked idea like this is going to help that.
Somedude8
50%
50%
Somedude8,
User Rank: Apprentice
9/20/2013 | 4:22:03 PM
re: Google's Plan To Kill Cookies
If one wants to advertise on the web, one would have to play by the rules of a single corporation? Yeah...
WKash
50%
50%
WKash,
User Rank: Apprentice
9/20/2013 | 9:19:46 PM
re: Google's Plan To Kill Cookies
While this seems like a potentially better way to deal with privacy issues, I wonder whether the advertising world will go along with letting Google create a new standard that inevitably will give Google an advantage in tracking online behavior.
rradina
50%
50%
rradina,
User Rank: Apprentice
9/23/2013 | 1:21:09 PM
re: Google's Plan To Kill Cookies
I agree that share looks low. However I recently read that one statistic group recently changed its methods. Among other things, they stopped counting page hits rendered in the background but never viewed (how they know that...I have no idea). They claim hits that are never viewed skew the numbers. I believe the article claimed Chrome leverages background page rendering more than other browsers and thus took the biggest negative hit.
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-2014-0103
Published: 2014-07-29
WebAccess in Zarafa before 7.1.10 and WebApp before 1.6 stores credentials in cleartext, which allows local Apache users to obtain sensitive information by reading the PHP session files.

CVE-2014-0475
Published: 2014-07-29
Multiple directory traversal vulnerabilities in GNU C Library (aka glibc or libc6) before 2.20 allow context-dependent attackers to bypass ForceCommand restrictions and possibly have other unspecified impact via a .. (dot dot) in a (1) LC_*, (2) LANG, or other locale environment variable.

CVE-2014-0889
Published: 2014-07-29
Multiple cross-site scripting (XSS) vulnerabilities in IBM Atlas Suite (aka Atlas Policy Suite), as used in Atlas eDiscovery Process Management through 6.0.3, Disposal and Governance Management for IT through 6.0.3, and Global Retention Policy and Schedule Management through 6.0.3, allow remote atta...

CVE-2014-2226
Published: 2014-07-29
Ubiquiti UniFi Controller before 3.2.1 logs the administrative password hash in syslog messages, which allows man-in-the-middle attackers to obtains sensitive information via unspecified vectors.

CVE-2014-3020
Published: 2014-07-29
install.sh in the Embedded WebSphere Application Server (eWAS) 7.0 before FP33 in IBM Tivoli Integrated Portal (TIP) 2.1 and 2.2 sets world-writable permissions for the installRoot directory tree, which allows local users to gain privileges via a Trojan horse program.

Best of the Web
Dark Reading Radio