Skip to content

Primary & Secondary Bidders #4612

@bsardo

Description

@bsardo

This feature request originated from PMC discussions on #4416 and is similar to the primary/secondary bidder feature in PBJS. The purpose of this feature is to improve performance, specifically in the situation where a bidder is responding with a 2xx status code within the allotted time (no timeout) but is slow to respond.

Bidders may be classified as either primary or secondary.
If a bidder is classified as primary, Prebid Server will wait for its response before proceeding with the auction.
If a bidder is classified as secondary, Prebid Server will not wait for its response before proceeding with the auction.
This means that only those responses that are received before the last primary bidder responds are considered in the auction.

The initial ask is to add this capability as an account-level config so that each account may specify primary and secondary bidders. If not specified, all bidders default to primary.
TBD on the field name.

A potential future enhancement is to add a similar request-level config.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    Triage

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions