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

Added documentation for 'bidRequestsCount' key in bid request #922

Merged
merged 2 commits into from
Aug 17, 2018
Merged
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
7 changes: 4 additions & 3 deletions dev-docs/bidder-adaptor.md
Original file line number Diff line number Diff line change
Expand Up @@ -223,15 +223,16 @@ Sample array entry for `validBidRequests[]`:
"transactionId": "d7b773de-ceaa-484d-89ca-d9f51b8d61ec",
"sizes": [[320,50],[300,250],[300,600]],
"bidderRequestId": "418b37f85e772c",
"auctionId": "18fd8b8b0bd757"
"auctionId": "18fd8b8b0bd757",
"bidRequestsCount": 1
}]
{% endhighlight %}

{: .alert.alert-success :}
There are several IDs present in the bidRequest object:
Notes on parameters in the bidRequest object:
- **Bid ID** is unique across ad units and bidders.
- **Auction ID** is unique per call to `requestBids()`, but is the same across ad units.
- **Transaction ID** is unique for each ad unit with a call to `requestBids`, but same across bidders. This is the ID that DSPs need to recognize the same impression coming in from different supply sources.
- **Bid Request Count** is the number of times `requestBids` has been called for this ad unit.

The ServerRequest objects returned from your adapter have this structure:

Expand Down