Skip to content

added adapter request params #2318

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

Merged
merged 1 commit into from
Sep 9, 2020
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions prebid-server/developers/add-new-bidder-go.md
Original file line number Diff line number Diff line change
Expand Up @@ -49,6 +49,20 @@ Bidder implementations may assume that any params have already been validated ag
{: .alert.alert-warning :}
Prebid Server bid adapters must follow all required conventions defined in the [Module Rules](/dev-docs/module-rules.html). Not doing so could lead to delays in approving your adapter for inclusion in Prebid Server. If you'd like to apply for an exception to one of the rules, make your request in a new [Prebid Server issue](https://github.com/prebid/prebid-server/issues).

### Bid Request Standards

Prebid clients ([Prebid.js](/use-cases/pbs-pbjs.html), [Prebid SDK](/use-cases/pbs-sdk.html), and [AMP](/use-cases/pbs-amp.html)) pass a number of parameters
that bid adapters should take into account:

- Currency: The publisher's desired bid currency is in the OpenRTB `cur` field. If your bid is in a different currency, you must set the bid currency in the response.
- Bid Floor: `imp[].bidfloor` and `imp[].bidfloorcur` - please make use of this value before responding with a bid.
- First Party Data: bidders should look in these locations for first party data: `imp[].ext.context.data.*`, `site.ext.data.*`, `app.ext.data.*`, and `user.ext.data.*`.
- Supply Chain: `source.ext.schain`
- GDPR: `regs.ext.gdpr` and `user.ext.consent`
- CCPA: `regs.ext.us_privacy`
- COPPA: `regs.coppa`
- Test: Bidders should be aware that the OpenRTB `test` flag indicates non-production traffic.

### Bid Response Metadata

In addition to the standard OpenRTB2.5 response fields, Prebid encourages bidders to
Expand Down
17 changes: 17 additions & 0 deletions prebid-server/developers/add-new-bidder-java.md
Original file line number Diff line number Diff line change
Expand Up @@ -88,6 +88,23 @@ Bidder response processing:
1. Extract bids from response;
2. Set each bid type and currency;

### Bid Request Standards

Prebid clients ([Prebid.js](/use-cases/pbs-pbjs.html), [Prebid SDK](/use-cases/pbs-sdk.html), and [AMP](/use-cases/pbs-amp.html)) pass a number of parameters
that bid adapters should take into account:

- Currency: The publisher's desired bid currency is in the OpenRTB `cur` field. I
f your bid is in a different currency, you must set the bid currency in the respo
nse.
- Bid Floor: `imp[].bidfloor` and `imp[].bidfloorcur` - please make use of this v
alue before responding with a bid.
- First Party Data: bidders should look in these locations for first party data: `imp[].ext.context.data.*`, `site.ext.data.*`, `app.ext.data.*`, and `user.ext.data.*`.
- Supply Chain: `source.ext.schain`
- GDPR: `regs.ext.gdpr` and `user.ext.consent`
- CCPA: `regs.ext.us_privacy`
- COPPA: `regs.coppa`
- Test: Bidders should be aware that the OpenRTB `test` flag indicates non-production traffic.

### Bid Response Metadata

In addition to the standard OpenRTB2.5 response fields, Prebid encourages bidders to
Expand Down