Issues: WICG/turtledove
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
FLEDGE: how is publisher first party extension use case supported?
#144
opened Mar 12, 2021 by
jdelhommeau
Attacks Against Proposed Outcome-Based Microtargeting Prevention
#140
opened Mar 10, 2021 by
johnwilander
FLEDGE: support multi-level frequency capping
Non-breaking Feature Request
Feature request for functionality unlikely to break backwards compatibility
#138
opened Mar 5, 2021 by
stguav
FLEDGE: clarification on support for post-view conversion measurement
#131
opened Mar 3, 2021 by
RLemonnierScibids
FLEDGE: User-based A/B testing
Non-breaking Feature Request
Feature request for functionality unlikely to break backwards compatibility
#122
opened Feb 23, 2021 by
alois-bissuel
Securely Propagating Auction Signals
FLEDGE
Non-breaking Feature Request
Feature request for functionality unlikely to break backwards compatibility
#119
opened Feb 22, 2021 by
jeffkaufman
FLEDGE : Answering contextual requests with a generate_bid() function
FLEDGE
#116
opened Feb 19, 2021 by
MarieScibids
FLEDGE: Parity among players, Accountability, Transparency, and Fraud Detection
FLEDGE
#114
opened Feb 18, 2021 by
TheMaskMaker
FLEDGE Reporting API: Highest other bid data
FLEDGE
Non-breaking Feature Request
Feature request for functionality unlikely to break backwards compatibility
#111
opened Feb 10, 2021 by
vineetkahlon
FLEDGE: Clarity on ability to report into the Conversion Measurement API
FLEDGE
Non-breaking Feature Request
Feature request for functionality unlikely to break backwards compatibility
#103
opened Feb 4, 2021 by
eriktaubeneck
FLEDE : Optimal “Optimization & Performance” reporting for training bidding models
FLEDGE
Non-breaking Feature Request
Feature request for functionality unlikely to break backwards compatibility
#101
opened Feb 4, 2021 by
abdellah-lamrani-alaoui
FLEDGE: extend runAdAuction to support multiple ad slots
FLEDGE
Non-breaking Feature Request
Feature request for functionality unlikely to break backwards compatibility
Participation on contextual requests required to pass signals back to in-browser bidding logic
#83
opened Jan 6, 2021 by
polvorin
Non-JS based APIs for adding users to interest group in Turtledove
Non-breaking Feature Request
Feature request for functionality unlikely to break backwards compatibility
#82
opened Dec 22, 2020 by
nikunj101
ProTip!
Type g p on any issue or pull request to go back to the pull request listing page.