Skip to content

Latest commit

 

History

History
53 lines (37 loc) · 4.88 KB

fledge-tester-list.md

File metadata and controls

53 lines (37 loc) · 4.88 KB
Raw

FLEDGE Tester List

Ecosystem Testing of FLEDGE

The purpose of this page is to consolidate testing information which is currently distributed across various GitHub issues, company blogs, social posts, etc. The usefulness of this page depends on testers sharing information and updates.

Disclaimers

  • Not a complete list. Testers are strongly encouraged to share their activities and insights publicly for the benefit of the broader community, but sharing is voluntary and therefore this page is not expected to reflect all testing activity.

  • Not evaluative. The purpose of this page is to consolidate links to information published by Privacy Sandbox testers. Editors will review submissions for relevance and to ensure general conformance to the guidelines above, but are not evaluating or endorsing the information provided.

  • Editors will regularly review and approve submissions that meet the guidelines below. If you believe that an error has been submitted, please create an issue in the FLEDGE repository with the words ‘[Tester List]‘ in the subject and the Editors will respond in short order.

Guidelines

  • Enter information on behalf of your own organization.

  • Do not share test results or other detailed information inline; instead link to GitHub issues or other public pages for elaboration and discussion.

  • Table fields:

    • Company/Party: The organization directly conducting tests or analysis.
    • Role in testing: Organization’s role(s) with respect to testing FLEDGE. For example, SSP, DSP, Publisher, etc.
    • Est. Testing Timeframe: Expected start and duration of tests, if known.
    • [Optional] Link to Testing Plan and/or Learnings: Link to GitHub issues, blog posts or other public information. This could include plans for upcoming tests, or insights and summaries from completed tests.
    • [Optional] How to Contact You: For example, a website form or reply on a GitHub issue.

How to submit

  1. On the FLEDGE GitHub page, navigate to the document in the main table called ‘fledge-tester-list.md’ (If you can read this sentence then you have already completed this step!)

  2. Click the ‘pencil’ icon on the right side to edit the table and add your information

    1. Use the | to make sure that the information that you provide correctly shows up in each cell
    2. After you select ‘Propose changes’ an editor will review and publish your updates in the coming days.

  3. You can find additional details here for editing tables in GitHub.

Table

Company / Party Role in testing Est. Testing Timeframe Link to testing plan and/or learnings How to contact you
Criteo DSP [email protected]
NextRoll DSP [email protected]
OpenX SSP Limited testing in progress [email protected]
RTB House DSP Continuous testing ongoing; long term commitment. https://blog.rtbhouse.com/whitepaper-deep-insights-from-early-fledge-experiments/ [email protected]
SMN DSP [email protected]
CafeMedia ad service for >3900 publisher sites duration of origin trial [email protected]
CyberAgent(Dynalyst) DSP [email protected]
Google Ad Manager + AdSense (including with Authorized Buyers) SSP Testing ongoing Publishers (Ad Manager)
Publishers (AdSense)
Authorized Buyers (DSPs)
Multi-seller auction support		 Publishers with questions should reach out via their account manager directly, or via our support channels.

Authorized Buyers (DSPs) interested in testing should follow the steps listed in the onboarding guide.

For technical questions on the experimental GPT API for multi-seller auctions, reach out via the “send feedback” button on the GPT developer site.
Google Ads + Display & Video 360 DSP 2022-2023 Advertisers with questions can reach out via their account manager, or directly via this form.
MicroAd SSP & DSP [email protected]
Neodata Group SSP & DSP [email protected]