API status and feature releases

Review Chrome platform status, resources, and feature release timelines.

Published on Updated on

Translated to: Español, Português, 한국어, 中文, Pусский, 日本語, Français, Deutsch

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.

To review the latest information on any proposal or API, visit the respective overview documentation and the Privacy Sandbox timeline.

Aggregation Service

ProposalStatus
Aggregation Service support for Google Cloud Platform across Attribution Reporting API, Private Aggregation API
Explainer
Expected in Q4 2023
Aggregation Service site enrollment and mapping of a site to cloud accounts (AWS, or GCP)
FAQs on GitHub
Expected in Q4 2023

Attribution Reporting

You can keep track of the API changes.

ProposalStatus
Event-level reports for clicks and views
Explainer
Available in Chrome
Aggregatable reports for clicks and views
Explainer
Available in Chrome
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 via report verification
Explainer
Expected in Chrome in H1 2024
Support for multiple destinations in source registration
Chromium Bug
Available in Chrome in Q1 2023
Default allowlist for the Attribution Reporting API Permissions-Policy will remain *
Mailing list announcement
Available in Chrome in Q1 2023
Support for filter-based deduplication keys for aggregatable reports
Mailing list announcement
Available in Chrome in Q1 2023
Support for source registration success reports in verbose debugging
Debugging cookbook
Available in Chrome in Q1 2023
Reducing delays for aggregatable reports
Github issue | Updated Explainer
Available in Chrome in Q2 2023
Phase 1 Lite Flexible Event-Level
Flexible event-level configurations explainer
Expected in Chrome in Q4 2023
Phase 2 Full Flexible Event-Level
Flexible event-level configurations explainer
Expected in Chrome in Q1 2024
Support for Attribution Reporting debugging after third-party cookie deprecation
Seeking feedback on GitHub
Expected in Chrome in H1 2024
Support for Attribution Reporting API and Aggregation Service for Google Cloud
Attribution Reporting API Explainer
Aggregation Service Explainer
Expected in Chrome in H2 2023

Bounce tracking mitigations

CHIPS

Federated Credential Management API (FedCM)

Fenced Frames

ProposalStatus
Web API changes for urn to config
Explainer
Available in Chrome in Q1 2023.
Add size to API for K-Anon check for URLs and Frame Size
Github Issue
Available in Chrome in Q2 2023.
Protected Audience Fenced Frames support for event-level reports with Attribution Reporting
Github Issue
Available in Chrome in Q1 2023.
Protected Audience, Fenced Frames, and Private Aggregation API support
urn-iframes reportEvent
Github Issue
Available in Chrome in Q1 2023.
Protected Audience component ads reporting
Github Issue
Available in Chrome in Q2 2023.
Deprecate src attribute for the config attribute
Github Issue
Available in Chrome in Q2 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 Fortmat 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.

IP Protection

Private Aggregation API

Update

The Private Aggregation API will contain the following breaking changes in the M115 Beta and Stable releases:

  1. The sendHistogramReport() function is renamed to contributeToHistogram().
  2. The reportContributionForEvent() function is renamed to contributeToHistogramOnEvent().
  3. enableDebugMode()’s debug_key parameter is renamed to debugKey.
  4. The reporting endpoint is renamed from /.well-known/private-aggregation/report-fledge to /.well-known/private-aggregation/report-protected-audience.
  5. The api property value of the aggregatable report payload is renamed from fledge to protected-audience.

You must update your code to ensure that the Private Aggregation API continues to work with the Protected Audience API. Users in an outdated Chrome instance will still send their report to the legacy endpoint, so you should ensure backward compatibility to collect all reports. We recommend using feature detection with if ('contributeToHistogram' in privateAggregation)).

These changes will be possible for testing from the week of Monday, May 22nd in Canary and Dev channels.

  • 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+
  • 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.
ProposalStatus
Support for debugging mode and testing of reporting aggregation with the debug mode and local testing tool
Private Aggregation API documentation
Available in Chrome in Q2 2023
Private Aggregation API available for origin trial testing in Chrome stable channel
Explainer
Available in Chrome in Q2 2023
Prevent invalid Private Aggregation API reports with report verification for Shared Storage
Explainer
Available in Chrome in Q2 2023
Private Aggregation debug mode availability dependent on 3PC eligibility
GitHub issue
Available in Chrome M119
Reducing report delay
Explainer
Available in Chrome M119
Support for Private Aggregation API and Aggregation Service for Google Cloud
Explainer
Expected in Chrome M121
Padding for aggregatable report payloads
Explainer
Available in Chrome M119

Private State Tokens

Protected Audience

Descendant of TURTLEDOVE. Formerly named FLEDGE. Also refer to Status of pending Protected Audience API capabilities for more information.

To be notified of status changes in the API, join the mailing list for developers.

ProposalStatus
Per-Buyer Latency Reporting
Github Issue
Available in Chrome in Q1 2023
Direct Seller Destination Support
Github Issue
Available in Chrome in Q1 2023
Per-Buyer Wall-Time Timeout
Github Issue
Available in Chrome in Q1 2023
Accuracy-limited ad cost for cost-per-click billing
Github Issue
Available in Chrome in Q2 2023
Event-level User Bidding Signals for Modeling
Github Issue
Available in Chrome in Q2 2023
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
Expected in Chrome in Q4 2023
Secure Propagation of Auction Signals without WebBundles
Github Issue
Expected in Chrome in Q4 2023
Bulk Interest Group Deletion
Github Issue
Expected in Chrome in Q4 2023
Increase Interest Group Cap from 1K to 2K
Github Issue
Expected in Chrome in Q4 2023
Support for Bidding and Auction Beta 1
Explainer
Expected in Chrome (via Origin Trial) in Q4 2023

Shared Storage

ProposalStatus
Event-level reporting for Content Selection (selectURL())Available until at least 2026
Per-site budgeting
Explainer
Expected in Chrome Q4 2023
Allow writing from response headers
Explainer
Expected in Chrome Q4 2023

Topics API

FeatureStatus
Improved taxonomy for Topics (latest note)Expected in Chrome in Q4 2023.

User-Agent reduction and Client Hints (UA-CH)

Limit passively shared browser data to reduce the volume of sensitive information which leads to fingerprinting.

User-Agent Client Hints API documentation is available on MDN.

Closed proposals

FLoC

Replaced by the Topics API.


Find out more

Origin trials

Updated on Improve article

This site uses cookies to deliver and enhance the quality of its services and to analyze traffic. If you agree, cookies are also used to serve advertising and to personalize the content and advertisements that you see. Learn more about our use of cookies.