查看 Chrome 平台狀態、資源和功能發布時程。
每個 Privacy Sandbox 提案都處於不同的開發程序階段。每項提案中都會有個別功能的預估可用性。列出 2023 年第 2 季的最新功能狀態可用。注意：2023 年第 2 季之前的功能可能會從清單中移除。
如要查看任何提案或 API 的最新資訊，請參閱各自的總覽說明文件和 Privacy Sandbox 時間軸。
匯總服務
| 提案 | 狀態 |
|---|---|
| Attribution Reporting API 和 Private Aggregation API 提供的 Amazon Web Services (AWS) 匯總服務支援
說明 |
可用 |
| Aggregation Service 支援 Google Cloud 的 Attribution Reporting API、Private Aggregation API 說明 |
可用 |
| 匯總服務網站註冊和多來源匯總。網站註冊程序包括將網站對應至雲端帳戶 (AWS 或 GCP)。如要匯總多個來源，這些來源必須屬於同一個網站。
GitHub 常見問題 網站匯總 API 說明文件 |
可用 |
| 匯總服務的 epsilon 值最多會保留 64，方便你針對不同參數進行實驗和意見回饋。
提交 ARA Epsilon 意見回饋。 提交 PAA ϵ 意見回饋。 |
有我們會在更新小數值範圍值之前，提前通知生態系統。 |
| 匯總服務查詢的貢獻篩選功能更靈活
說明 |
可用 |
| 災難後復原預算 (錯誤、設定錯誤等) 的流程
說明 |
可用 機制，可查看廣告技術使用預算復原功能復原的共用 ID 百分比，並暫停 2025 年第一季的過度復原作業 |
| 以 AWS 統籌專員的身分運作的 Accenture
開發人員網誌 |
可用 |
| 獨立方，擔任 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 |
跳轉追蹤因應措施
- 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.
方塊
- Chrome 114 以上版本預設支援這項功能。
- 來源試用目前已在 Chrome 100 至 116 推出，現在已經結束。
- 參閱「從實驗意圖」和「意圖：出貨」這兩篇文章。
Federated Credential Management API (FedCM)
- Chrome 平台狀態
- FedCM 在 Chrome 108 版中已出貨。
- FedCM 提案開放公開討論。
- 其他瀏覽器目前尚不支援 FedCM。
- Mozilla 正為 Firefox 和 Apple 提供一般支援，並表示有興趣一起參與 FedCM 提案。
圍欄頁框
- Fenced Frames 提案現已正式發布。
- Chrome 平台狀態
| 提案 | 狀態 |
|---|---|
| 透過 Web API 變更使用者介面設定 說明 |
將於 2023 年第 1 季在 Chrome 推出。 |
| 廣告回報 (FFAR) 的圍欄框架中的廣告素材巨集 GitHub 問題 |
2023 年第 3 季推出。 |
| 傳送自動信標一次 GitHub 問題 |
這項功能將於 2023 年第 3 季在 Chrome 中推出。 |
| Serializable Fenced Frames 設定 GitHub 問題 |
2023 年第 3 季推出。 |
| Protected Audience 廣告大小巨集的其他格式選項 GitHub 問題 |
Chrome 將於 2023 年第 4 季推出。 |
| 自動信標會傳送至所有已註冊的網址 GitHub 問題 |GitHub 問題 |
2023 年第 4 季在 Chrome 推出。 |
| 啟用 Urn 資訊框架和廣告元件框架的離開廣告興趣群組功能
GitHub 問題 |
Chrome 將於 2024 年第 1 季推出 |
| 引入 reserved.top_navigation_start/commit
GitHub 問題、GitHub 問題 |
2024 年第 1 季在 Chrome 推出 |
| 在 3PCD 之前，請勿在 ReportEvent 中停用 Cookie 設定
GitHub 問題 |
2024 年第 1 季在 Chrome 推出 |
| 新增對跨來源子框架中的自動信標支援
GitHub 問題 |
Chrome 將於 2024 年第 1 季推出 |
允許跨來源子框架傳送 reportEvent() 信標
GitHub 問題 |
Chrome 將於 2024 年第 2 季推出 |
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 |
私密狀態權杖
- 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 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
| Proposal | Status |
|---|---|
Event-level reporting for Content Selection (selectURL()) |
Available until at least 2026 |
| Per-site budgeting Explainer |
Available in M119 |
| Allow writing from response headers Explainer GitHub Issue |
Available in M124. Can be manually enabled in M119-M123 |
| Debugging Shared Storage worklets with DevTools Section |
Available in M120 |
| Update Shared Storage data storage limit to 5MB Explainer |
Available in M124 |
createWorklet() to create cross-origin worklets without an iframe |
Available in M125 |
Allow cross-origin script in addModule(), and align createWorklet() to match the behavior |
Available in 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 平台狀態：
- 初始來源試用已關閉。如需最新資訊，請參閱「實驗意圖」。
- 閃爍狀態：
- 我們正在與 WICG 和興趣群組討論 API 提案，
- GitHub：請參閱問題來尋求 API 問題和討論。
瞭解詳情
閃爍、Chromium 和 Chrome
- 什麼是 Chrome 發布版本？
- Chrome 發布時間表
- 在 Chromium 中推出新功能的程序
- 意圖說明：揭開 Blink 運送程序的神秘面紗
- blink-dev：針對 Chromium 使用的轉譯引擎 Blink 中的功能實作狀態和討論
- Chromium 程式碼搜尋
- 什麼是 Chrome 旗標？