pm-harshad-mane
commented
5 years ago Hello @r-schweitzer , Can you please share a test-page where with this scenario?
@mkendall07 @jsnellbaker I think the issue is due to large values stored in native assets key-value pairs as other key-value pairs do not have large values. Can we avoid sending native assets in key-value pairs and share an API which will return requested asset from a specified creative(using bid-id)? this will help us avoid sending native-assets related key-value pairs.
ghost
stale[bot]
Type of issue
Feature
Description
This the same issue as described in #3800
In certain scenarios, Prebid may generate a large number of targeting keys after an auction has completed. An issue could arise when Prebid needs to send all these keys (and their values which can vary in length) to GAM or any other ad server, as this data is typically sent over as query-data in the ad server's request URL and some systems may have limits to the query-data's size.
In such scenarios, commonly what happens is that the query-data is truncated at the designated point and the ad server processes what keys came through and acts accordingly with that data-set. In Prebid's case, this can lead to issues with the Prebid ad being properly rendered (such as if some data points for a native bid were missing) or delivery issues if the Prebid line-item/campaign was targeting off of certain keys that were dropped.
Proposed Solution
Prebid.js will offer a new config setting that will cap the number of bids made per ad unit when sendAllBids is enabled. This limiter setting will take in a number which will represents the bidCap (defaulted to zero). When bids are capped at zero sendAllBids will function normally. When the bidCap is set to 2 for example, only the targeting for the top 2 bids will be sent to the ad server for each adunit.
An example of the setting:
pbjs.setConfig({ bidCap: 2 })