microsoft/parakeet

Introduction

At Microsoft, we are committed to fostering a healthy web ecosystem where everyone can thrive – consumers, publishers, advertisers, and platforms alike. Protecting user privacy is foundational to that commitment and is built into Microsoft Edge with features like Tracking Prevention, Microsoft Defender SmartScreen, and InPrivate browsing. We also support an ad-funded web because we don't want to see a day where all quality content has moved behind paywalls, accessible to only those with the financial means.

Through this proposal, we believe we can substantially improve end-user privacy while retaining the ability for sites to sustain their businesses through ad funding. We propose a new set of APIs that leverage a browser-trusted service to develop a sufficient understanding of user interests and therefore enable effective ad targeting without allowing ad networks to passively track users across the web. This approach removes the need for cross-site identity tracking, enables new privacy enabling methods to support monetization, and maintains ad auction functionality within existing ad tech ecosystems.

We're pleased to further this discussion among the web community with the contribution of one possible approach. We will continue to collaborate with the community to iterate on this and other proposals with the goal of landing on a set of interoperable standards that work in multiple browsers. Together with the web community, we have an opportunity to share ideas, learn from each other, and create a better future for the web.

Proposals

• PARAKEET
  • PARAKEET polyfill
• PARAKEET with Noisy Ranking
• MaCAW
• Masked LARK: Masked Learning, Aggregation and Reporting worKflow

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

Trademarks

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.

parakeet's Issues

PARAKEET Polyfill Sign-up

To enroll in the Polyfill test:

1. Open a new Polyfill-Sign-up issue & identify your company and the groups you are working with
2. Complete the steps on our PARAKEET Polyfill registration page and link your Polyfill-Sign-up issue to your registration.

[Polyfill-Sign-up]

Company:
Partners/Groups:

• Click here to complete PARAKEET Polyfill registration

Dropping targeting features (maybe prioritization?)

I think it would be very helpful for the polyfill to include at least a minimal version of noising the targeting signals from the proxied ad request.

Perhaps the simplest way to do this is:

1. Expand the polyfill API to allow some kind of weights or priorities to be attached to features (both user-interest and contextual features), and then
2. Provide an option in navigator.createAdRequest() to set a priority threshold, where the proxy drops any features with priority below that threshold value.

This is maybe too unrealistic to be useful, but I'm afraid that fully faithful signals are also too unrealistic to be useful.

Workflow on polyfill

Hi @mehulparsana ,

Apologies as this was likely discussed during previous PARAKEET call, but I couldn't attend, so I wanted to clarify what is the expected behavior for ongoing test with polyfill.

Is the polyfill workflow already including the parakeet service, or is the polyfill js script emulating the parakeet service client and making direct call to the ad-network?

Looking at the code in Parakeet.Polyfill.ts

It seems the createAdRequest makes a direct call form the page to "https://edge.microsoft.com/.well-known/ad-bundles" url. According to the parakeet spec, it seems that the ".well-known/ad-bundles" endpoint is the ad-network endpoint that parakeet service would call. So my understanding is that in the polyfill test phase, there is no actual parakeet service needed, this is all emulated by the polyfill.

Correct?

Does it also means that any SSP that would like to test should update his own version of parakeet.polyfill.ts to use his own endpoint (rather than microsoft's one) ?

Thank you for your help clarifying above points.

[Polyfill-Sign-up]

Company:The New York Times Company
Partners/Groups: Microsoft, Xandr

• Click here to complete PARAKEET Polyfill registration

[Polyfill-Sign-up]

Company: Xandr
Partners/Groups: TBD

• Click here to complete PARAKEET Polyfill registration

[Polyfill-Sign-up]

Company:
Partners/Groups:

• Click here to complete PARAKEET Polyfill registration

[Polyfill-Sign-up]

Company: The New York Times
Partners/Groups: Xander

• Click here to complete PARAKEET Polyfill registration