Skip to content
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

Convention to set blocked banner attributes / battr #7925

Closed
pboisso opened this issue Jan 8, 2022 · 6 comments
Closed

Convention to set blocked banner attributes / battr #7925

pboisso opened this issue Jan 8, 2022 · 6 comments

Comments

@pboisso
Copy link

pboisso commented Jan 8, 2022

Type of issue

Feature request

Description

I could not find any way to set battr to block some banner attributes from bids (only on videos). How is it possible on banners? If currently not possible, could this be considered as a feature request? Thanks!

Platform details

prebid.js

@bretg
Copy link
Collaborator

bretg commented Jan 11, 2022

Blocked Attributes/Advertisers/etc are generally defined at the SSP level.

There are a few bid adapters that have instructions on how to specify the battr/etc. I see a few like Adagio, PulsePoint, TappX.

The definition of battr/badv/etc would be easy to make a convention:

pbjs.setConfig({
   ortb2: {
       battr: [...],
       badv: [...],
       bcat: [...],
       etc.
   }
});

Then it would up to each bid adapter to read from this location rather than their bidder-specific params.

Will leave it up to @gglas and @patmmccann to decide whether this should (A) be a convention and (B) get enforced in a future major release.

@ChrisHuie ChrisHuie changed the title Ability to set blocked banner attributes / battr Convention to set blocked banner attributes / battr Feb 14, 2022
@patmmccann
Copy link
Collaborator

patmmccann commented Mar 25, 2022

It seems to me the PR here would look like this: modification to all adapters that see battr, bcat, or badv on their bidder parameters to append the ortb2 field to their params if it is set.

The doc pull would look like this: all the bidders specifying these params would say they also read from ortb2. The first party data page would get an example of it in the massive set config. A discussion of it would go into the getting started or adops setup section.

This would be incredibly helpful to companies that manage a wide variety of webssites with different brand safety tolerences, eg a magazine company with both an alcohol or lifestyle brand and another with an audience with different expectations.

@jdcauley
Copy link

@patmmccann the committee seems generally in favor of encouraging that other adaptors be encouraged to adopt the standard

@patmmccann
Copy link
Collaborator

@bretg is there any simple way to specify if the bcat list should replace or append an existing list, eg one the pub configured in an ssp ui?

cc: @mike-chowla

@patmmccann
Copy link
Collaborator

patmmccann commented Apr 18, 2022

also, it seems battr is not a top level param; it belongs on imp.banner i think ? https://iabtechlab.com/wp-content/uploads/2021/12/OpenRTB-2.6.pdf

@patmmccann
Copy link
Collaborator

Closing this, we will document it in the 7.0 docs release

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

No branches or pull requests

5 participants