From c21ba67939a32ffa9663b5e3dc74f98a4761331e Mon Sep 17 00:00:00 2001 From: Xiaochen Zhou Date: Tue, 10 Oct 2023 09:57:18 -0400 Subject: [PATCH] Add info about when the ad component support for event reporting is available. (#622) * Added info about when the ad component support is available. * Mention that all combination of urn-iframe and fenced frame works. * Update Fenced_Frames_Ads_Reporting.md Co-authored-by: Paul Jensen * Update Fenced_Frames_Ads_Reporting.md Co-authored-by: Paul Jensen --------- Co-authored-by: Paul Jensen --- Fenced_Frames_Ads_Reporting.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/Fenced_Frames_Ads_Reporting.md b/Fenced_Frames_Ads_Reporting.md index c3b015772..1c504ca45 100644 --- a/Fenced_Frames_Ads_Reporting.md +++ b/Fenced_Frames_Ads_Reporting.md @@ -218,6 +218,9 @@ window.fence.setReportEventDataForAutomaticBeacons({ ``` # Support for Ad Components +For ad components [rendered in fenced frames](https://github.com/WICG/turtledove/blob/main/FLEDGE.md#4-browsers-render-the-winning-ad), the support for event-level reporting described below is available in Chrome starting M114. +For ad components rendered in iframes, the support will be available in Chrome starting M115. The support works for all combinations of the top-level ad and ad component being rendered in iframes and/or Fenced Frames. + ## Goal When a rendered ad is composed of [multiple pieces](https://github.com/WICG/turtledove/blob/main/FLEDGE.md#34-ads-composed-of-multiple-pieces), it is useful to detect user clicks that happened on ad components.