Skip to content

Yahoo DSP support #87

Open
1 of 1 issue completed
Open

Description

@aram356

Description

Define and validate what “Yahoo DSP support” means for Trusted Server. The existing ticket had no description; a May 2026 comment says follow-up on testing was requested, but does not identify the bidder route, protocol, partner prerequisites, or expected outcome. Do not assume an integration is complete from that comment.

Proposed scope

  • Confirm whether the intended path is through an existing auction provider, a direct bidder connection, or another arrangement, and record the partner's test requirements.
  • Map required bid request fields, identity/consent handling, bid response fields, and creative handoff to the selected Trusted Server path.
  • Exercise the path with test traffic and record any code or configuration gaps.

Done when

  • The selected route, partner contact/test status, prerequisites, and supported formats are documented.
  • A representative request and response are validated end to end, including no-bid or error behavior, or the ticket records why testing could not proceed.
  • Any remaining implementation work is specified with owners and acceptance checks.

Related

The May 2026 comment is historical testing follow-up, not a documented API contract.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions