Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update automatic beacon explainer for new sending behavior #808

Merged
merged 7 commits into from
Nov 8, 2023
Merged

Update automatic beacon explainer for new sending behavior #808

Changes from 1 commit
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
97e8f56
update automatic beacon explainer
blu25 Sep 14, 2023
dedbe93
update section on component ads
blu25 Sep 26, 2023
c0d0ad4
update to include changes from security review
blu25 Oct 9, 2023
5f68360
fix formatting
blu25 Oct 9, 2023
d28afbe
update to include changes from code review
blu25 Oct 10, 2023
8bf8260
address review comments
blu25 Oct 23, 2023
ee968ab
fix typo
blu25 Oct 26, 2023
File filter

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
fix formatting
  • Loading branch information
@blu25
blu25 committed Oct 9, 2023
commit 5f683600c602912756f63a4796d31d5543333877
1 change: 0 additions & 1 deletion Fenced_Frames_Ads_Reporting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -159,7 +159,6 @@ As mentioned in the explainer above, `reportEvent` beacons are POST requests and

blu25 marked this conversation as resolved.
Show resolved Hide resolved
Since the `reserved.top_navigation` beacons are automatically generated by the browser, there needs to be some way for those beacons to include event data, as it happens in `reportEvent` generated beacons. Because this is information about a frame that can be sent to a cross-origin destination, there also needs to be a way for the frame to opt in/opt out of having this information sent. To achieve this, a new `setReportEventDataForAutomaticBeacons` API can be invoked from within the fenced frame:


```
window.fence.setReportEventDataForAutomaticBeacons({
'eventType': 'reserved.top_navigation',
Expand Down