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

Extended Private Aggregation Reporting #1151

Closed
MarcoLugo opened this issue Apr 25, 2024 · 6 comments
Closed

Extended Private Aggregation Reporting #1151

MarcoLugo opened this issue Apr 25, 2024 · 6 comments

Comments

@MarcoLugo
Copy link

Hello,

Has there been any consideration for adding something like script-fetch-time here?

Any status update on introducing generateBid() hitting timeout? This is definitely a metric that we would find useful.

Thank you.

@JensenPaul
Copy link
Collaborator

This ask is similar to patcg-individual-drafts/private-aggregation-api#119

@MarcoLugo
Copy link
Author

Great, thank you Paul. Closing this one as it's duplicated.

@morlovich
Copy link
Collaborator

So I am not sure you saw this via what this was duped against:

Hi... So we've been looking to potential ways of addressing feedback given here and in similar issues, and put together a doc with a possible direction:

https://docs.google.com/document/d/1EHVJkKUKIL4dMFrcJ6FJH65Ad4Ml7pKZ8Iepft5OvYk/edit?usp=sharing

we would appreciate feedback on the overall approach, and also on the particularities of metrics and how well they suit their needs (including, of course, potential alternatives you would find preferable). Probably easiest to put it in patcg-individual-drafts/private-aggregation-api#119, since I don't know how to sensibly ACL a public doc so it's accessible to people and not spammers.

@morlovich
Copy link
Collaborator

FWIW #1272 is the shape it actually seems to be taking in the implementation.

@morlovich
Copy link
Collaborator

Just landed experiment config for this for canary/dev 50% (though it will take some time for it to take effect).
Please note that the parsing of new base values is not forward compatible, so you'll want to use try/catch (which you should be using for permission policy anyway).

@morlovich
Copy link
Collaborator

Config for beta 50% landed as well. As usual, it takes some time for the config to reach that many people.

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