/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

← → days · ↑ ↓ browse · Enter similar · o open

Google Finally Adds Do-Not-Track Support in Latest Test Version of Chrome

Google has included support for the Do Not Track privacy setting in its latest Chrome developer build, which was released today.  —  Do Not Track — which aims to help users opt out of being tracked across Web sites …

AllThingsD Liz Gannes

Context & Ripple Effects

In February 2012, the Wall Street Journal reported that major web firms had agreed to adopt a 'No Track' button, putting the industry on record behind the Do Not Track preference signal (Web Firms to Adopt 'No Track' Button). Seven months later, Google has followed through where it matters most for its own business: Do Not Track support now appears in the latest Chrome developer build.

The timing is notable because Chrome is the browser of the company whose advertising revenue gives it the most to lose from widespread opt-outs. The story drew same-day pickups from CNET, Neowin, and BrowserFame — solid trade coverage rather than front-page news, reflecting that shipping the setting is a compliance step, not yet a change in what websites actually do with the signal.

First-order effects

  • Chrome developer-build users gain a working Do Not Track toggle, closing the gap with the commitment Google made alongside other major web firms in February 2012.
  • Google now sends the DNT header from its own browser while remaining the largest seller of the targeted ads the signal asks to suppress — putting its ad business and its browser team on opposite sides of the same preference.

Second-order effects

  • Websites and ad networks face mounting pressure to state publicly whether they honor the header, since a DNT setting that most sites ignore shifts blame from browsers to the tracking ecosystem itself.
  • Rival browser makers lose 'Google won't participate' as a talking point, making non-support harder to defend and pushing adoption toward universal default-on or default-off debates.

Third-order effects

  • If every major browser ships the signal, the battleground moves from implementation to enforcement — regulators and standards bodies become the arbiters of what 'do not track' legally means, since voluntary honoring has no teeth.
  • The episode foreshadows the deeper structural question: whether self-regulation via browser signals can constrain behavioral advertising at all, or whether the industry will need binding rules to make an opt-out meaningful.

The trend: Browser makers are converging on universal Do Not Track support faster than the advertising industry is converging on honoring it, moving the real fight from shipping the setting to enforcing it.