Skip to content

Latest commit

 

History

History
61 lines (42 loc) · 4.38 KB

ara-tester-list.md

File metadata and controls

61 lines (42 loc) · 4.38 KB
Raw

Attribution Reporting API Tester List

Ecosystem Use of the Attribution Reporting API

The purpose of this page is to consolidate 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; if testers do not contribute or the information becomes stale it would make sense to deprecate.

Disclaimers

  • Not a complete list. Participants 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 activity.

  • Not evaluative. The purpose of this page is to consolidate links to information published by Privacy Sandbox participants. 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 Attribution Reporting API 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.
    • 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 Attribution Reporting API GitHub page, navigate to the document in the main table called ara-tester-list.md

  2. Click the ‘pencil’ icon on the right side to edit the appropriate 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 the edits and add your information in the coming days.

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

Table - Direct Integrations

Company / Party Industry or vertical Est. Testing Timeframe Link to testing plan and/or learnings (optional) How to contact you (optional)
Criteo Ad tech services [email protected]
Teads Ad tech services [email protected]
SMN Ad tech services [email protected]
Yahoo! JAPAN Ad tech services 2022-2023 Report
NextRoll Demand-side platform (DSP) [email protected]
RTB House Demand-side platform (DSP) [email protected]
CyberAgent(Dynalyst) Demand-side platform (DSP) [email protected]
Google (Ads Products & Platforms) Ad tech services Testing ongoing Clients can reach out to their account manager directly
MicroAd SSP & DSP [email protected]
Tremor International SSP & DSP 2023-2024 coming soon [email protected]
Seedtag SSP & DSP 2023-2024 coming soon [email protected]

Table - Publishers and Advertisers Interested in Testing or Early Adoption

Companies who may be interested in participating in tests and early adoption opportunities provided by ad tech companies.

Company / Party Role (publisher/sellside, advertiser/buyside, etc.) Additional details about your interest (Optional) How to contact you
Vocento Publisher [email protected]
Clarin Publisher [email protected]