Enter a search term such as “mobile analytics” or browse our content using the filters above.
That’s not only a poor Scrabble score but we also couldn’t find any results matching
Check your spelling or try broadening your search.
Sorry about this, there is a problem with our search at the moment.
Please try again later.
Earlier this year, Mozilla added a new feature to Firefox: do not track (DNT) functionality.
When enabled, the Firefox browser includes an HTTP header intended for advertisers and publishers that indicates the user does not want to be tracked.
Many, myself included, were skeptical about the potential efficacy of DNT, but how's it doing thus far?
In a blog post last week, Mozilla's Anurag Phadke revealed that, based on Mozilla's analysis, "just under 5% of our users with DNT turned on within Firefox".
In reality, the number may be slightly higher, as Mozilla's method of counting DNT usage is likely to underestimate the number of users who have activated the feature.
As I have noted before, DNT's fatal flaw is that it relies on advertisers and publishers to respect the DNT HTTP header. For obvious reasons, they have little incentive to do so.
Even if one assumes that advertisers and publishers have the utmost respect for user privacy, DNT has the potential to upset the unspoken compact between individuals and publishers: you give me your content, and I'll tolerate your ads.
If advertisers lose the ability to learn more about the individuals who are perusing the sites on which their ads are displayed, digital ad inventory arguably becomes far less valuable, and advertisers have every incentive to pay less for it, harming the publishers who supply their content at no cost to those who consume it.
None of this, of course, is really Mozilla's problem. But Mozilla does have a problem: enabling DNT is currently a fruitless exercise as Firefox users with DNT enabled have no way of knowing whether any given site is respecting their wishes.
Currently, some 5% (give or take) of Firefox users are telling advertisers and publishers that they don't want to be tracked, but few if any of those advertisers and publishers are listening.
Needless to say, some of the users who have enabled DNT but don't quite understand how it actually works would probably be disappointed to learn that the vast majority of the time, they're still being tracked.
So what should Mozilla do?
Barring unworkable, unenforceable government mandates that advertisers and publishers respect the DNT HTTP header, I think it's safe to say that 'solutions' like Mozilla's are simply not going to be effective.
After all, any amount of DNT user adoption without significant advertiser and publisher adoption fails to address the fundamental concerns that led to it in the first place, and renders DNT little more than a safety blanket that provides no safety.
If the privacy concerns that led to DNT are ever to be effectively addressed, more realistic approaches that don't ignore the economics of digital content will need to be developed.