-
Notifications
You must be signed in to change notification settings - Fork 215
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
PAAPI support for nested component auction #1160
Comments
No, we do not support more levels of auction. |
@johnzhang-amzn, you might find the references in #251 of interest. TURTLEDOVE started out with only a single-level auction, a local decision over the demand coming through a single SSP. |
Not for me to answer. |
If there was the option that there could be multi level component auctions, it would be interesting for Bidswitch to host one on behalf of SSP's and trading pairs that currently trade via BSW on Ortb |
Can PAAPI support more than 2-levels of auction?
looks like PAAPI only supports upto 2-level auctions (a top-level auction plus a 2nd-level component auctions). In today's contextual bidding flow, there can be more than one SSP between the publisher and the DSP. Assuming the top-level auction is run by the publisher/their ad-tag/their-adServer/etc (ie not one of the SSPs), then it is impossible for each of the SSPs to participate in the same PAAPI auction as they would in the contextual auction.
Put it differently, I would like to run a 3-level auction in PAAPI:
level1: top-level auction by the publisher-adServer
level2: component auction by the SSP (SSP1) which the publisher is directly connected to
level3: component auctions by each of the SSPs (eg SSP2, SSP3) that get requests from SSP1
if I construct an auction config as outlined above and call runAdAuction, it fails with
TypeError: Failed to execute 'runAdAuction' on 'Navigator': Auctions listed in componentAuctions may not have their own nested componentAuctions.
Has anyone run into this or considered multi-level auction in PAAPI flow?
The text was updated successfully, but these errors were encountered: