Call for additional bid adapter technical checklist items

[bretg]

In the Summit this week one of the attendees (from Gourmet Ads) expressed a desire to have a checklist of technical best practices with a Prebid stamp of approval for each adapter.

The example listed was having both an iframe and a pixel sync, though it's not clear to me this is really something to enforce. Maybe we could require a pixel option, but I don't think we should require an iframe.

In general, I think the technical teams already do a pretty good job of enforcing a range of technical requirements:

• the general Prebid module rules
• no fully dynamic hosts
• operational email address
• documentation exists
• getting rid of adapters that are no longer active (a big driver behind PBS 2.0)

We're in progress on trying to improve metadata about geographic regions.

The Publisher Taskforce is working on a more business-focused set of metadata that I think is even more relevant for helping publishers choose from the staggering array of bid adapters.

But, it is worth opening the call to the community for specific ways the technical teams can continue to tighten the review process. If it's just requiring pixel syncs, should be possible to add that as a requirement for 3.0.

[bretg]

Discussed in committee:

• there may be additional metadata collected as part of adapter documentation. e.g. HTTP2, compression enabled, etc.
• the publisher committee is working on defining this additional metadata
• the Prebid Server community is still welcome to suggest technical rules that reviewers should enforce

[bretg]

One item that we should enforce during inspection: it's not ok for bidders to require publisher-provided parameters that define a geographic endpoint.

[bretg]

Closing this item:

• geographic scope issue is done in documentation
• the reviewers checklist create a reviewer checklist #3307 can be linked into the bidder docs when done
• It's been several months and no additional items have come up
• open a new issue as needed