Review Chrome platform status, resources, and feature release timelines.
Each of the Privacy Sandbox proposals are in varied stages of the development process. Within each proposal, there are individual features that have different expected availability. This lists the latest feature status availability from Q2 2023. Note: Availability of features prior to Q2 2023 may be removed from the list.
To review the latest information on any proposal or API, visit the respective overview documentation and the Privacy Sandbox timeline.
Aggregation Service
| Proposal | Status |
|---|---|
| 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 |
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 |
Bounce tracking mitigations
- 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.
CHIPS
- 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.
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
- The Fenced Frames proposal is now in general availability.
- Chrome Platform Status
| Proposal | Status |
|---|---|
| Web API changes for urn to config Explainer |
Available in Chrome in Q1 2023. |
| Creative Macros in Fenced Frames for Ads Reporting (FFAR) GitHub Issue |
Available in Chrome in Q3 2023. |
| Send Automatic Beacons Once GitHub Issue |
Available in Chrome in Q3 2023. |
| Serializable Fenced Frames Configs GitHub Issue |
Available in Chrome in Q3 2023. |
| Additional Format Option for Protected Audience Ad Size Macros GitHub Issue |
Available in Chrome in Q4 2023. |
| Automatic beacons sending to all registered URLs GitHub Issue | GitHub Issue |
Available in Chrome in Q4 2023. |
| Enable Leaving Ad Interest Groups from Urn iFrames and Ad Component Frames
GitHub issue |
Available in Chrome in Q1 2024 |
| Introduce reserved.top_navigation_start/commit
GitHub issue, GitHub issue |
Available in Chrome in Q1 2024 |
| Do Not Disable Cookie Setting in ReportEvent until 3PCD
GitHub issue |
Available in Chrome in Q1 2024 |
| Add support for automatic beacons in cross-origin subframes
GitHub issue |
Available in Chrome in Q1 2024 |
Allow Cross-Origin Subframes to Send reportEvent() Beacons
GitHub issue |
Available in Chrome in Q2 2024 |
IP Protection
- 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.
| 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 |
Private State Tokens
- Chrome Platform Status.
- In origin trial Chrome 84 to 101: now closed.
- Demo.
- Chrome DevTools integration.
Protected Audience
Descendant of TURTLEDOVE. Formerly named FLEDGE. Also refer to Status of pending Protected Audience API capabilities for more information.
- 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 (formerly First-Party Sets)
- 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
Shared Storage
- 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 |
User-Agent reduction and Client Hints (UA-CH)
Limit passively shared browser data to reduce the volume of sensitive information which leads to fingerprinting.
- 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.
Closed proposals
FLoC
Replaced by the Topics API.
- Chrome Platform Status.
- Initial origin trial was closed. See Intent to Experiment for updates.
- Blink status.
- API proposal was under discussion with WICG and interest groups.
- GitHub: see issues for API questions and discussion.
Find out more
Blink, Chromium, and Chrome
- What are Chrome release channels?
- Chrome release schedule
- Process for launching new features in Chromium
- Intent to explain: Demystifying the Blink shipping process
- blink-dev: implementation status and discussion of features in Blink, the rendering engine used by Chromium
- Chromium code search
- What are Chrome flags?