https://github.com/WICG/turtledove

TURTLEDOVE
https://github.com/WICG/turtledove

Last synced: about 2 months ago
JSON representation

TURTLEDOVE

• Host: GitHub
• URL: https://github.com/WICG/turtledove
• Owner: WICG
• License: other
• Created: 2020-01-16T14:32:18.000Z (almost 5 years ago)
• Default Branch: main
• Last Pushed: 2024-11-07T02:27:07.000Z (2 months ago)
• Last Synced: 2024-11-07T03:25:06.962Z (2 months ago)
• Language: Bikeshed
• Homepage: https://wicg.github.io/turtledove/
• Size: 16.9 MB
• Stars: 531
• Watchers: 165
• Forks: 233
• Open Issues: 413
• Metadata Files:
  • Readme: README.md
  • Contributing: CONTRIBUTING.md
  • License: LICENSE
  • Code of conduct: CODE_OF_CONDUCT.md

Awesome Lists containing this project

• awesome-list - turtledove

README

        
> FLEDGE has been renamed to Protected Audience API. To learn more about the name change, see the [blog post](https://privacysandbox.com/intl/en_us/news/protected-audience-api-our-new-name-for-fledge)

# TURTLEDOVE

Some online advertising has been based on showing an ad to a potentially-interested person who has previously interacted with the advertiser or ad network.

Historically this has worked by the advertiser recognizing a specific person as they browse across web sites, a core privacy concern with today's web.

The TURTLEDOVE effort is about offering a new API to address this use case while offering some key privacy advances:

*   The browser, not the advertiser, holds the information about what the advertiser thinks a person is interested in.

*   Advertisers can serve ads based on an interest, but cannot combine that interest with other information about the person — in particular, with who they are or what page they are visiting.

*   Web sites the person visits, and the ad networks those sites use, cannot learn about their visitors' ad interests.

**Chrome has been running [a FLEDGE Origin Trial since milestone 101 (March 2022)](https://groups.google.com/a/chromium.org/g/blink-dev/c/0VmMSsDWsFg/m/_0T5qleqCgAJ).  For details of the current design, see [the FLEDGE explainer](FLEDGE.md) or [the in progress FLEDGE specification](https://wicg.github.io/turtledove/).**

The FLEDGE design draws on many discussions and proposals published during 2020, most notably:

*  The [original TURTLEDOVE](Original-TURTLEDOVE.md) from Chrome.

*  [SPARROW](https://github.com/WICG/sparrow) from Criteo, which entered [WICG incubation jointly](https://discourse.wicg.io/t/advertising-to-interest-groups-without-tracking/4565) with TURTLEDOVE.

*  [Outcome-based TURTLEDOVE](OUTCOME_BASED.md) and [Product-level TURTLEDOVE](PRODUCT_LEVEL.md) from RTB House.

*  [Dovekey](https://github.com/google/ads-privacy/tree/master/proposals/dovekey) from Google Ads.

*  [PARRROT](https://github.com/prebid/identity-gatekeeper/blob/master/proposals/PARRROT.md) from Magnite.

*  [TERN](TERN.md) from NextRoll.

Many additional contributions came from Issues opened in this repo, and from discussion in the [W3C Web Advertising Business Group](https://github.com/w3c/web-advertising).