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.

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

Event-level reporting (debugging) API #275

Closed
barteklos opened this issue Mar 28, 2022 · 2 comments
Closed

Event-level reporting (debugging) API #275

barteklos opened this issue Mar 28, 2022 · 2 comments

Comments

@barteklos
Copy link

Hi,

We started experimenting with the FLEDGE event-level reporting (debugging) API for both winning and losing bids: forDebuggingOnly.reportAdAuctionWin and forDebuggingOnly.reportAdAuctionLoss.

One thing we realized is the fact that it only works with --enable-features=BiddingAndScoringDebugReportingAPI flag turned on. Could you please confirm that this flag would not be needed during FOT#1 and the API would be available by default.

Best regards,
Bartosz

@jeffkaufman
Copy link
Contributor

jeffkaufman commented Mar 31, 2022

https://chromium.googlesource.com/chromium/src/+/26692dbdb845d6341acc945a3b5d7c22167f68d4

"Add BiddingAndScoringDebugReportingAPI switch to privacy sandbox flag. This enables the forDebuggingOnly.reportAdAuction[Loss|Win]() APIs."

michaelkleber pushed a commit that referenced this issue Apr 26, 2022
The BiddingAndScoringDebugReportingAPI flag was missing from the list of flags required to make Chrome's behavior mimic the details in this doc.
@JensenPaul
Copy link
Collaborator

I believe this was addressed in #288.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants