demo · v135

Cross-origin reporting payload, after the click

The scenario in the Privacy Sandbox post: a Protected Audience fenced frame renders an ad from creative.example. When the user clicks through, the ad-tech reporter on report.example needs the landing URL and contextual data. The new flag destination_cross_origin lets the automatic beacon carry that cross-origin payload to a different reporting origin without the fenced frame breaking the privacy fence.

Behind a flag Fenced frames need chrome://flags/#enable-fenced-frames plus Protected Audience.

Fenced frames: ?

fenced frame

creative.example/ad.html

window.fence.setReportEventDataForAutomaticBeacons({
  eventType: "reserved.top_navigation_commit",
  eventData: JSON.stringify({ creative_id: 42, dwell_ms: 6300 }),
  destination: ["seller"],
  crossOriginExposed: true   // NEW in Chrome 135
});

→
auto-beacon

reporting endpoint

report.example

POST /event

{ creative_id: 42,
  dwell_ms: 6300,
  destination_url: "merchant.example/p/123" }

scenario focus

Select a scenario to focus its rendered example and summary.

fenced frame

reporting endpoint

see also

scenario focus