This repository was archived by the owner on Nov 7, 2025. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 7, 2025. It is now read-only.
Add SSP to the query parameter of the key value server. #987
Description
This proposal is for implementing a blocklist for SSPs.
Some SSPs have restrictions on ad categories.
There are three ways to check if an ad is included in the blocklist when generateBid.
- store the blocklist in IG.
- fetch the blocklist from the trusted server.
- include the blocklist in perBuyerSignal.
All of these make the blocklist public, which is not preferable.
If the query parameter contains the SSP name, we can only retrieve if the IG is included in the blocklist.
Activity
[-]I want to add SSP to the query parameter of the key value server.[/-][+]Add SSP to the query parameter of the key value server.[/+]hanishi commentedon Jan 17, 2024
It is essential to recognize that ad category restrictions are typically within the purview of SSP, and the
scoreAdfunction can be an effective tool for ad category restrictions. Different publishers may have different standards and definitions for what constitutes a restricted ad (category). This variability can make applying a one-size-fits-all approach in thegenerateBidprocess challenging if that is your proposal, IMHO.Pre-scoring creatives stored in Interest Groups could be a proactive approach to managing ad category restrictions effectively, particularly if a set of standardized criteria or guidelines supports it.
michaelkleber commentedon Jan 17, 2024
Today a single interest group might bid in the same auction through multiple different SSPs. In that case, it seems like the addition of the SSP name to the Key-Value request on the trusted server would force the browser to send multiple KV requests.
The request already includes the publisher's domain. Might that be enough? You said "Different publishers may have different standards", so maybe you can decide based on the publisher, not based on the particular SSP.
k-o-ta commentedon Jan 17, 2024
@michaelkleber
Thanks for sharing your concern.
I understand that the name of the SSP is not determined until the runAdAuction is called, so we cannot multiplex requests to the trusted server.
Some SSPs also have their own standards, which may be independent of the publisher's standards. Therefore, it is not suitable for our use case.
michaelkleber commentedon Jan 17, 2024
I understand your goal. It seems to me that if some SSPs have some particular categories of ads that they are unwilling to touch, then that information should probably be stored in the ad metadata (that is, it can be stored in the Interest Group at the time of IG Join or Update). Each ad could either hold onto a list of "dangerous category tags", or else a list of specific SSPs that it should not bid through, which could be evaluated at on-device bidding time.
k-o-ta commentedon Jan 18, 2024
Thanks for the advice. It will works for me.