Topics API
Topics API 是什么?
Topics APIA Privacy Sandbox API in Chrome and Android that derives a small set of high-level interest topics from the user's recent browsing locally on the device, exposing them to participating sites instead of cross-site tracking identifiers.
The Topics API is a Privacy Sandbox component that replaces third-party-cookie-based behavioural interest signals with a locally derived, low-resolution interest taxonomy. Chrome (and Android) infers, on device, up to a few coarse topics — drawn from a public taxonomy of a few hundred categories such as 'Sports/Soccer' or 'Travel/Hotels & Accommodations' — based on the top-level hostnames the user has visited over the past few weeks. When a caller invokes `document.browsingTopics()`, the browser returns a small random sample of recent topics (with random noise to limit linkability), but only for hostnames that were observed by that caller in the past. This means a fingerprinter sitting on a single site cannot ask for topics on behalf of unrelated callers, and a site cannot use the topics as a stable identifier. Critics — Mozilla, Brave, the EFF, several DPAs — have argued the API still reveals more than necessary and effectively endorses behavioural advertising at the browser level. Google launched Topics for general availability in Chrome in 2023 and on Android in 2024; uptake by ad-tech players grew through 2024–2025 in tandem with Privacy Sandbox.
● 示例
- 01
An ad-tech vendor calls `document.browsingTopics()` from its tag on a sports site, receives `Sports/Soccer` for that user, and uses it as a contextual signal.
- 02
A regulator's analysis observes that, even with topic noise, frequent callers can build short-lived behavioural cohorts and flags the API for further review.
● 常见问题
Topics API 是什么?
A Privacy Sandbox API in Chrome and Android that derives a small set of high-level interest topics from the user's recent browsing locally on the device, exposing them to participating sites instead of cross-site tracking identifiers. 它属于网络安全的 隐私与数据保护 分类。
Topics API 是什么意思?
A Privacy Sandbox API in Chrome and Android that derives a small set of high-level interest topics from the user's recent browsing locally on the device, exposing them to participating sites instead of cross-site tracking identifiers.
Topics API 是如何工作的?
The Topics API is a Privacy Sandbox component that replaces third-party-cookie-based behavioural interest signals with a locally derived, low-resolution interest taxonomy. Chrome (and Android) infers, on device, up to a few coarse topics — drawn from a public taxonomy of a few hundred categories such as 'Sports/Soccer' or 'Travel/Hotels & Accommodations' — based on the top-level hostnames the user has visited over the past few weeks. When a caller invokes `document.browsingTopics()`, the browser returns a small random sample of recent topics (with random noise to limit linkability), but only for hostnames that were observed by that caller in the past. This means a fingerprinter sitting on a single site cannot ask for topics on behalf of unrelated callers, and a site cannot use the topics as a stable identifier. Critics — Mozilla, Brave, the EFF, several DPAs — have argued the API still reveals more than necessary and effectively endorses behavioural advertising at the browser level. Google launched Topics for general availability in Chrome in 2023 and on Android in 2024; uptake by ad-tech players grew through 2024–2025 in tandem with Privacy Sandbox.
如何防御 Topics API?
针对 Topics API 的防御通常结合技术控制与运营实践,详见上方完整定义。
Topics API 还有哪些其他名称?
常见的别称包括: Browsing Topics API。
● 相关术语
- privacy№ 960
Privacy Sandbox
Google's umbrella initiative for replacing third-party cookies and cross-site identifiers with privacy-preserving alternatives — Topics, Protected Audience (FLEDGE), Attribution Reporting, and on-device APIs — under heavy regulatory and competitor scrutiny.
- privacy№ 088
Attribution Reporting API
A Privacy Sandbox API in Chrome and Android that lets advertisers measure ad conversions across sites without cross-site identifiers, using browser-mediated, noise-injected event-level or aggregated reports.
- privacy№ 1263
第三方 Cookie
由浏览器地址栏域名之外的另一域名设置的 Cookie,历史上常用于跨站点跟踪用户。
- privacy№ 143
浏览器指纹识别
一种无状态跟踪技术,通过组合浏览器、设备和配置属性,生成近乎唯一的标识来识别用户。
- privacy№ 266
跨站点跟踪
将同一用户在多个不相关网站上的活动关联起来,构建长期行为画像的做法。
- privacy№ 914
个人可识别信息 (PII)
可单独或与其他信息结合用于识别特定个人的任何数据,例如姓名、标识符或生物特征记录。