You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Only bid adapters who have enabled this feature will be able to utilize it. To do this, a bid adapter must add the following to their bidAdapter.js file:
| previousAuctionInfo.bidders | no | array of strings | Array of bidder codes to determine which bidders are allowed to receive collected previous auction info. Leaving the array empty will enable all bidders. By default, all bidders will be allowed to collect previous auction info. |
1422
+
| previousAuctionInfo.maxQueueLength | no | integer | The number of previous auction info payloads to store per bidder before injecting these payloads into the bidstream. Any payloads collected for a bidder during one auction will be injected into the bidstream during the next auction that the same bidder participates in with valid bids. By default, the value of this field is 10. |
1423
1423
1424
1424
* Only valid bid requests submitted by bidders who have enabled the Previous Auction Info module will be permitted.
1425
1425
@@ -1428,7 +1428,7 @@ If the requirements above are met, the flow for how the module works is as follo
1428
1428
1. A Prebid.js auction runs and completes
1429
1429
1. At the end of an auction, details about the auction are collected from each bidder using the module
1430
1430
1. If a Prebid bid wins, then the `rendered` field is updated to `1` to indicate this in the collected auction data for all bidders who bid on the same adunit
1431
-
1. During the next Prebid.js auction, if a bidder has this module enabled AND submits a valid bid request, then previous auction info data will be injected into the bid request of the new auction within the following path: `ortb2.ext.prebid.previousAuctionInfo`
1431
+
1. During the next Prebid.js auction, if a bidder has this module enabled AND submits a valid bid request, then previous auction info data will be injected into the bid request of the new auction within the following path: `ortb2.ext.prebid.previousauctioninfo`
1432
1432
1433
1433
`previousAuctionInfo` is an array of prior auction data catered to a specific bidder (if present, it will be added to a bidder's bid request), the structure of the data looks like this (Note: Once collected previous auction data has been injected into the bid stream, then it is removed from storage):
0 commit comments