查看 Chrome 平台状态、资源和功能发布时间表。
各种 Privacy Sandbox 提案分别处在开发流程的不同阶段。每个提案中，各个功能的预计可用性各不相同。此表格列出了 2023 年第 2 季度最新的功能状态。 注意：2023 年第 2 季度之前的功能发布时间可能会从列表中移除。
如需查看任何提案或 API 的最新信息，请访问相应的概览文档和 Privacy Sandbox 时间表。
汇总服务
| 提案 | 状态 |
|---|---|
| 跨云隐私预算服务
说明 |
可用 |
| 针对 Attribution Reporting API、Private Aggregation API 中的 Amazon Web Services (AWS) 提供汇总服务支持
说明 |
可用 |
| 针对 Attribution Reporting API、Private Aggregation API 的 Google Cloud 汇总服务支持 说明 |
可用 |
| 汇总服务网站注册和多源汇总。网站注册包括将网站映射到云账号（AWS 或 GCP）。如需汇总多个来源，这些来源必须属于同一网站。
GitHub 上的常见问题解答 Site aggregation API 文档 |
可用 |
| 汇总服务的 epsilon 值将保持在 64 以内的范围内，以便对不同的参数进行实验和反馈。
提交 ARA 小数值反馈。 提交 PAA 小样本误差反馈。 |
可用。在更新 epsilon 范围值之前，我们会提前通知生态系统。 |
| 为汇总服务查询提供了更灵活的贡献过滤功能
解说 |
可用 |
| 灾难发生后（错误、配置错误等）预算恢复流程
说明 |
可用 机制，用于查看广告技术平台使用预算恢复功能恢复的共享 ID 的百分比，并暂停计划在 2025 年上半年过度恢复的未来恢复 |
| Accenture 是 AWS 协调者之一
开发者博客 |
可用 |
| 作为 Google Cloud 协调者之一的独立方
开发者博客 |
可用 |
| 汇总服务对 Attribution Reporting API 上的汇总调试报告的支持
说明 |
可用 |
Attribution Reporting
- The Attribution Reporting proposal is now moving to general availability. Raise questions and follow discussion.
- Discuss industry use cases in the Improving Web Advertising Business Group.
- Blink status
- Attribution Reporting Chrome platform status: Specific to this API on Chrome.
- Ads API Chrome platform status: A collection of APIs to facilitate advertising: Protected Audience API, Topics, Fenced Frames and Attribution Reporting.
You can keep track of the API changes.
| Proposal | Status |
|---|---|
| Conversion journey: app-to-web Web explainer and Android explainer Mailing list announcement |
Available in Chrome and Android for origin trial |
| Conversion journey: cross-device Explainer |
This proposal has been archived. There are no current plans for implementation. |
| Preventing invalid aggregatable reports using report verification Explainer |
This proposal has been archived. We have implemented trigger_context_id for this use case instead. |
| Default allowlist for the Attribution Reporting API Permissions-Policy will remain * Mailing list announcement |
Available in Chrome in Q1 2023 |
| Configurable event-Level reporting epsilon GitHub issue |
Available in Chrome in Q4 2023 |
| Padding for aggregatable reports payload Updated explainer |
Available in Chrome in Q4 2023 |
| Phase 1 lite flexible event-Level Flexible event-level configurations explainer |
Available in Chrome in Q4 2023
The ability to customize the number of attribution reports and the number/length of reporting windows. Available in Chrome in Q1 2024 The ability to customize the number of bits of trigger data. |
| Support for Attribution Reporting verbose debugging reports not dependent on third-party cookies Explainer |
Expected in Chrome in early Q3 2024 |
| Support for Attribution Reporting API and Aggregation Service for Google Cloud Attribution Reporting API Explainer Aggregation Service Explainer |
Available in Chrome in H2 2023 |
| Flexible contribution filtering Explainer |
Expected in Chrome in Q3 2024 |
| Pre-attribution filtering: attribution scopes Explainer |
Expected in Chrome in Q3 2024 |
跳出跟踪缓解措施
- 我们已实现反弹跟踪缓解措施提案，以在 Chrome 中进行测试。如果您试用了此功能并有任何反馈，我们非常期待收到您的宝贵意见。
- Chrome 平台状态。
CHIPS
- Chrome 114 及更高版本默认支持。
- Chrome 100 至 Chrome 116 已有一项源试用现已结束，
- 阅读实验意图和发布意图。
Federated Credential Management API (FedCM)
- Chrome Platform Status
- FedCM shipped in Chrome 108.
- The FedCM proposal is open for public discussion.
- FedCM isn't supported in other browsers yet.
- Mozilla is implementing a prototype for Firefox and Apple has expressed general support and interest in working together on the FedCM proposal.
Fenced Frames
- 围栏框架提案现已正式发布。
- Chrome 平台状态
| 提案 | 状态 |
|---|---|
| 将 urn 更改为 config 的 Web API 变更 说明 |
2023 年第 1 季度在 Chrome 中提供。 |
| 围栏框架中的广告素材宏用于广告报告 (FFAR) GitHub 问题 |
将于 2023 年第 3 季度在 Chrome 中提供。 |
| 一次发送自动信标 GitHub 问题 |
将于 2023 年第 3 季度在 Chrome 中推出。 |
| 可序列化的围栏帧配置 GitHub 问题 |
将于 2023 年第 3 季度在 Chrome 中提供。 |
| 针对 Protected Audience 广告尺寸宏的其他格式选项 GitHub 问题 |
2023 年第 4 季度在 Chrome 中提供。 |
| 自动向所有已注册网址发送信标 GitHub 问题 | GitHub 问题 |
2023 年第 4 季度在 Chrome 中提供。 |
| 启用从 Urn iFrame 和广告组件框架中退出广告兴趣群组的功能
GitHub 问题 |
2024 年第 1 季度在 Chrome 中推出 |
| 引入了 reserved.top_navigation_start/commit
GitHub 问题、GitHub 问题 |
2024 年第 1 季度在 Chrome 中推出 |
| 在 3PCD 之前，请勿在 ReportEvent 中停用 Cookie 设置
GitHub 问题 |
2024 年第 1 季度在 Chrome 中推出 |
| 添加对跨源子框架中的自动信标的支持
GitHub 问题 |
2024 年第 1 季度在 Chrome 中推出 |
允许跨源子帧发送 reportEvent() 信标
GitHub 问题 |
2024 年第 2 季度在 Chrome 中推出 |
IP 保护
- The IP Protection proposal has entered public discussion.
- This proposal has not been implemented in any browser.
Private Aggregation API
- The Private Aggregation API is now moving to general availability.
- New function names
- The
contributeToHistogram()function is available in Chrome Canary, Dev, Beta, and Stable M115+ - The
contributeToHistogramOnEvent()function is available in Chrome Canary, Dev, Beta, and Stable M115+
- The
- Legacy function names
- The following function names will be deprecated in M115
- See the Chrome platform status page page to see the API's current stage.
| 提案 | 状态 |
|---|---|
| 通过对共享存储空间的报告进行验证，防止 Private Aggregation API 报告无效 说明 |
在 Chrome 中提供 |
| 私有汇总调试模式的可用性取决于 3PC 资格条件 GitHub 问题 |
适用于 Chrome M119 |
| 缩短报告延迟时间 说明 |
适用于 Chrome M119 |
| 共享存储空间的不公开汇总贡献超时 说明 |
适用于 M119 |
| 支持 Google Cloud 专用汇总 API 和汇总服务 说明 |
适用于 Chrome M121 |
| 可汇总报告载荷的填充 说明 |
适用于 Chrome M119 |
| 私密汇总调试模式适用于 auctionReportBuyers 报告 说明 |
适用于 Chrome M123 |
| 过滤 ID 支持 说明 |
适用于 Chrome M128 |
| 客户端贡献合并 说明 |
适用于 Chrome M129 |
私密状态令牌
- Chrome Platform Status.
- In origin trial Chrome 84 to 101: now closed.
- Demo.
- Chrome DevTools integration.
Protected Audience
TURTLEDOVE 的后代。以前称为 FLEDGE。如需了解详情，请参阅待处理的 Protected Audience API 功能的状态。
- The Protected Audience API proposal is now moving to general availability. Raise questions and follow discussion.
- Protected Audience API status of pending capabilities details changes and enhancements to the Protected Audience API API and features.
- Blink status
- Protected Audience API Chrome platform status: Specific to the Protected Audience API on Chrome.
- Ads API Chrome platform status: A collection of APIs to facilitate advertising: Protected Audience API, Topics, Fenced Frames and Attribution Reporting.
To be notified of status changes in the API, join the mailing list for developers.
| Proposal | Status |
|---|---|
| Buyer Reporting ID for Custom Breakdowns Github Issue |
Available in Chrome in Q3 2023 |
| Currency for Highest and bid Highest Other Scoring Bid Github Issue |
Available in Chrome in Q3 2023 |
| Macro Support for Third-party Ad Trackers (3PAT) Github Issue |
Available in Chrome in Q3 2023 |
| Support for Negative Interest Group Targeting Github Issue |
Available in Chrome in Q4 2023 |
| Secure Propagation of Auction Signals without WebBundles Github Issue |
Available in Chrome in Q4 2023 |
| Bulk Interest Group Deletion Github Issue |
Available in Chrome in Q4 2023 |
| Increase Interest Group Cap from 1K to 2K Github Issue |
Available in Chrome in Q4 2023 |
| Support for Bidding and Auction Beta 1 Explainer |
Available in Chrome (via Origin Trial) in Q4 2023 |
| Request for Ad Slot size as an additional Buyer Trusted Signal GitHub issue |
Available in Chrome in Q1 2024 |
| directFromSellerSignals to use LIFO ordering | Available in Chrome in Q1 2024 |
| Negative Targeting to work with iFrame Loads | Available in Chrome in Q1 2024 |
| Allow Updating IG userBiddingSignals | Available in Chrome in Q1 2024 |
| Allow Updating IG executionMode | Available in Chrome in Q1 2024 |
| Include Chrome-facilitated Testing Label in Trusted Server Requests
GitHub issue |
Available in Chrome in Q2 2024 |
Downsampled forDebuggingOnly() labels
GitHub issue |
Available in Chrome in Q2 2024 |
| Prevent Overly Large Trusted Bidding Signal URLs
GitHub issue |
Available in Chrome in Q2 2024 |
| Increase Ad Component Max Count from 20 to 40
GitHub issue |
Available in Chrome in Q2 2024 |
deprecatedReplaceInURN() for multi-seller auctions
GitHub issue |
Available in Chrome in Q2 2024 |
Allow generateBid() to return multiple bids
GitHub issue |
Available in Chrome in Q2 2024 |
| Key/Value Service update for interest group
GitHub issue |
Available in Chrome in Q2 2024 |
| K-anonymity will be enforced on 20% of the unlabeled traffic outside of the Chrome-facilitated testing
Explainer |
Available in Chrome in Q2 2024 |
| Real-Time Monitoring API to get auction data to buyers and sellers as quickly as possible (e.g. < 10 mins) to support monitoring and alerting | Available in Chrome in Q3 2024 |
| Deal ID
GitHub issue |
Expected in Chrome in Q4 2024 |
Related Website Set（以前称为 First-Party Set）
- Related Website Sets has now moved to general availability in Chrome.
- The first origin trial ran from Chrome 89 to 93.
- Chrome Platform Status.
- Blink status.
- Chromium Projects
- Related Website Sets submission guidelines
共享存储空间
- The Shared Storage API has now moved to general availability.
- A live demo is available, as is testing:
- URL selection output gate is available for local testing from Chrome M105+.
- Private Aggregation output gate is available for local testing from Chrome M107+.
- Measurement with the Private Aggregation API is now in general availability.
- Chrome platform status
| 提案 | 状态 |
|---|---|
| 允许从响应标头写入 说明 GitHub 问题 |
适用于 M124。可以在 M119-M123 中手动启用 |
| 使用开发者工具调试共享存储空间 Worklet 部分 |
在 M120 中提供 |
| 将共享存储空间数据存储空间上限更新为 5MB 说明 |
适用于 M124 |
createWorklet()，用于创建不使用 iframe 的跨源 worklet |
在 M125 中提供 |
允许在 addModule() 中使用跨源脚本，并使 createWorklet() 与该行为保持一致 |
在 M130 中提供 |
Storage Access API
- Storage Access API supported by default from Chrome 119 an higher.
- Chrome Platform Status.
- Blink status.
Topics API
- The Topics API is now in general availability.
- To provide your feedback on the Topics API, create an Issue on the Topics explainer or participate in discussions in the Improving Web Advertising Business Group. The explainer has a number of open questions that still require further definition.
- Topics API latest updates details changes and enhancements to the Topics API and implementations.
- Topics Chrome platform status: Specific to the Topics API on Chrome.
- Ads API Chrome platform status: A collection of APIs to facilitate advertising: Protected Audience API, Topics, Fenced Frames and Attribution Reporting.
| Feature | Status |
|---|---|
| Improved taxonomy for Topics (latest note) | Available in Chrome in M119 |
| Updated top topics selection algorithm | Available in Chrome in M120 |
用户代理缩减和客户端提示 (UA-CH)
限制被动共享的浏览器数据，以减少导致数字“指纹”收集的敏感信息量。
- Origin trial Chrome 95 to 103, ended March 7, 2023.
- Deprecation trial Chrome 103 to Chrome 116, ended September 23, 2023.
- Chrome DevTools integration
- Review the UA-CH Chrome platform status
User-Agent Client Hints API documentation is available on MDN.
已关闭的提案
FLoC
已被 Topics API 取代。
- Chrome 平台状态。
- 初始来源试用已结束。 如需了解最新动态，请参阅意向开展实验。
- Blink 状态。
- API 提案正在与 WICG 和利益相关方讨论中。
- GitHub：如需查看 API 问题和讨论，请参阅问题。
了解详情
Blink、Chromium 和 Chrome
- 什么是 Chrome 发布渠道？
- Chrome 发布时间表
- 在 Chromium 中发布新功能的流程
- 意图说明：揭秘 Blink 配送流程
- blink-dev：Chromium 使用的渲染引擎 Blink 的实现状态和功能讨论
- Chromium 代码搜索
- 什么是 Chrome 标志？