Status of pending FLEDGE capabilities

As we move FLEDGE closer to general availability and approach third-party cookie deprecation in Chrome, you may be wondering about the availability of FLEDGE services and features. Here you'll find a list of the scoped FLEDGE features and when they'll be supported.

# Event-level auction win reporting

We initially indicated that the event-level auction win reporting would be a temporary solution, and Private Aggregation API will be used to generate summary reports. After listening to feedback and examining the relative complexity of aggregation-based solutions, particularly for billing, we have decided to not remove support for event-level auction win results reporting with reportResult() and reportWin() functions having the ability to call sendReportTo() until sometime after third-party cookie deprecation.

Event-level auction win reporting will be supported until at least 2026, and we will provide advanced notice before the API transitions to any alternative solutions.

Auction loss reporting will continue to be supported through the Private Aggregation API.

# Trusted Execution Environment usage for Key/Value service

The FLEDGE Key/Value service allows the auction to retrieve real-time signals when the bid is generated by the buyer and the ad is scored by the seller. The Key/Value service will eventually be required to run in a trusted execution environment (TEE) to ensure that the user's data is kept private.

Running the Key/Value service in a TEE will not be required until sometime after third-party cookie deprecation. We will provide at least 12 months notice before TEE usage is mandatory. Until then, you can continue to use your own server for real-time key/value signals. Note that running the Key/Value service in a TEE with user-defined functions (UDFs) will be available for testing by the end of Q1 2023 with on-device FLEDGE.

# Fenced frames

Fenced frames are a new HTML element that limits communication between the content and the embedder, and is used for rendering content based on cross-site data. FLEDGE will render content into a fenced frame.

After working closely with various stakeholders and examining the significant effort to accommodate this change, Chrome will not mandate fenced frames until at least 2026 to maintain ecosystem inclusivity,and Chrome will provide significant advanced notice. Until then, if fenced frames are not used, you will need to use an iframe to render the opaque URN. Also, it should be noted that sellers could still require the use of Fenced Frames.

# Improved FLEDGE and Attribution Reporting integration

Recently, challenges have been pointed out around the integration of the Attribution Reporting API and FLEDGE, especially where fenced frames are involved.

For event-level reporting with FLEDGE, we have a proposed set of initial improvements to make this integration easier which you can learn more about in the explainer. The integration will be available for both fenced frames and iFrames. Event-level reporting will be available for testing in Chrome Stable M112+.

For those who need Attribution Reporting with FLEDGE, we are working on more flexible solutions to capture more bidding signals with aggregatable reports, and we will publish a proposal once it is ready.

# K-anonymity

We will soon publish an explainer with more details on how k-anonymity will be enforced using the FLEDGE framework.

For rendering a creative, we will require a crowd of 50 users per creative within the past 7 days to pass the k-anonymity threshold before the ad can be served. The creative is available to be served as soon as it hits the 50 ads threshold and does not need to wait for 7 days.

K-anonymity requirements will be available for testing and will be enforced later in 2023. We encourage feedback from ad tech on this parameter.

# Bidding and Auction Services

We have heard some concerns about FLEDGE latency and are actively working on improving on-device latency. Both Chrome and Android plan to provide Bidding and Auction Services as an additional way to run bidding and scoring logic besides on-device auctions. Bidding and Auction services is a FLEDGE service solution for running auctions off-device, which we believe will allow for even faster performance.

We will continue to support on-device auctions, and the use of the Bidding and Auction Services is not required unless it fits your use cases.

More details can be found in the blog post.

# What's next?

We want to engage in conversations with you to ensure we build an API that works for everyone.

# Discuss the API

Like other Privacy Sandbox proposals, this API is documented and discussed publicly.

# Experiment with the API

You can experiment and participate in conversation about the FLEDGE API.