Последнее обновление: четверг, 30 января 2025 г.
Просмотрите состояние платформы Chrome, ресурсы и сроки выпуска функций.
Каждое из предложений Privacy Sandbox находится на разных стадиях разработки. В каждом предложении есть отдельные функции, которые имеют разную ожидаемую доступность.
Чтобы просмотреть самую свежую информацию о любом предложении или API, посетите соответствующую обзорную документацию и временную шкалу Privacy Sandbox .
Служба агрегации
| Proposal | Status |
|---|---|
| Cross Cloud Privacy Budget Service
Explainer |
Available |
| Aggregation Service support for Amazon Web Services (AWS) across Attribution Reporting API, Private Aggregation API
Explainer |
Available |
| Aggregation Service support for Google Cloud across Attribution Reporting API, Private Aggregation API Explainer |
Available |
| Aggregation Service site enrollment and multi-origin aggregation. Site enrollment includes mapping of a site to cloud accounts (AWS, or GCP). To aggregate multiple origins, they must be of the same site.
FAQs on GitHub Site aggregation API documentation |
Available |
| The Aggregation Service's epsilon value will be kept as a range of up to 64, to facilitate experimentation and feedback on different parameters.
Submit ARA epsilon feedback. Submit PAA epsilon feedback. |
Available. We will provide advanced notice to the ecosystem before the epsilon range values are updated. |
| More flexible contribution filtering for Aggregation Service queries
Explainer |
Available |
| Process for budget recovery post-disasters (errors, misconfigurations, and so on)
Explainer |
Available Mechanism to review the percentage of shared IDs recovered by an ad tech using budget recovery and suspend future recoveries for excessive recoveries planned for H1 2025 |
| Accenture operating as one of the Coordinators on AWS
Developer Blog |
Available |
| Independent party operating as one of the Coordinators on Google Cloud
Developer blog |
Available |
| Aggregation Service support for Aggregate Debug Reporting on Attribution Reporting API
Explainer |
Available |
| Cross-cloud cryptographic key services
Explainer |
Expected in H1 2025 |
Отчеты по атрибуции
- Attribution Reporting 提案现已正式发布。提出问题并关注讨论内容。
- 在 Improving Web Advertising Business Group（改进网络广告业务群组）中讨论行业用例。
- 闪烁状态
- Attribution Reporting Chrome 平台状态：针对 Chrome 上的此 API。
- Ads API Chrome 平台状态：一系列有助于投放广告的 API，包括：Protected Audience API、Topics、Fenced Frames 和 Attribution Reporting。
您可以跟踪 API 更改。
| 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 |
| 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 |
Available in Chrome in 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 |
Available in Chrome in Q3 2024 |
| Pre-attribution filtering: attribution scopes Explainer |
Available in Chrome in Q4 2024 |
Меры по устранению последствий отслеживания отказов
- The Bounce tracking mitigations proposal has been implemented for testing in Chrome. If you try this out and have any feedback, we'd love to hear it.
- Chrome platform status.
ЧИПСЫ
- Supported by default in Chrome 114 and higher.
- An origin trial, now complete, was available from Chrome 100 to 116.
- Read the Intent to Experiment and Intent to Ship.
API федеративного управления учетными данными (FedCM)
- Chrome 平台状态
- Chrome 108 中已提供 FedCM。
- FedCM 提案可供公开讨论。
- 其他浏览器尚不支持 FedCM。
- Mozilla 正在实现 Firefox 的原型，并且 Apple 已表示对就 FedCM 提案展开合作的普遍支持和兴趣。
Огороженные рамы
- The Fenced Frames proposal is now in general availability.
- Chrome Platform Status
| 提案 | 状态 |
|---|---|
| 将 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 中推出 |
信标中的 Referer 标头
GitHub 问题 |
2025 年第 1 季度在 Chrome 中推出 |
IP-защита
- The IP Protection proposal has entered public discussion.
- This proposal has not been implemented in any browser.
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.
| Proposal | Status |
|---|---|
| Prevent invalid Private Aggregation API reports with report verification for Shared Storage Explainer |
Available in Chrome |
| Private Aggregation debug mode availability dependent on 3PC eligibility GitHub issue |
Available in Chrome M119 |
| Reducing report delay Explainer |
Available in Chrome M119 |
| Private Aggregation contribution timeout for Shared Storage Explainer |
Available in M119 |
| Support for Private Aggregation API and Aggregation Service for Google Cloud Explainer |
Available in Chrome M121 |
| Padding for aggregatable report payloads Explainer |
Available in Chrome M119 |
| Private Aggregation debug mode available for auctionReportBuyers reporting Explainer |
Available in Chrome M123 |
| Filtering ID support Explainer |
Available in Chrome M128 |
| Client-side contribution merging Explainer |
Available in Chrome M129 |
| Per-context contribution limits Explainer |
Expected in Q1 2025 |
| Named budgets Explainer |
Expected in Q1 2025 |
| Aggregate error reporting Explainer |
Expected in Q1 2025 |
Частные государственные токены
- Chrome Platform Status.
- In origin trial Chrome 84 to 101: now closed.
- Demo.
- Chrome DevTools integration.
Защищенная аудитория
Потомок ГЕРЕПАХИ . Ранее назывался FLEDGE. Дополнительную информацию также можно найти в разделе Статус ожидающих возможностей 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 |
| Deals support through reporting ID enhancements
GitHub issue |
Expected in Chrome in Q1 2025 |
| Additional bids auction nonce hardening GitHub issue |
Expected in Chrome in Q1 2025 |
Сопутствующие наборы веб-сайтов (ранее — собственные наборы)
- 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 |
createWorklet() 中对自定义数据源的支持说明 |
预计 2025 年第 1 季度 |
| 允许共享存储空间 Worklet 读取兴趣群组 说明 |
预计 2025 年第 1 季度 |
| 使用 DevTools 调试共享存储空间 Worklet 说明 GitHub 问题 |
预计 2025 年第 1 季度 |
API доступа к хранилищу
- Chrome 119 及更高版本默认支持 Storage Access API。
- Chrome 平台状态。
- 闪烁状态。
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.
| Особенность | Положение дел |
|---|---|
| Улучшенная таксономия тем (последняя заметка ) | Доступен в хроме M119. |
| Обновлен алгоритм выбора топ-тем | Доступен в хроме в M120. |
Сокращение числа пользовательских агентов и подсказки для клиентов (UA-CH)
Ограничьте пассивный общий доступ к данным браузера, чтобы уменьшить объем конфиденциальной информации, которая приводит к снятию отпечатков пальцев.
- Пробная версия Origin Chrome 95–103, закончившаяся 7 марта 2023 г.
- Пробная версия Chrome 103 до Chrome 116 закончится 23 сентября 2023 г.
- Интеграция с Chrome DevTools
- Проверьте статус платформы Chrome UA-CH.
Документация по API User-Agent Client Hints доступна на MDN .
Закрытые предложения
ФЛОК
Заменено API тем .
- Статус платформы Chrome .
- Первоначальное судебное разбирательство по происхождению было закрытым. Обновления см. в разделе « Намерение экспериментировать ».
- Статус мигания .
- Предложение API обсуждалось с WICG и заинтересованными группами.
- GitHub : см . вопросы по API и обсуждение.
Узнать больше
Блинк, Хром и Хром
- Какие каналы выпуска Chrome?
- График выпуска Chrome
- Процесс запуска новых функций в Chromium
- Намерение объяснить: демистификация процесса доставки Blink
- Blink-dev : статус реализации и обсуждение функций Blink, механизма рендеринга, используемого Chromium.
- Поиск по коду Chrome
- Что такое флаги Chrome?